Issue filter
- Tetiana Kamenkova (Deactivated)
- Olexiy Artemenko
The Issue Filter is designed to narrow down the data within the scope already defined by your selected Data Source. These filters do not expand the data set but rather focus it, allowing you to refine your analysis by zeroing in on specific criteria, such as issue types or estimation ranges.
The Issue Filter affects all three charts: Cycle Time Histogram, Time in Status Cycle Time, and Cycle Time Trend Charts.
Estimation field
Filter issues by the Estimation field and apply a range for more specific filtering.
Filter by Story Points or any other numeric field: you can filter issues within a specific range of story points. For example, you want to filter all issues estimated between 1 and 3 story points.
If only the "from" value is set, it will show all issues with an estimate greater than or equal to that value.
If only the "to" value is set, it will show all issues with an estimate less than or equal to that value.
Filter by Time Tracking fields: when filtering by time-based estimates, you can select a time unit (minutes, hours, days or weeks) and apply a range. For example, filter issues estimated between 15 minutes to 2 hours or 5 days to 2 weeks.
Use the following designations to specify the time unit:
m: minutes
h: hours
d: days
w: weeks
The Estimation field is added to the Issue list columns by default after selection. This column becomes unchangable. The column disappears if clear the Estimation field selection.
Gain insights of:
which cycle or lead time is associated with more complex issues,
planning the simple tasks delivery based on the past trends,
in which statuses issues with the most common estimates are getting stuck.
Issue type
The Issue Type setting allows you to customize which types of issues are included in your charts.
By default, Bug, Task, and Story are selected. Clear all predefined issue types to see all issues analyze.
However, you can add issue types from the dropdown menu or replace the default to tailor the data to your specific needs.
Imagine your team frequently creates the Spike issue type to explore and research potential solutions before implementation. Using the Issue Type setting, you can include Spikes in your analysis. This allows you to track the cycle or lead time on these exploratory tasks and assess their impact on the overall project timeline.
Epics
The Epics filter allows you to narrow down the data within your predefined scope by selecting specific Epics. Here’s how it works:
Navigate to the Epics filter option within the Issue Filter tab.
From the dropdown list, you can choose one or more Epics that you want to include in your analysis. This list is based on the data scope you previously defined in the Data Source settings.
Once you’ve selected the relevant Epics, the chart will update to display only the issues associated with those Epics, refining your analysis to focus on specific aspects of your project.
The filter gives you precise control over your data, allowing you to zero in on the most relevant parts of your workflow by filtering the data to include only the Epics that matter most to your analysis.
Exclude issues
Select the issues you want to remove from the calculation by using multi-select field, where you can search by issue key:
JQL filter
The JQL Filter within the Issue Filter settings allows you to apply specific filters to further narrow down the data scope that was defined earlier in the Data Source settings.
Use the JQL (Jira Query Language) field to input a custom query. This lets you apply highly specific criteria to filter the issues, such as finding all issues assigned to a particular user or those that meet certain status conditions.
Once your JQL query is entered, the chart will update to reflect only the issues that match your query, refining the previously selected data scope to focus on exactly what you need to analyze.
It provides powerful flexibility, allowing you to tailor your analysis to any specific requirement or scenario, ensuring that the data you work with is as relevant and targeted as possible.