Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 time spent 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:

  1. Navigate to the Epics filter option within the Issue Filter tab.

  2. 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.

  3. 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.

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.

  1. 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.

  2. 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.

Expand
titleJQL which can help you to define the scope
  • Track all tasks currently assigned to a specific team member.
    assignee = "username"

  • Get a list of all issues that haven't been completed or resolved.
    resolution = Unresolved

  • Review recent tasks to prioritize or assess workload.
    created >= -7d

  • Identify tasks that are past their due date and need urgent attention.
    due <= now() AND resolution = Unresolved

  • Monitor recent activity and changes to issues.
    updated >= -1d

  • Focus on all tasks under a particular Epic to track progress.
    "Epic Link" = "EPIC-123"

  • Filter for high-priority tasks that need immediate attention.
    priority = "High"

  • See all tasks that are currently being worked on.
    status = "In Progress"

  • Identify issues that are blocking other tasks, which may require immediate resolution.
    issueFunction in hasLinkType("blocks")

  • Review recent work completion to evaluate team performance.
    resolved >= -30d