Configure custom values

Configure custom values

 

About custom values

Custom values are user-defined outputs that can be used in rich filter gadgets. They are available as columns in views and as values in gadgets alongside the Jira fields. They provide support for custom aggregation formulas (sum, average, minimum, and maximum, with optional JQL filtering of contributing issues) and custom results display (label, color, and format). Custom values can be based on Issue Count or numeric and time-tracking fields.

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.

statistics with custom val.png

Custom values key attributes

The Custom values section of your rich filter lets you add new custom values and view their configuration.

custom_values.png

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

The selected color will be used to display the value in some of the rich filter gadgets.

Base value

The value on which your custom value is based is selected among Issue Count or numeric and time-tracking fields.

Total formula

The formula used for aggregation. The possible options are sum, average, minimum, and maximum.

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 exactly 2 options, the value will always be displayed in 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

You can optionally define a JQL query to filter the issues contributing to the custom value. Only the issues satisfying this query will be taken into account when calculating the custom value.

Add and edit custom values

The Custom values section of your rich filter lets you perform the following operations:

To achieve this:

Do the following:

To achieve this:

Do the following:

Add a new custom value

  1. Click Create custom value at the top-right of the page.

create_custom_val.png
  1. Type a Name, select a color, Base value, Total formula, and a display format,

  2. (Optional) Type a JQL query,

  3. Click Create.

You can add up to 50 custom values in each rich filter.

View or edit a custom value

Click the Edit (edit icon.png)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.

Reorder the custom values

Hold the pointer over the queue's Grid (grid icon.png) icon, then drag the custom value up or down to the new position.

Delete a custom value

Click the Delete (delete_icon.png) icon next to the custom value name.

Computed custom values

Computed custom values are a special case of custom values having a computed base value. Like any other custom value, computed custom values can be used in views and rich filter gadgets.

The Rich Filter app provides two computed duration custom values:

  • 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

Issue age / resolution time is a predefined computed duration value based on the issue created and resolved dates. The issue age / resolution time is calculated as:

  • for unresolved issues – the time elapsed between now and the created date (issue age)

  • for resolved issues – the time elapsed between the resolution date and the created date (resolution time)

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:

The Total formula and JQL fields are the same as any other custom value described in Custom Values' Key Attributes.

The Duration display format field is duration-specific and lets you choose between Days and Hours.

Custom duration

Custom duration is a computed duration value, calculated as the time elapsed between any two date/date-time fields or between a date/date-time field and now.

  1. Select the Custom duration option in the Base value drop-down menu to create a custom value based on a custom duration.
    The option is available under the Duration (computed) category:

  1. Select the Start and End, which can be a date/date-time field or the Current time.
    If the selected date/date-time field can be empty, an extra checkbox becomes available in the selection window, allowing the current day to be used instead of an empty value:

Need support? Create a request with our support team.

Copyright © 2005 - 2026 Appfire | All rights reserved.