Automatically Link PIR Reference Back to Incident When PIR is Created via "Add PIR" Action

Question

When an agent manually creates a PIR using "Add PIR " from an incident or major Incident,the PIR already displays the originating incidents as its Primary Incident.However ,the incident does not display the PIR reference . how can i set automation for that .to link that created PIR.

Sarah Marenchino | Devoteam · Answer

Thanks Arkadiusz for pointing to the REST API.

I'd like to clarify one point from my earlier suggestion.

I haven't confirmed that the Primary Incident relationship created by the native "Add PIR" action is exposed as a standard Jira issue link. Therefore, the "Linked work items" branch I suggested should be considered a possibility to verify, not a confirmed solution.

Atlassian's Incidents REST API provides a Get primary incident endpoint. This could help retrieve the originating incident from the PIR.

However, retrieving that association does not automatically display the PIR reference on the originating incident. An additional step would be required, and the complete automation would need to be tested.

There is also a related feature request, AUTO-727, concerning native Automation support for setting the Primary Incident relationship. It remains unresolved, although it addresses a slightly different requirement.

Kirti, would a custom field or comment containing the PIR key meet your needs, or do you specifically need a clickable issue link?

Arkadiusz Wroblewski · Answer

Hey @Kirti Cloud Administrator Rajput

Did you looked on REST API for that ?

https://developer.atlassian.com/cloud/incidents/rest/api-group-post-incident-review/

Sarah Marenchino | Devoteam · Answer

Hi Kirti,

Since the "Add PIR" action already associates the originating incident as the Primary Incident, I would suggest reusing that existing relationship rather than trying to recreate it.

You could test the following automation:

* Trigger: Work item created.
* Condition: Work item type = Post-incident review.
* Branch: Linked work items, using the "reviews / is reviewed by" relationship, if exposed.
* Action: Update a dedicated custom field on the originating incident with the PIR key ({{triggerIssue.key}}).

Alternatively, you could add a comment containing the PIR reference.

One important point: I'd first verify how the Primary Incident relationship is exposed to Jira Automation. If it isn't accessible as a standard issue link, this approach would require a different mechanism.

Hope this helps!