Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

• Find issues where the Assignee is a member of the group "Jira-administrators":
  assignee in membersOfGroups("Jira-administrators", "Developers")

• Search through multiple groups and a specific user:
  reporter in membersOfGroups("Jira-administators") or reporter in membersOfGroups("Jira-core-users") or reporter=jsmith

• Search for a particular group, but exclude a particular member or members:
  assignee in membersOfGroups("Jira-core-users") and assignee not in ("John Smith","Jill Jones")

• Exclude members of a particular group:
  assignee not in membersOf("Jira-core-users")

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

• usersInRole(INTDEV, 'Developer')

• project in (INTDEV, DEV, MKT) and usersInRole('Developer') - projects use from query context

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Assignee, Reporter, Voter, Watcher, custom fields of type User

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Custom fields of type Group

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all groups that the user john.doe is a member of.

This query retrieves all groups for the currently logged-in user.

Parameters:

• user (optional) – The username or account ID of the user whose group memberships should be retrieved.

  • If omitted, it defaults to currentUser().

Use Cases:

• Finding user group memberships to manage permissions or team assignments.

• Creating dynamic queries that adjust based on a user's group membership.

• Filtering issues by teams or departments using group-based access control.

Custom fields of type Group

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all groups whose names start with "dev", such as "dev-team", "dev-ops", etc.

Parameters:

• pattern (required) – A string pattern to match group names.

  • Supports wildcards such as * (matches any characters) or ? (matches a single character).

Use Cases:

• Finding groups related to a specific team or function, for example, all groups starting with "dev" for development teams.

• Automating queries based on group naming conventions (e.g., "admin", "support").

• Managing group memberships by targeting groups with certain prefixes or keywords.

Component

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all components whose names start with "Backend", such as "Backend API", "Backend Services", etc.

Parameters:

• pattern (required) – A string pattern used to match component names.

  • The pattern can include wildcards such as * (matches any characters) or ? (matches a single character).

Use Cases:

• Finding components related to specific categories (e.g., components starting with "UI" or "API").

• Creating dynamic filters that automatically include new components following a naming pattern.

• Grouping similar components based on their names, which is useful for organizing large numbers of components.

Component

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all active components within the projects PRJ, INT, and DEV.

Parameters:

• 'PRJ', 'INT', 'DEV' (required) – A list of project keys for which you want to search for active components. You can include multiple project keys, separated by commas.

Use Cases:

• Finding active components in multiple projects for reporting or analysis.

• Filtering components that are still in use or need further action, like bug fixes or feature updates.

• Tracking current development work by focusing on active components in specific projects.

Custom fields of type Group

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all components that have been archived within the specified projects: PRJ, INT, and DEV.

Parameters:

• 'PRJ', 'INT', 'DEV' (required) – The list of project keys for which archived components should be searched. You can include multiple project keys, separated by commas.

Use Cases:

• Finding archived components in multiple projects for reporting or cleanup purposes.

• Tracking legacy components that may no longer be in active use but still exist in the system.

• Managing old or unused components in projects that have been archived or are no longer active.

Project

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all projects with names that begin with "HR", including examples like "HR System" and "HR Requests".

Parameters:

• pattern (required) – A string pattern used to match project names.

  • The pattern may incorporate wildcards such as * (which matches any sequence of characters) or ? (which matches a single character).

Use Cases:

• Identifying related projects that adhere to a specific naming convention (e.g., projects that begin with "Sales" or "Support").

• Developing dynamic filters that automatically incorporate new projects that follow an established naming pattern.

• Organizing similar projects without the necessity of manually enumerating them.

Project

IN , NOT IN

= , != , ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

This query retrieves all projects where the current user has the role "Developers".

Parameters:

• user (optional) – The username or account ID of the user. If omitted, it defaults to currentUser().

• projectRole (required) – The name of the project role (e.g., "Administrators", "Developers", "Testers").

Use Cases:

• Finding projects where a user has a specific role, such as an administrator or developer.

• Managing permissions by identifying which projects a user is assigned to.

• Creating reports for team-based project assignments.