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
The issue.internal function returns all internal issues that the user has JIRA permissions to browse. It doesn't apply additional logic, but returns all issues that fall under the internal category.
| Code Block |
|---|
issue.internal = 'true' |
Tempo Team
The Tempo Team function allows you to search for issues that have a specific Tempo Team set in the Tempo Team custom field by team name
| Code Block |
|---|
"Tempo Team" = "Team Name" |
Tempo Team id
The Tempo Team.id function allows you to search for issues with a specific Tempo Team set in the Tempo Team custom field.
| Code Block |
|---|
"Tempo Team.id" = team_id |
Team Projects
The project.teamName function allows you to search for issues in projects that are linked to a specific team
| Code Block |
|---|
The project.teamName function allows you to search for issues in projects that are linked to a specific team |
Tempo Team program
The Tempo Team.program function allows you to search for issues that have a specific Tempo Team, (which is assigned to a selected Program) set in the Tempo Team custom field.
| Code Block |
|---|
"Tempo Team.program" = "Program_name" |
Account
The Account function returns all JIRA issues that have been set to the account that matches the key used.
| Code Block |
|---|
Account = "Account_name" |
Accounts by customer
Account.customer returns all JIRA issues set to accounts for a specific customer. With this function, you can find all issues for a specific customer or create a custom filter based on a customer that can be used to generate custom reports. It is possible to use the name, id or key to query for this information.
| Code Block |
|---|
Account.customer = "Name of Customer" Account.customer.id = account_id Account.customer.key = account_key |
Accounts by category
Account.category returns all issues that have an Account as well as custom field(s) with an assigned Category. Likewise, it enables you to group JIRA issues by the account categories that exist for your accounts. This includes Development, Internal Cost or Billable. It is possible to use the name or key to query for this information.
| Code Block |
|---|
Account.category = "Category_name" Account.category.key = category_key |
Accounts by category type
The Account.category.type function enables you to group JIRA issues by their account category types. The account category types are: Billable, Capitalized, Internal and Operational. The query returns all issues with Accounts belonging to the Category Type selected.
| Code Block |
|---|
Account.category.type = "Billable" |
Accounts by status
The Account.status function enables you to group JIRA issues based on their account status. Accounts can have one of three statuses: Open, Closed or Archived. The value input to the function is the name of the status.
| Code Block |
|---|
Account.status = "OPEN" |
Global accounts
The last JQL function for accounts is for global accounts. Global accounts are accounts that are not related to specific projects and can be associated with any issue in JIRA. If set to "true" this function returns a list of issues set to global account(s).
| Code Block |
|---|
Account.global = 'true' |