Refining a Folio scope by using a JQL filter

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

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.

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.

If you want to only include certain issue types like Epic and Story, and not include other issue types like Bug and Support, this will solve that use case.

Note: it is safer to search by type ID than type name. It is possible for your Jira administrator to change the name of a type, which could break any saved filter that rely on that name. Type IDs, however, are unique and cannot be changed.

If you only want to pull in issues that have time logged on them already, this is the filter you need.

You need to be aware that if you are at the beginning of the project, then the Progress bar will not show you the entirety of the work that must be accomplished, but in some cases this may be purposeful.

If you only want to pull in issues that have a specific Tempo Team, this is the filter you need.

See documentation for how to add Team to your issues.

If you only want to exclude issues that were resolved prior to the start of your Folio, this is the filter you need. You can use this instead of the Date created if you need to make sure that issues that are still in progress are included in the Folio

If you only want to include only issues that have been worked on by a certain Team or Jira group like jira-administrators, then you can use this to narrow down the scope of the Folio.

If you only want to include only issues that belong to an open account, then you can use this JQL.

If you want to make sure your scope includes multiple criteria, e.g. issues in a certain project, of a certain issue type, and created in 2020, you need to use the operator AND to connect all these statements in your JQL.

project in (“Development”, “Apps”) AND issueType in (Epic,Story) AND (created > "2020/01/01" and created < "2020/12/31")