When using the advanced searching options within JQL of Jira Cloud, there exist a number of development functions you can use to search for Jira issues that might have pull requests, commits, branches, and builds. More details in Advanced searching - developer reference - Atlassian Documentation
Source code searches
You can search for issues based on the your development status:
- development[pullrequests].all (or .open)
- development[reviews].all (or .open)
However these do not appear to ever return any issues that exist in next-gen projects.
- Link a Jira Cloud site to a Bitbucket repo via the DVCS connector
- Create a next-gen scrum project
- create a sample issue in that project, for example let's say it's NEX-3 is the issuekey for one issue in that project
- In Bitbucket, create a commit and enter that issuekey (NEX-3) in the commit message
- You can confirm by visiting the Jira issue directly that this development info is linked to the correct issue. That part is working as expected.
- Then go to the issue navigator in Jira Cloud, [yourCloudURL].atlassian.net/issues/ to search under advanced searching for a JQL query such as
JQL results should return at least one issue
JQL returns 0 issues from next-gen projects
Currently there is no known workaround for this behavior. A workaround will be added here when available