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. There are two approaches for setting up projects to show chart information by team:

Using Labels (Recommended)

With this approach, 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 which their teams work on. A 'team identifier' label is 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 to a JIRA issue, each team should apply a consistent 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.

Using Project Components (Not Recommended)

It is also possible to specify 'team identifiers' on JIRA issues as JIRA project components.

While project components have the benefit of ensuring consistent team identifiers are applied to issues (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 your team needs to manipulate issues from multiple JIRA projects on a Rapid View and specify team identifiers on these issues as project components, you would need to predefine the same set of team identifier components for each JIRA project available from that Rapid View.