Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-25344

Allow JQL to query other Atlassian products

This issue is archived. You can view it, but you can't modify it. Learn more

      Sometimes it is helpful to look for issues in Jira that have certain relationship between other elements in other Atlassian products. For example, doing a search to list all Jira issues that do not have a Crucible code review associated with them. As I understand it this is not currently possible.

      Where one of the strengths / selling points of Atlassian products is their integration with Jira this seems like a logical extension to the current JQL APIs.

            [JRASERVER-25344] Allow JQL to query other Atlassian products

            Yes, odd that the more general request "link to Atlassian products" is a sub-task of a more specific request "link to BitBucket"

            Like Fernando above, I came here looking for how to find all Jira issues linked to a particular Confluence page.

            John Dunkelberg added a comment - Yes, odd that the more general request "link to Atlassian products" is a sub-task of a more specific request "link to BitBucket" Like Fernando above, I came here looking for how to find all Jira issues linked to a particular Confluence page.

            It would be helpful if the REST API had the option for retrieving the confluence links of an issue, allowing to list all the issues and their related spaces.

            Fernando Ramos Castillo (Inactive) added a comment - It would be helpful if the REST API had the option for retrieving the confluence links of an issue, allowing to list all the issues and their related spaces.

            Charles Albrecht added a comment - - edited

            It would be helpful if the REST API had a way of listing all issue.property values associated with an issue so we're not stuck randomly trying strings to see whether they return any results.

            Looks like these definitions are stored in the entity_property_index_document table. In my installation, these six properties are defined:

            com.atlassian.jira.plugins.jira-development-integration-plugin : jira-issue-fusion-jql
            <?xml version="1.0" encoding="UTF-8"?>
            <index-document-configuration entity-key="IssueProperty">
            	<key property-key="development">
            		<extract path="failingbuilds" type="NUMBER" />
            		<extract path="openprs" type="NUMBER" />
            		<extract path="prs" type="NUMBER" />
            		<extract path="reviews" type="NUMBER" />
            		<extract path="openreviews" type="NUMBER" />
            		<extract path="commits" type="NUMBER" />
            	</key>
            </index-document-configuration>
            

            Charles Albrecht added a comment - - edited It would be helpful if the REST API had a way of listing all issue.property values associated with an issue so we're not stuck randomly trying strings to see whether they return any results. Looks like these definitions are stored in the entity_property_index_document table. In my installation, these six properties are defined: com.atlassian.jira.plugins.jira-development-integration-plugin : jira-issue-fusion-jql <?xml version= "1.0" encoding= "UTF-8" ?> <index-document-configuration entity-key= "IssueProperty" > <key property-key= "development" > <extract path= "failingbuilds" type= "NUMBER" /> <extract path= "openprs" type= "NUMBER" /> <extract path= "prs" type= "NUMBER" /> <extract path= "reviews" type= "NUMBER" /> <extract path= "openreviews" type= "NUMBER" /> <extract path= "commits" type= "NUMBER" /> </key> </index-document-configuration>

            It seems as if Atlassian has actually done something approaching this and not told anybody - see https://medium.com/@agile.umer/jira-searching-for-tickets-that-have-been-commited-to-a-development-branch-e6a2221bea07.

            CHD CM Support added a comment - It seems as if Atlassian has actually done something approaching this and not told anybody - see  https://medium.com/@agile.umer/jira-searching-for-tickets-that-have-been-commited-to-a-development-branch-e6a2221bea07 .

            Matthew Korich added a comment - - edited

            Please see JRA-62190 as a more focused version of this ticket. Thanks Cameron.

            Matthew Korich added a comment - - edited Please see JRA-62190 as a more focused version of this ticket. Thanks Cameron.

            Wanted to point out to other watchers that this issue is a subtask of a closed issue, because I didn't notice the first time I visited. This seems to mean that Atlassian has no intention of addressing this.

            Cameron Ackerman added a comment - Wanted to point out to other watchers that this issue is a subtask of a closed issue, because I didn't notice the first time I visited. This seems to mean that Atlassian has no intention of addressing this.

            Leslie and Jimmy Wood added a comment - - edited

            We are using the SAFe Agile methodology and this feature is greatly desired for our release report. We are currently doing this by hand. Each root issue (not sub task) is displayed in a query and then someone manually goes through and creates a report of code review coverage (which issues have completed code reviews in crucible).

            Leslie and Jimmy Wood added a comment - - edited We are using the SAFe Agile methodology and this feature is greatly desired for our release report. We are currently doing this by hand. Each root issue (not sub task) is displayed in a query and then someone manually goes through and creates a report of code review coverage (which issues have completed code reviews in crucible).

            Hello!
            We also vote for this issue.

            Pavel Luksha added a comment - Hello! We also vote for this issue.

            Voting for this issue to be addressed. Need to be able to JQL commits per user.

            peter_pantilla added a comment - Voting for this issue to be addressed. Need to be able to JQL commits per user.

            patricia.a.nadolsky added a comment -

            We also have a similar requirement so would like its implementation.

            patricia.a.nadolsky added a comment - We also have a similar requirement so would like its implementation.

              Unassigned Unassigned
              21f1f889e3a1 Kevin Phillips
              Archiver:
              mandreacchio Michael Andreacchio

                Created:
                Updated:
                Archived: