Work with applications
Applications are the separate components developed by the teams in your workspace. Applications can be independent of each other, or composite – designed to be integrated into a single product.
You can associate the following items with applications: themes, features, user stories, defects.
Items that do not belong to any application are assigned to the not set category. Themes and features can be associated with multiple applications.
Applications trickle up the product backlog tree, and do not trickle down:
-
When you associate child items with applications, the parent items are automatically associated with those applications. Group stories are not affected.
-
When you associate parent items with applications, the child items are not automatically associated with those applications. You can associate the child items with the applications separately.
- If child items are not associated with any application, they and their parent items are assigned to the not set category.

-
Define applications.
-
In the Configuration area, on the Workspace > Applications page, create a list of applications. You can define up to 300 applications.
-
On the Workspace > Users page, specify the applications users have access to. To require users to specify the application for new items, clear the (not set) value from the Applications field.
-
To require all users to specify the application for new items, select options in Configuration > Settings > Set required fields.
Note: After providing a user with access to an application, the user must log out of Agile Manager and log in again for the changes to take effect.
-
-
ALI: Associate build configurations with applications. This enables you to filter builds by application.
On the Workspace > Builds page, expand a build server, and click a build configuration. Specify an application.
-
ALI: Associate repository branches with applications. This enables you to filter code changes by application.
On the Workspace > Code page, expand a source code server, and click a branch. Specify an application.

-
Administrators: In the Configuration area, on the Workspace > Users page, specify the applications users have access to.
Note: Items that do not belong to any application are assigned to the not set category. Determine whether users have access to such items.
-
Users: The information displayed in Agile Manager is filtered according to the applications to which you were given access.
You can further filter the information by a specific application: select an application from the Application selector, or define a filter on the Applications column.
Note:
- Items can belong to the not set category. Such items will be displayed only if you have access to the not set category.
- A feature or theme may be associated with several applications. The feature or theme will be displayed as long as you have access to at least one of its applications.

-
Review overall application health and quality.
Use the Application Summary view to gain insight into the quality and health of applications in a release, based on code change, defect, and build information.
For more details, see ALI: Analyze application quality .
-
Review build and code change information for applications.
Filter build and change set information by application. Open the Builds or Source Code page, and select an application to filter by.

You can track the progress of an application on the Features and Themes pages, or in a widget on the Dashboard.
Use the following methods to track application progress:
-
Features and Themes pages: On the Features or Themes page, filter the grid by Application. Only the items belonging to the specified application will be listed. Use the progress bars to track the work on the application's features or themes.
-
Dashboard: On the Dashboard, use one of the following:
-
In the widget gallery, select from a selection of widgets under the Applications category.
-
Customize other widgets to display data by application.
-