Warnings are a customizable set of markers that highlight possible flaws. May be treated as a fellow project manager, who’s seen some stuff.
They are represented as a tab with configurable options, and also as a column in any breakdown table:
Warnings are customizable per report only. That means you can have custom set of warnings for every report in your Jira instance, but you can’t share warnings settings across multiple reports.
As it was mentioned above, warnings are a set of common markers that point to issues without estimations, missing due dates, unassigned issues, etc.
Warnings are configured per report, and can be added as a column to any breakdown table.
A warning for an issue is displayed as a counter in a column with text tooltip that has all the details:
All of them are pretty self-explanatory, so they won’t be discussed in this article. In case you need to hear more, please let us know by sending a message to firstname.lastname@example.org.
We get this question about customizing the warnings pretty often. But unfortunately, Jira API is slow and every extra JQL request slows down report generation even more. That is why we’ve limited the number of warnings to a reasonable amount that doesn’t hurt performance too much.
Another reason is a bit more complicated: we want to keep the warnings easy to understand and use for as many users as possible. This is why the list of warnings is relatively short and their meaning is applicable to nearly any project.
First of all, we are really sorry you haven’t found what you need. Here are two ways to fix a missing warning:
Report slices let you create groups of issues using custom JQL.
But please keep in mind that JQL is still very slow, and custom slices can slow down report performance.