Quality standard

Quality standard

A Quality standard is a (set of) criteria for an Issue to be considered of good quality. A Quality standard is defined by:

  • Name: the name of the standard

  • Condition: the (JQL) criteria for the Issue to be considered good quality

  • Scope: an optional filtering to only apply the standard to issues with certain properties

  • Documentation: an optional link to more information about the standard

An example of a Quality standard can be:

  • Name: Stories musth have a parent Epic as soon as they are in Progress

  • Condition: parent IS NOT EMPTY

  • Scope: type = Story and statusCategory != “To Do”

image-20250303-102547.png
Standard properties when viewing an issue

Global or Project standards

A Quality standard can be set on Global or Project level. A Quality standard can be set on a Global level by a Jira Administrator. These rules will apply to all Projects in Jira (but can be limited by setting their ‘scope’).

Project Administrators can define and manage Quality standards on a Project level. These standards will only apply to the issues within their project.

If you want to set a standard for a set of projects, a Jira Administrator can create the standard globally, but use the ‘Scope’ to limit the standard to only a set of projects (or a project category) by using JQL. See ‘Scope’ below.

Name

The name is a short descriptive title for the Quality standard. It will be displayed in the Quality standard scores when viewing an issue.

Condition

The condition is the (set of) criteria for an Issue to be considered of good quality. It is defined using Jira Query Language (JQL).

More information about this can be found here: Setting conditions and scope using JQL

Scope

Some rules might not apply to all issues. The ‘Scope’ allows you to restrict the scope to which issues the standard applies. Same as with Condition, this is done using JQL. For example:

You only want the standard to apply to Bugs

Scope: type = Bug

You don’t want the rule to apply to sub-task issue types

Scope: type not in subTaskIssueTypes()

More information about this can also be found here: Setting conditions and scope using JQL

Documentation

You can optionally provide a link to more information about the standard. Maybe you have some policy you want to refer to. Or you have a Confluence page where your organisation has published relevant information.

When a documentation link is provided, a icon is displayed in the Quality standard scores when viewing an issue. When a user clicks the icon, a new window (or tab) will open and direct the user to the link.