There are two ways to display your data from JIRA in your Notion Dashboard:

  • Using the custom JQL Query template
  • Using one of our templates

Custom JQL query

JQL stands for JIRA Query Language, and it's a flexible way to search for issues in JIRA. JQL is very similar to SQL, and the advanced search box in JIRA provides with code suggestions and inline validation to make constructing queries easy. By using Notion to trend JQL results over time, you can easily pull together your metrics across sprint teams in one place. For an example, check out Getting Started with JIRA JQL Velocity.

If you are not familiar with JQLs, you can use the simple search in JIRA instead. With simple search, you only need to fill in a set of forms. Once you have made your selection, click on the "advanced search" and your JQL query will be there, ready for you!

Paste the JQL query from JIRA into your Notion template.

Give your recipe a name that makes it clear to everyone on your team what you are tracking. You can also include a brief description to help your team understand why you are tracking this.

It’s important to note that JQL searches typically return counts of tickets to Notion based on the search (e.g. number of tickets assigned to a team). Story Point JQLs are a special case. If your team uses Story Points in JIRA, Notion can sum the story points for you based on the search and the presence of the story point field.

By default the recipe is set to display daily values, and will update daily from JIRA. But you can select a new frequency of weekly, biweekly, monthly, quarterly, or yearly.

Finally, add the recipe to an existing dashboard or create a new one.

Our JQL recipes don’t currently fetch historical (previous) values, so it’s important to get set up to start tracking your information now.

Edit a JQL metric

After you create your metric using a JQL, it is possible to edit the query itself. To do so, find the metric in your directory or on your dashboard, click Edit and then Metric Settings.

From this view, you will be able to edit the JQL and hit Submit.

When your import runs next, it will start pulling results based on the new JQL. It will not fetch nor update any historical (previous) values.

JIRA template recipes

You can also choose one of the JIRA template recipes, which are pre-built formulas calculated by Notion to help you turn your data into actionable metrics.

Cycle Times by Issue Status

This recipe shows the average time (in days) that tickets spend in each status.

Add this to your dashboard to identify bottlenecks or trouble areas in your development team workflow. This helps to reduce disruption and the impact on efficiency, quality, and value.

Step 1: Recipe Settings

Each recipe template can be customized with a name and description to help your team understand why you are tracking this metric and what the data means.

Next, select the project you wish to pull data from. All your JIRA projects (include JIRA Service Desk projects) associated with your account will be listed in the Recipe template, though you can currently choose one at a time.

Finally, select the frequency (how often you want the value reported) for your metric. Values will update automatically based on the selected frequency.

Step 2: Template Settings

First, select all of the issue types you are interested in tracking. The calculated value will be the average time of all selected issues.

Second, select the issue states. A separate line will be displayed to represent the average time spent in each status selected.

Please note, Issue Types and Status will only appear for the selected project you have selected in Step 1

Step 3: Addition Options

If you use additional fields in JIRA—like labels and priorities—you can also use these to filter your data set. Check a box to expand the options.

Once you have finished with the setup, you can add this Recipe to a dashboard or create a new one.

Cycle Times by Issue Type

This recipe shows the average time (in days) that it takes tickets to move between two states.

Add this to your dashboard to measure productivity and consistency of ticket types moving through a your workflow. For example, if the cycle time for features (the time it takes to finish a ticket) is increasing each sprint, perhaps you need to break tickets down into smaller pieces.

Step 1: Recipe Settings

Each recipe template can be customized with a name and description to help your team understand why you are tracking this metric and what the data means.

Next, select the project you wish to pull data from. All your JIRA projects (include JIRA Service Desk projects) associated with your account will be listed in the Recipe template, though you can currently choose one at a time.

Finally, select the frequency (how often you want the value reported) for your metric. Values will update automatically based on the selected frequency.

Step 2: Template Settings

First, select all of the issue types you are interested in tracking. A separate line will be displayed for each issue type selected.

Second, select the starting and ending boundaries of your cycle time. For example, you may be interested to know how long it took for tickets to move from Open to Closed.

Step 3: Addition Options

If you use additional fields in JIRA—like labels and priorities—you can also use these to filter your data set. Check a box to expand the options.

Once you have finished with the setup, you can add this Recipe to a dashboard or create a new one.