Folder usage examples

You can use folders to plan releases and iterations, and track their progress. If you are managing an upcoming release or iteration, you can enter the start and end dates, holidays and non-working days, working hours in a day, available users, vacation and sick day hours, and target story points for a folder. Helix ALM automatically calculates the available man hours based on the information you enter. See Entering release planning information for folders.

After you configure the release information, team members can view the start and end dates, number of working days and remaining days in the period, available users, available man hours, and target story points in the Release Planning pane in the Folders list window. See Using the Folders list window.

Viewing live charts in the Folders list window can also help you monitor release or iteration progress. See Viewing live charts.

You can use folders to group and organize items for a specific project and share project information with team members. For example, you may want to group requirements for a new feature in folders so you can track progress and communicate information to others.

You can display important messages about a project in the Folders list window Details pane. For example, you may want to provide schedule updates, milestones, or information about the next build. See Entering folder details. You can also display a web page related to the project in the Web View pane. For example, you may want to display a wiki related to a project. See Setting the default web page for folders.

The Folders list window can also display time tracking information in columns, such as estimated and actual hours and percent complete. This information can help you monitor progress of individual items and overall calculations for all displayed items.

You can use folders to visually represent field relationships. For example, a project includes items for multiple products, which are values in the item Product field. Each product has multiple components, which are available in the Component field based on the value selected in the Product value. You can create a folder for each product and then create folders in each product folder to represent the related components.

You can use folders to organize test cases in test suites. For example, you may want to group regression test cases together with the related manual test runs in child folders.

You may also use folders to group test cases based on the areas to be tested, the test type, or tests that are automated. You can group manual test runs based on when they need to be performed, the system architecture, the assigned tester, or the manual test run results.

You can use folders and filters to create a triage system that decision makers can use to indicate an issue's priority. This can help you make sure high priority issues are fixed first, resolve priority conflicts, and maintain a history of issues fixed for a release. See Triaging Issues for more information.

You can use private folders to organize items related to your own work. For example, there may be change requests implemented that impact work you are responsible for. You can add these items to a private folder so you can easily locate and review the changes when you have time.