Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to find Issues with Merged PR

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?

3 answers

2 accepted

5 votes
Answer accepted
Anton Genkin Atlassian Team May 13, 2019

Hi @Fabian Ehrentraud 

For Jira Software Server 7.8+ you can find the full list of available development fields here - 

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

nice that `merged` now exists! but i'd not filter for `declined = 0`, because it could be that 2 PRs were created for a ticket, one declined and one merged, and these tickets should still show up.

Like joshuaryanwhite likes this

@Anton Genkin How do you do this in Jira Cloud? When I try to use development[pullrequests].merged > 0 I get the following error.

For "development[pullrequests]" use "development[pullrequests].all" or "development[pullrequests].open"

Like # people like this

@[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 -

@Anton Genkin Do you know if the merged field is on the roadmap for Jira Cloud ?

Like # people like this


@Anton it would be very nice to have development[pullrequests].declined and .merged in Jira Cloud.  Any ETA?

Like # people like this

WHY all of you is saying that this exists, it DOESN'T



For anyone searching to find merge PRs only: 

development[pullrequests].all > 0 AND development[pullrequests].open = 0


it will include the merged and declined tho, there's no other way.



Like # people like this

@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?

Like # people like this

And it has been 6 more months. How about we get .merged in Jira Cloud now?😜

Like # people like this

And it has been 3 more months. How about we get .merged in Jira Cloud now?

Like # people like this

development[pullrequests].open > 0

This works, but not merged or declined, still looking to know how to filter for these, in case anyone knows

Like CKinKC likes this

Same, is anyone aware of a feature request for this.  It's very frustrating, thank you!

9 months later. How about we get .merged in Jira Cloud now?

0 votes
Answer accepted

Hi @Fabian Ehrentraud,

It seems like this behaviour matches what is described on the following feature request (this is the Jira Server version):

JQL Entity Property for Pull Request Status


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

Thank you, that indeed looks like a feature request for what I try to do. Too bad that it is not possible yet.

Thanks Fabian for commenting on the feature request. Really appreciated!

Having status property is a should have feature,
I guess atlassian removed it for a purpose

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events