How to find PR identifier and URL associated with a Jira Issue

[Alex Kidd]

My goal is to build a hierarchy that groups all issues associated with a feature, something along the lines of this:

1. Feature-1
   • Epic-1
     • Task-1
     • Task-2
     • Task-3
     • Task-4
       • PR-a
   • Epic-2
     • Task-8
       • PR-b
     • Task-9
       • PR-c
     • Task-10
       • PR-d
   • Epic-3
     • Task-20
     • Task-21
       • PR-e
     • Task-30
2. Feature-2 
   • Epic-10
     • Task-100
       • PR-aa
     • Task-101
       • PR-bb
     • Task-102
     • Task-103
       • PR-cc
   • Epic-2 
     • Task-200
       • PR-ee
     • Task-201
       • PR-ff
     • Task-203 
       • PR-gg

Have been able to do this for the Feature/Epic/Tasks (and sub-tasks), however I have not been able to find where I obtain the PR identifier and URL that Jira shows in the developer panel within Jira Issues that have an associated PR. I am familiar with the development[pullrequests]... JQL options, but have not been able to determine how I can obtain the identifier and URL for the associated PR.

Have been looking to accomplish this via JQL or via use of the Jira Cloud REST Api.

We are using Jira Cloud - so unfortunately ScriptRunner does not provide a solution.

Our SCM system is Git and we are using the Github application link (plug-in).

If the community knows how to accomplish this - please share - as my searches have not returned a solution.

[Alex Kidd]

Kristian,

Thank you for your response. I did indeed look into the linkedIssuesOfRecursiveLimited function. 

My challenge is the final step - in that I can locate the issues, and using the 'developer' information ascertain which issues have an associated PR.

My challenge, however, is that I am not able to locate the PR ( ID and Link ) information that is displaced when you open the Developer section of the ticket in the Jira Cloud UI. Any ideas as to how this can be exposed?

Regards,

Alex

[Kristian Walker _Adaptavist_]

Hi Alex,

Thank you for your question.

I can confirm that ScriptRunner for Jira Cloud does not provide the same portfolioChildrenOf() and portfolioParentOf() JQL functions that the server version provides in order out of the box in order to search for Portfolio issues as the API to provide this function does not exist in the Jira Cloud as it does in Jira Server. 

However I can confirm that the linkedIssuesOfRecursiveLimited enhanced search function which is documented here, may help you to run a JQL search to return all issues linked to a feature if you specified the names of the issue links, used to link the issues together.

If this response has answered your question can you please mark it as accepted so that other users can see it is correct when searching for similar answers.

Regards,

Kristian