Tempo JQL functions for Jira advanced search
By using JQL functions, you can include Tempo data in the JIRA advanced search. This includes a range of data, from Tempo Teams and Accounts to internal issues.
Internal Issues
This function returns all internal issues, that the user has JIRA permissions to browse.
It doesn't take any arguments, simply returns all issues that fall under the category of being internal.
|
Teams
Team
The team function allows you to search for team members, that are for example either the JIRA issue assignee or reporter.
It takes the team name as argument.
|
|
Team Role
The team role function allows you to search for issues where a selected Team role has been set
"Team Role" = "Name of Team role" |
Team Projects
The teamProjects() returns a list of issues, in projects linked to the searched team(s). The function can take parameter(s), as either team Id or team name. Insert one or many, separated by a comma ",".
project in teamProjects("Name of the team") |
Program Projects
The programProjects() returns a list of issues based on searched program(s), where the restricting factor is the projects linked to team(s). These projects can also be linked to teams not in the searched program(s), giving different result than for programTeams above. The function can take parameter(s), as either program Id or program name. Insert one or many,
separated by a comma ",".
|
Program Teams
The programTeams() returns a list of issues based on searched programs, where the restricting factor is the team(s) in the program(s). The issues must be associated to the team(s) through the Team Custom field and they are therefore independent of the projects linked to team(s). The function can take parameter(s), as either program Id or program name. Insert one or many, separated by a comma ",".
|
Epics
The function tempoEpicIssues, makes it possible to search for issues that are of type Epic and return all stories that are assigned to the Epic.
It takes the issue key of the Epic as an argument and returns all of it's stories and sub-tasks.
|
Accounts
Account Key
This returns all JIRA issues that have been set to the account that matches the key used.
Account = "account key" |
Example: Account = 23456
Accounts by Customer
The accountsByCustomer() returns all JIRA issues set to accounts for a specific customer. With this function you can find all open issues for a specific customer or create a custom filter based on several customers that can be used to generate custom reports.The value input(s) to the function, is the configured key or name (not case sensitive) for the customer. Insert one or many, separated by a comma ",".
|
Accounts by Category
Account in accountsByCategory("*") - Returns all issues that have an Account in customfield that has an assigned Category. Like wise, Account in accountsByCategory() enables you to group JIRA issues on account categories, that exist for your accounts. Examples are: Development, Internal Cost or Billable.The value input(s) to the function, is the configured key or name (not case sensitive) for the category. Insert one or many, separated by a comma ",".
|
Please note: the filter will return all the issues that are linked to an account that have a category with the word used in the search. For example: if there are different account categories called "billing1", "billing2" and "billed" and you use the filter to search for the category "bill", the result will return all the categories that have "bill" in their names, in the case of this example, it would return all the issues that are linked to accounts in categories "billing1", "billing2" and "billed".
Accounts by Category Type
The accountsByCategoryType(), enables you to group JIRA issues on account category types. The account category types are: Billable, Capitalize, Internal and Operational.Account in accountsByCategoryType(Capitalized) - Returns all issues with Accounts belonging to the Category Type "Capitalized"Account in accountsByCategoryType("*") - Returns all issues that have an Account in customfield that has an assigned Category with a Category TypeThe value input(s) to the function, is the name (not case sensitive) for the category type. Insert one or many, separated by a comma ",".
|
Accounts by Project
For accounts that have many linked projects, it is useful to get all issues set to accounts for specific projects. This is possible with the accountsByProject() function. The value input(s) to the function, is the JIRA project key.
|
Accounts by Status
The accountsByStatus(), enables you to group JIRA issues on account status. Account can have one of three statuses: Open, Closed and Archived.
The value input(s) to the function, is the name (not case sensitive) for the status. Insert one or many, separated by a comma ",".
|
Global Accounts
The last JQL function for accounts, is for the global accounts. Global accounts, are accounts that are not related to specific projects and can be associated with any issue in JIRA. This function returns a list of issues set to global account(s).
Account IN globalAccounts() |