You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I'd like to find all open issues that have a merged PR in order to find tickets that might have been forgotten to be resolved and therefore will probably ship to production untested.
JQL has the two terms `development[pullrequests].open` and `development[pullrequests].open`, but unfortunately no means to filter out `declined` PRs. So when I do `status not in (Closed, Resolved) AND development[pullrequests].all > 0 AND development[pullrequests].open = 0`, I will get both issues with `merged` and `declined` PRs. I'd like to only get the ones with `merged` PRs.
Is that possible somehow? If not, could this be added to JQL?
For Jira Software Server 7.8+ you can find the full list of available development fields here - https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-fields-reference-939938743.html
To find all the issues only with merged pull requests I recommend using the following filter:
development[pullrequests].merged > 0 AND development[pullrequests].open = 0 AND development[pullrequests].declined = 0
@[deleted] The list of fields available in Jira Cloud is different from Jira Server.
As of May 2019, Jira Cloud doesn't support development[pullrequests].merged field.
Here is full search reference for Jira Cloud - https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-developer-reference-967312910.html
@FinAdmin That only works if PRs are never declined. If there are multiple rounds of PRs that get declined and none ever gets merged, your query will return that result.
Above @Anton Genkin mentioned that Jira Server supports .merged but Jira Cloud does not. I presume you ran your test on Jira Cloud.
It's been 1.5 years, @Anton Genkin can we get .declined and .merged in Jira Cloud soon?
Jira is a big, fat company. They have the market share such that their product managers don't have to worry about keeping customers happy. Thus, if it takes five years to implement something that should take five minutes, it takes five years! And you'll sit there and like it!
It seems like this behaviour matches what is described on the following feature request (this is the Jira Server version):
If that's the case, feel free to comment on the feature request to share with the Jira team the use cases for this request.
Caterina - Atlassian