JQL functions

The app adds two functions to Jira's JQL. They work in the issue navigator, saved filters, boards, dashboards, JSM queues and Automation.

Both are used with the issue in ... form, which is how Jira exposes app-provided functions.

teamIn()

Find issues whose Team matches one or more team names, without pasting team ids.

issue in teamIn("Payments")
issue in teamIn("Payments", "Checkout", "Risk")
issue in teamIn("Platform*")          -- every team whose name starts with Platform
issue not in teamIn("Payments")       -- everything except that team

Rules

• Names are matched case-insensitively against the team's display name.
• A trailing * matches by prefix.
• A team id (the UUID from the team's URL) is accepted instead of a name.
• If no team matches, JQL shows an error naming the unmatched value.
• The team list is cached for ten minutes; a team renamed in the last few minutes may still resolve by the old name.

noTeam()

Find issues with an empty Team field.

issue in noTeam()
issue in noTeam() AND statusCategory != Done
issue not in noTeam()                 -- issues that do have a team

Where to use them

• Boards: board filter project = ABC AND issue in teamIn("Checkout").
• JSM queues: issue in teamIn("Tier 2 Support") AND status = Open.
• Automation: JQL condition or scheduled trigger, for example a weekly rule that flags issue in noTeam().
• Dashboards: any filter-based gadget, including the app's Team Statistics gadget.

Coming next

myTeams() (issues for every team you belong to) is planned. See Known limitations for why it depends on an Atlassian platform change.

Was this page helpful? Email support@mortiseapps.com.