Warnings

Warnings can appear as columns in the Breakdown section of the Pivot, Worklogs/Comments, and Capacity tab types, as long as the Breakdown section is enabled and the Warnings column is shown.

Each issue associated with a warning is highlighted with a red tint. When you hover over the red square in the W (Warnings) column, a tooltip appears showing the specific warnings linked to that issue.

Warnings can appear in the Summary section of the Pivot tab type, as well as the Breakdown section.

Each warning type can be visualized in a vertical bar chart and combined with additional columns for context, such as Issue Type, Status Category, or Time Spent for the issues associated with each warning.

In the example shown, the Issue Count column displays a vertical bar chart showing the number of issues linked to each warning. Clicking a bar opens a Breakdown pop-up that lists the issues related to that warning. Alternatively, you can use the Breakdown section below the table to see the issues related to that warning.

Warnings can appear in the Summary section of the Worklogs/Comments tab, as well as the Breakdown section.

1. Within a selected time interval, you can filter issues flagged with warnings and identify which users logged time on those issues.

   Keep in mind that the list of flagged issues may change depending on the selected interval (e.g. Feb 23 - Mar 1, 2026). For example, older completed issues may still carry an Overdue or other warning, even if you are reviewing recent worklogs.

2. In the example shown, fields such as Warnings, User, Worklog Date, and Time Logged help you analyze which users logged time on flagged issues during the last two weeks.

   For example, the Active issue with no remaining estimate warning lists the relevant issues and the dates when time was logged. This helps you determine when the original estimate may have been exceeded—and evaluate the remaining effort as of the most recent worklog.

Warnings can appear in the Charts tab type.

Each warning type can be visualized in a vertical bar chart. In the example shown, the Y-axis on the left lists the enabled warnings that contain values, while the X-axis shows the number of issues associated with each warning.

When you click a bar, a Breakdown pop-up appears, displaying the list of issues related to that warning. The pop-up below shows Active issues with no estimates.

Yes. An issue can be flagged by one or more warning types.

1. Issues flagged by any enabled warnings are counted next to the tab name. In the example shown, 11 issues are flagged with at least one warning.

2. In the Summary section, the number of issues is displayed next to each warning type.

3. In the Breakdown section, issues are grouped by warning type. An issue flagged by multiple warnings appears under each relevant warning. For example, SSP-4 is flagged more than once and therefore appears under two warning types.

No. You cannot create custom warnings in the Warnings tab.

This highly requested feature is unavailable due to Jira’s API speed limits—each additional JQL request slows report generation. To maintain performance and usability, the number of warnings is intentionally limited.

The predefined warnings are designed to be simple and widely applicable, so users can easily understand and apply them across most projects.

If you want to create custom logic outside the Warnings tab, you can use Slices. Keep in mind that custom slices relying on JQL may impact report performance. Slices are explained in a separate article.

Yes. You can suggest a new warning to be added.

Some warnings are added based on user requests, so your idea could become the next one. To submit a suggestion, send your proposal to support@colined.com.

No. Activating all warnings does not affect the report’s loading time or performance.

Warnings are processed in your browser and run independently of Jira’s API, so enabling them does not slow down report generation.

No. The warnings selected in the Warnings tab are available across all tabs, and you cannot choose to show more or fewer warnings on a per-tab basis.

If you want warnings to be unavailable in other tabs, you must deselect them all in the Warnings tab.

No. Time zones do not change an issue's Due Date, as confirmed by Atlassian in a related article. However, they can affect when an Overdue warning appears in the report.

For example:

Employee A is assigned an issue with a Due Date of May 25 and works in the Eastern Time zone. The employee is still working on the task during the evening of May 25.

Employee B works in the Pacific Time zone. When Employee B views the same issue,, an Overdue warning may appear because the date in that time zone has already changed to May 26.

As a result, time zone differences can influence when an issue is flagged as overdue, even though the Due Date itself does not change.

The current date is based on the Default user time zone set in Jira. If Overdue warnings appear unexpectedly, you can review or update this setting in Jira System → General configuration → Internationalization.

Update the Default user time zone as needed to ensure the current date aligns with your users’ location.

No. The Warnings column in the Issue Structure tab does not display rollup values within the hierarchy.

1. For example, rollup values do not appear for a Project or any other field used for grouping.

2. The number of warnings is shown for each flagged issue. Hovering over this number displays the list of warnings in a tooltip.

This behavior is consistent with the Breakdown sections in the Pivot, Worklogs/Comments, and Capacity tabs.

No. Warnings cannot be displayed in Widgets within the Issue View. Widgets are exclusively available on Jira Cloud.

Each Warning comes with a predefined set of columns in the Breakdown section. To use additional columns, click Columns and select the fields from the dropdown.

For example:

1. Time Spent and Original Estimate are shown together for the Issue with logged time and no estimates warning to highlight how much time exceeded the original estimate.

2. Updated Date and Due Date appear together for the Overdue warning to show when the issue was last updated compared with its due date.

To display these columns for other warnings, you must add them manually.

No. Columns in the Breakdown section cannot be sorted. Each warning type uses a predefined set of columns, and the content of these columns cannot be reordered through sorting.

Yes. You can rearrange columns in the Breakdown section from the report sidebar.

1. Drag a field using the grid icon (the dotted handle on the left side of the field card) to change its position.

2. For example, drag Key above Summary to place it before that column.

Yes. You can sort and rearrange the Warnings column, along with other columns, within the Breakdown section in other tabs, as shown in a related article. Similar steps also apply to the Issue Structure tab.

Yes. In the Breakdown section or the Issue Structure tab, the Sprints column shows how many sprints each issue has been assigned to.

This can serve as a warning indicator. As the number of sprint assignments increases for incomplete issues, the risk of delay rises. You can then compare Time Spent with the Original Estimate to determine whether the issue should be reassigned, re-evaluated, or descoped.

When the Warnings tab shows OK next to its name in the Tabs section, or when the message Good job! No warnings found appears in the center of the screen, warnings are enabled. In this case, only the selected warnings are active, and none of them currently return results.

To verify whether all warnings—or only specific ones—are enabled in the report, follow these steps:

1. Click Warnings below the Good job! No warnings found message.

2. Alternatively, open the report sidebar and select Warnings from the available settings.

3. In the Warnings options, click Deselect All, then click Select All to enable every warning. (The Select All option appears only when no warnings are selected.)

4. To enable specific warnings only, select them individually instead of using Select All.

Warnings shown in grey are available only for Jira Service Management (JSM) projects. For these warnings to apply, a Service Level Agreement (SLA) must be configured.

If warnings are not appearing, they may be disabled for the report, as shown in the screenshot above. When the Warnings tab displays Off next to its name in the Tabs section, or when the message All warnings are disabled appears in the center of the screen, warnings are turned off.

To enable warnings, follow these steps:

1. Click Warnings below the All warnings are disabled message.

2. Alternatively, open the report sidebar and select Warnings from the available settings.

3. In the Warnings options, click Select All to enable all warnings.

4. To enable only specific warnings, select them individually instead of clicking Select All.

Warnings shown in grey are available only for Jira Service Management (JSM) projects. For these warnings to apply, a Service Level Agreement (SLA) must be configured.

If the Warnings tab is missing, as shown in the screenshot above, it may have been removed from the report.