This page relates to the Cloud version of Rich Filters for Jira Dashboards. Please see the documentation index for Server & Data Center versions.

The Rich Filter Created vs. Resolved Chart Gadget

In this section:

  1. About the Rich Filter Created vs. Resolved Chart Gadget
  2. Configuring the Rich Filter Created vs. Resolved Chart Gadget

1. About the Rich Filter Created vs. Resolved Chart Gadget

The Rich Filter Created vs. Resolved Chart gadget displays the number of issues created versus the number of issues resolved over a given period of time. It is similar to Jira’s built-in Created vs. Resolved Chart gadget, but it is based on a rich filter instead of a Jira saved search and thus adds several new features:

  • the collection of issues used by the gadget can be further filtered using Rich Filter Controller gadgets;
  • the gadget itself can further refine the results by applying a gadget-specific JQL that we call working query;
  • the values used by the gadget can be customized (for instance, to show the sum of Story Points instead of the Issue Count).

2. Configuring the Rich Filter Created vs. Resolved Chart Gadget

Add a new or edit an existing Rich Filter Created vs. Resolved Chart gadget in your Jira dashboard. The configuration form of the gadget will be displayed.

Edit the gadget configuration as described below:

Rich filter

Select the rich filter the gadget will use.

Click on the Rich Filter button to display the list of rich filters; you can either scroll through or use the search box to find the filter you need.
The gadgets’ configuration forms only show the rich filters you are allowed to view. See the Rights and Permissions documentation page for details.

Working queryThe working query is an additional JQL query which is permanently applied on top of the base Jira filter and any active quick filters in the controller to further filter the issues the gadget will work with. The working query is optional: if left empty, only the base Jira filter and the quick filters affect the issues used by the gadget.
Aggregation periods

Select the periods on which the issues will be grouped. The available options are: Days, Weeks, Months, Quarters, Years, Auto.

If the Auto option is selected, the aggregation periods and time range are adjusted dynamically to produce the most granular yet complete statistics (i.e. with the appropriate aggregation period so that all the relevant issues are included).

Time range

Together with its subsettings, this specifies the total time span for which the statistics should be computed. 

The time range subsettings depend on the option selected in the Time range drop-down as described below.

Time rangeTime range subsettingDescription

Number of days / weeks etc.

NumberEnter the number of aggregation periods to be displayed. The time range corresponds to the specified number of consecutive aggregation periods.

Between dates

From / To

Enter the two dates that define the limits of the time range (both specified dates are inclusive).

The inputs can be selected from a date picker or entered manually as a calendar date ("yyyy/MM/dd" or "yyyy-MM-dd").

All dates

If selected, the time range is determined dynamically to include all the relevant issues (from the first date to the last date occurring in the values of the issues).

All dates is the only possible Time range option if the selected Aggregation period is Auto.

Contextual options

These are predefined Time range options which depend on the selected Aggregation period.

Possible options are: This year, Last year, This quarter, Last quarter, This month, Last month. 

Aggregation type

Select one of the following aggregation type options:

  • Period value: this is the default option – the chart displays the values of each individual aggregation period;
  • Cumulative trend: progressively adds the values from the previous periods, including only the issues starting with the first period of the chart;
  • Cumulative total: progressively adds the values from the previous periods, also including the issues before the first period.


Select the value to be computed for each aggregation period. There are two kinds of possible values:

  • Issue Count: computes the number of issues created/resolved in each aggregation period.
  • Numeric: computes the sum of a numeric field for the issues in each aggregation period. For instance, when using Jira Software, the gadget can show how many Story Points there are for the issues created/resolved in each aggregation period.

Unresolved trend

If checked, the graph will also include a sub-plot with the trend of unresolved issues over time.

The unresolved trend is always cumulative – when the selected Aggregation type is Period value, the Unresolved trend is computed as cumulative trend.