Configure custom values

Contents:

1 About custom values
2 Custom values key attributes
3 Edit custom values
4 Computed custom values
- 4.1 Issue age/resolution time
- 4.2 Lead Time
- 4.3 Custom duration
5 Use custom values in rich filter gadgets
6 Use custom values in time series

About custom values

Custom values are user-defined outputs used in rich filter gadgets and time series, just like the built-in values. The custom values add new options for value display (label, color, formatting) and support for total formulas (sum, average, min, max). They can be based on issue count, numeric and time tracking field values, or computed duration (resolution time & issue age). Also, the scope of the custom values can be further refined using JQL sub-queries.

Below is an example of a Rich Filter Statistics gadget that displays, by assignee, the following custom values: the sum of the story points of the resolved issues, the sum of the time spent for support issues, the average time spent (displayed in hours) and the maximum remaining estimate for the unresolved issues.

Custom values key attributes

You can add new and see existing custom values and their key attributes in the Custom Values section of your rich filter.

The key attributes of a custom value are:

Attribute	Description

Attribute	Description
Name	Each custom value has a name used to identify and display it. The name is mandatory and must be unique among the custom values within the rich filter.
Color	Optionally, you can set a custom color to display the value in some rich filter gadgets.
Base value	Select the value on which your custom value is based. Your custom value can be based on: Issue count Numeric fields Time Tracking fields Duration - computed values (see Duration (calculated) Custom Values section below)
Total formula	The total formula is used when displaying totals for the custom values. Possible options are sum, average, minimum, and maximum values
Display	The display format of the custom value. The available options are For numeric fields: Thousand separators on/off Number of decimals: none or maximum 3, 2 or 1 or exactly 3, 2 or 1 For time-tracking fields: Jira's time display format – uses the time format as configured in Jira by the administrator of the instance Days, hours, minutes, or seconds What's the difference between maximum 2 and exactly 2 decimals? If you select the exactly 2 option the value will always be displayed with 2 decimals. This is achieved by rounding to 2 decimals if more than 2 are available (e.g., 23.4567 → 23.46) or padding with zeros up to a total of 2 decimals if fewer than 2 are available (e.g., 23.4 → 23.40). Selecting the maximum 2 option will display the value with 0, 1, or 2 decimals. This is achieved by rounding to 2 decimals if more than 2 are available (e.g. 23.4567 → 23.46) and leaving the value as it is if 2 or fewer decimals are available (e.g., 23.4 → 23.4).
JQL filter	You can optionally use a query to restrict the definition of this custom value to only a subset of issues. The custom value will be empty for the issues that do not satisfy this query.

Edit custom values

The custom values section of your rich filter also allows you do to the following operations:

To do the following:	Do this:

To do the following:	Do this:
Add a new custom value	Click Create custom value at the top-right of the page. Type a Name, select a color, Base value, Total formula, and a display format, (Optional) Type a JQL query, Click Create. You can add up to 50 custom values in each rich filter.
View or edit a custom value	Click the Edit ()icon next to a custom value to view or edit its configuration. Depending on your rights, you can edit or only view the custom value.
Delete a custom value	Click the Delete () icon next to the custom value name.
Reorder the custom values list	Hold the pointer over the queue's Grid () icon, then drag the custom value up or down to the new position. This order is applied when displaying the custom values in the settings of the rich filter gadgets and the time series where they can be used.

Computed custom values

Calculated custom values are a special case of custom values having a computed base value. Rich Filter for Jira Dashboards provides two calculated custom values that represent time duration:

Issue age/resolution time - predefined duration value calculated as the time elapsed between the resolution time (or now for unresolved issues) and the created date
Custom duration - duration value calculated as the time elapsed between any two date/date time fields or between a date/date time field and now

These options are further detailed in the sections below.

Issue age/resolution time

As its value type indicates, Issue age/resolution time is a computed duration value based on the issue created and resolved dates.

Here is how the Issue age / resolution time value is computed:

for resolved issues – the value represents the number of days between the resolution date and the created date (resolution time)
for unresolved issues – the value represents the number of days between now and the created date (issue age)

To create a custom value based on the issue age / resolution time, select the Issue age / resolution time option in the Base value drop-down menu. The option is available under the Duration (computed) category:

Lead Time

You can combine the Issue age / resolution time base value with JQL sub-queries to build custom values that show only the resolution time or only the issue age. For example, if you wish to see the lead time of your resolved issues, you can add the JQL query resolution that is not empty to your custom value definition and use the average total formula. Your custom value will show the average resolution time of your resolved issues – called the Lead Time.