Coloring issues
Viewing work
On this page
In this section
Related content
- How to find details of Assets Discovery Agent
- Assets Discovery step by step
- Assets Discovery agent throws "Value cannot be null. Parameter name: localaddr" error when starting
- Jira Assets Discovery Knowledge Base
- Assets Discovery agent throws "Value cannot be null. Parameter name: localaddr" error when starting
- How to copy configuration files between Discovery Tool and Discovery Agents
- Assets discovery throws "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified" when an agent is reinstalled.
- Assets Discovery overview
- How discovery Agents can export to Cloud instance
- How to install Discovery Agents unattended
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
- How to find details of Assets Discovery Agent
- Assets Discovery step by step
- Assets Discovery agent throws "Value cannot be null. Parameter name: localaddr" error when starting
- Jira Assets Discovery Knowledge Base
- Assets Discovery agent throws "Value cannot be null. Parameter name: localaddr" error when starting
- How to copy configuration files between Discovery Tool and Discovery Agents
- Assets discovery throws "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified" when an agent is reinstalled.
- Assets Discovery overview
- How discovery Agents can export to Cloud instance
- How to install Discovery Agents unattended