The following custom JQL functions enable you to expand your search in Jira:
- linkedIssuesHasStatuses
- commentedIssues
- userCommentedIssuesgroupCommentedIssues
- _AMU - Using JQL functions
- membersOfProjectRole
- issuesSubtasks
- issuesParents
- transitionDate
- transitionReporter
- transitionReporterGroup
- transitionCount
- areNotBlocked
- relatedIssuesByField
- relatedIssuesByQuery
...
JQL functions | Description | Examples |
---|---|---|
commentedIssues(timeframe) | Returns issues that have been commented by a currently logged in user within the specified time frame. To perform such search, you must have the "browse issues" rights. |
|
issuesParents(JQLquery) | Returns a list of issues that are parents of all issues inside the specified JQL query. | issue in issuesParents("Project = PRDT") |
issuesSubtasks(JQLquery) | The issuesSubtasks function returns a list of issues that are subtasks of all issues in the specified JQL query. | issue in issuesSubtasks("Project = PRDT") |
linkedIssuesHasStatuses(Status, linkingType) | Returns tickets that have linked issues which are in the specified status and that are linked with the specified linking type. For example, you have a ticket A, and it's cloned by ticket B which is in progress. The following: issue in linkedIssuesHasStatuses("In Progress", "clones") will search for the tickets that
...and then it will display the tickets that this ticket B clones, in our case this is ticket A. |
|
membersOfProjectRole(Group) | Returns the users who are the members of a certain role inside the Jira project. |
|
transitionCount(Project, Status, Count, Operation) | This JQL function enables you to get a list of tickets in the specified project (first parameter) that were in a certain status (second parameter), X amount of times (third parameter) with a certain operation (fourth parameter - possible options">", "<", "=", ">=", "<=", "<>"). |
|
transitionDate(Duration, Status) | This function returns a list of tickets for which the status was changed within the specified time frame (first parameter) to the specified status (second parameter). For example, "2h" would mean within the last 2 hours. |
|
transitionReporter(User, Status) | Returns a list of issues where the status was changed by the specified user (first parameter) to the specified status (second parameter). |
|
transitionReporterGroup(Group, Status) | Returns a list of issues that were transitioned by anyone from the specified group (first parameter) to the specified status (second parameter). |
|
userCommentedIssues(User, Duration) | Returns the issues that have been commented by a particular user within the specified time frame, for example, within the last 5 hours. To perform such search, you must have "browse issues" rights. See example below |
|
groupCommentedIssues(User, Duration) | Returns the issues that have been commented by a particular group within the specified time frame, for example, within the last 5 hours. To perform such search, you must have "browse issues" rights. |
|
relatedIssuesByField(query, customFieldId) | Returns issues that contain issue keys of other issues in the specified field. |
|
relatedIssuesByQuery (query1, query2) | Allows to apply Query2 for the Query1 results. It returns issues according to the following algorithm:
| JQL 1 = "project = TEST and assignee = test" relatedIssuesByQuery("project = TEST and assignee = test", "key = SELF_VALUE and AND \"Start Date\" > startOfDay()") JQL 1 starts running inside the function and, for instance, will find the following tasks: Then, it will perform the following calls and accumulate the results. |
Examples
Finding user's commented tickets
...