/
Issue filter

Issue filter

Applies to

Navigation

Left panel > Issue filter

You can refine the chart scope by filtering issues to match your workflow and needs.

Estimation field

Filter issues by the selected Estimation field to narrow down your analysis by complexity or effort. You can filter issues using any numeric field (for example, Story Points or Original Estimate) and specify a range.

  • If only the From value is set, the chart only shows issues with an estimate greater than or equal to that value.

  • If only the To value is set, the chart only includes issues with an estimate less than or equal to that value.

image-20251006-173755.png

Use this filter to gain insights into:

  • how cycle or lead time changes with issue complexity,

  • delivery pace for simple tasks based on past performance,

  • which workflow stages tend to delay the most complex work items.

Story points or numeric estimates

Filter issues estimated within a specific range of story points or another numeric value. In the example below, the graph displays work items estimated at 5 story points or higher:

image-20251006-174140.png

Time-tracking estimates

When filtering by time spent, you can apply a time unit and range.

Time unit designations:

  • m — minutes

  • h — hours

  • d — days

  • w — weeks

If Time spent is selected as the Estimation field, a corresponding column is automatically added to the Issue list and remains fixed until the field selection is cleared. In the example below, the graph displays work items that took between 3 days and 1 week:

image-20251006-174846.png

Issue types

Filter by stories, bugs, tasks, sub-tasks, or any other issue type available in your Jira instance. Select one or multiple specific issue types, all standard types, and/or all sub-tasks.

image-20251006-175256.png

Epics

Include only issues from selected epic(s).

The filter searches only the direct child issues of the epic, not deeper levels.

image-20251006-175353.png

Exclude issues

Exclude specific issues from the chart calculations. This is useful when you want to remove outliers, test items, or work items that could distort average cycle or lead time values.

Select one or more issues manually, or start typing an issue key to search and exclude it from the analysis:

image-20251006-180045.png

Releases

Select a project and one or more fix versions within it. To include versions from other projects, click Add release.

image-20251006-175604.png

Custom JQL filter

Use this option for maximum flexibility. Extended JQL functions from other apps (e.g., ScriptRunner) are also supported.

Possible use cases

  • Filter issues by assignee: assignee = "Joe Alpha"

  • Filter by team when teams are defined in a Component field: component = “Component 1.1”

  • Filter by label: labels = "PI-2024-Q3" to show all issues tagged for a specific Program Increment.

  • Filter by issue priority: priority in (Highest, High) to focus on critical work.

image-20251006-175734.png

Fast-expired JQL

The app caches all closed sprint reports because they are usually permanent entities. However, when using dynamic JQL functions, results may expire immediately because the values change over time.

Examples of fast-expired JQL expressions:

  • "Time to resolution" < remaining("2h")

  • created <= -5d

  • changed <= -5d

  • "Time to first response" < elapsed("10m")

You can reset the cache at any time by clicking ⋯ (three dots) > Reset cache at the top of the chart.

image-20250904-082221.png

 

When copying a JQL filter from another source, check whether it uses a fast-expired JQL function.