To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Refining a Folio scope by using a JQL filter

Owned by Carolyn French (Deactivated)
Last updated: Apr 01, 2024 by Jaramy Conners

Whenever possible, defining the Folio scope by using a JQL filter gives you the most flexibility to hone in on the relevant issues for your Folio, which will reduce the number of issues the Folio pulls in, and improve performance down the line.

How to create a JQL filter: https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14

JQL Options & Implications

  • By Project

This is the most commonly used type of filtering to find relevant issues.

  • Find issues that belong to the Project that has the name "ABC Project":
    project = "ABC Project"

  • Find issues that belong to the project that has the key "ABC":
    project = "ABC"

  • Find issues that belong to the project that has the ID "1234":
    project = 1234

  • By date created

If your project has issues since the beginning of time, you can start by limiting it to issues created in the last year, for example.

  • Find all issues created before 12th December 2010:
    created < "2010/12/12"

  • Find all issues created on or before 12th December 2010:
    created <= "2010/12/13"

  • Find all issues created on 12th December 2010 before 2:00pm:
    created > "2010/12/12" and created < "2010/12/12 14:00" 

  • Find issues created less than one day ago:
    created > "-1d"

  • Find issues created in January 2011:
    created > "2011/01/01" and created < "2011/02/01"

  • Find issues created on 15 January 2011:
    created > "2011/01/15" and created < "2011/01/16"

  • By custom field

If you have a custom field that you use to organize all the issues that are relevant to the folio, this might be useful to you.

Note: it is safer to search by custom field ID than by custom field name. It is possible for a custom field to have the same name as a built-in Jira system field; in which case, Jira will search for the system field (not your custom field). It is also possible for your Jira administrator to change the name of a custom field, which could break any saved filters that rely on that name. Custom field IDs, however, are unique and cannot be changed.

  • Find issues where the value of the "Location" custom field is "New York":
    location = "New York"

  • Find issues where the value of the custom field with ID 10003 is "New York":
    cf[10003] = "New York"

  • Find issues where the value of the "Location" custom field is "London" or "Milan" or "Paris":
    cf[10003] in ("London", "Milan", "Paris")

  • Find issues where the "Location" custom field has no value:
    location != empty

  • By Issue Type

  • Find issues with an issue type of "Bug":
    type = Bug

  • Find issues with an issue type of "Bug" or "Improvement":
    issueType in (Bug,Improvement)

  • Find issues with an issue type ID of 2:
    issueType = 2

  • By Time spent

  • Find issues where the time is logged:

timeSpent is not empty

timeSpent > 0

  • By Team

  • By Resolution Date

  • By Worklog Author

  • By Account

See JQL documentation for more information: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/

For more details about Tempo specific JQL: https://tempo-io.atlassian.net/wiki/spaces/KB/pages/383518497