If a product is being developed by more than one team, members of your teams may wish to view GreenHopper Classic chart data by issues which are relevant to their teams only. This requires that 'team identifiers' be specified on a team's issues. There are two approaches for specifying team identifiers on JIRA issues:
This simple approach involves adding a team identifier label to each issue worked on by a team. A 'team identifier' label is a JIRA 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.
Since team identifier labels are used for filtering issues (see Showing Chart Information By Team), consistent team identifier labels should be added to a team's 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.
It is also possible to specify 'team identifiers' on JIRA issues as Defining a Component.). (See the documentation on
Although using components as team identifiers ensures that consistent team identifiers are applied to issues (since each component must be), we do not recommend using components as team identifiers for the following reasons: