Grouping by components
Grouping issues
On this page
Related content
- How to migrate existing Bamboo artifacts to an AWS S3 bucket or to an SFTP server
- Configuring the SFTP artifact handler
- Bamboo Artifact Handlers - Use Case Scenarios
- How to access artifacts that are only available locally on the Bamboo Agents
- Suggestion for optimising Artifacts size/storage
- Automatically archive build artifacts to Amazon's S3 storage
- Configuring Elastic Bamboo
- Artifacts in Bamboo Server
- Bamboo Best Practice - Sharing artifacts
- Changing storage paths for builds and artifacts in Bamboo
Before you begin, note that the components should already be existing in your Jira project. See Managing components to know how to create and use components in your Jira issues.
To create a group for a component in a plan:
- In the roadmap view of the plan, click View settings.
- From the 'Group by' menu, choose Component. The options for component groups will be displayed.
- Click + Create group.
- Enter a name for the new group.
- In the field that appears, start typing to enter the components that you want to add to the group.
To delete a component group, go to the 'group by component' view settings, find the group you want to delete, then click the delete icon next to it.
To group issues by components:
- In the roadmap view of the plan, click View settings.
- From the 'Group by' menu, choose Component. The issues in the plan will be grouped into component-specific swimlanes, with the component groupings sorted alphabetically.
Sample issues grouped by components
Notes when grouping by components:
In the example above...
- TIS-116 and TIS-4 are using components that are not included in the Admin group, as you can see in the 'group by component' view settings. However, their child story TIS-134 is using the component Office Support, which is included in the group. This is why the issues are grouped under Admin.
- Issues not using any of the configured component groups will be grouped under All other issues, as shown at the bottom of the example.
Last modified on Aug 21, 2019
Related content
- How to migrate existing Bamboo artifacts to an AWS S3 bucket or to an SFTP server
- Configuring the SFTP artifact handler
- Bamboo Artifact Handlers - Use Case Scenarios
- How to access artifacts that are only available locally on the Bamboo Agents
- Suggestion for optimising Artifacts size/storage
- Automatically archive build artifacts to Amazon's S3 storage
- Configuring Elastic Bamboo
- Artifacts in Bamboo Server
- Bamboo Best Practice - Sharing artifacts
- Changing storage paths for builds and artifacts in Bamboo
Powered by Confluence and Scroll Viewport.