Coloring issues
Viewing work
On this page
In this section
Related content
- Removing releases
- Committing plan changes
- Removing dependencies from issues
- Issue created in the Advanced Roadmap plan is not showing in the project
- Deleting teams
- Frequently asked questions (live plans)
- Issue sources
- 3. Migrate classic plan data to a live plan
- Creating and deleting issues
- Creating and deleting plans
You can color issues using coloring options that are relevant to you, and to how your teams work. With issues relevantly colored in your plan, you can convey to your stakeholders more meaningfully how work is currently tracking.
Depending on how you're coloring issues, you may need to make additional configurations, like assigning colors to certain items in your plan.
An example of simple coloring would be coloring issues by status — any issue that's in the to do category will be colored blue, while issues in progress will be colored yellow, and issues in the done category will be colored green. Additional configurations are needed when you're coloring issues by label — you'll need to specify colors for each label that exists in your plan.
Sample plan, with issues colored by status
The following grouping options are available:
In this section
Related content
- Removing releases
- Committing plan changes
- Removing dependencies from issues
- Issue created in the Advanced Roadmap plan is not showing in the project
- Deleting teams
- Frequently asked questions (live plans)
- Issue sources
- 3. Migrate classic plan data to a live plan
- Creating and deleting issues
- Creating and deleting plans