Setting Up Projects to Show Chart Information By Team

If a product is being developed by more than one team, members of your teams may wish to view GreenHopper's chart data by issues which are relevant to their teams only.

To do this, GreenHopper projects do not need to be configured in any way. However, project administrators should ensure that 'team identifier' labels are specified on all JIRA issues worked on by their teams. A 'team identifier' label is essentially a label that identifies the team who worked on an issue. An issue may have more than one team identifier label if it was worked on by more than one team.

Be aware that team identifier labels will subsequently be used for filtering issues. Since any label can be added freely to a JIRA issue, each team should be consistent when applying their 'team identifier' label to their issues.
After a label has been added to a JIRA issue, it may appear in a list of suggestions in the 'Labels' dialog box's drop-down. Use the 'Suggestions' drop-down to assist with consistent issue labelling. See Adding a Label to an Issue for details.

It is also possible to specify team identifiers on JIRA issues as JIRA project components. While project components have the benefit of enforcing consistent team identifiers (since each component must be predefined by JIRA project administrators), we do not recommend using project components as team identifiers since components are JIRA project-specific. Hence, if you need to manipulate issues from multiple JIRA projects on a Rapid View and need to specify team identifiers on these issues as project components, you would need to predefine the same set of team identifier components in each JIRA project that is accessible from that Rapid View.