Is there a way of accessing the Primary incident link via automation?

[Curt Holley]

It would be great to generate a PIR where the 

Primary incident field is populated as part of the creation (via automation).

But is that possible currently?

[Ste404]

ah came here looking for the same thing.  I can 'link' a Major issue via some automation but I want it to be the Primary Incident, surely this can be picked out in automation somewhere.

It's not a custom field so can't jam a smart value into it.

This has to be achievable, linking a PIR to a primary incident seems logical!

[Bill Sheboy]

Hi @Curt Holley 

Have you tried using the how-to article below to identify the smart value of the field?  My understanding is that if the smart value is present, it can at least be edited with JSON using advanced edit.  And if it is absent it is not yet supported.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Curt Holley]

Thanks @Bill Sheboy 
Good call. Though I'm having issues accessing the API currently.
But, it isn't a JQL searchable field. Can't find it in Custom fields , Issue linking....
So I'm doubting it 🫤

[Simmo]

Not sure I really understand the question here? There is a particular field that you want to populate?

[Curt Holley]

Yeah @Simmo The "primary incident" field that is only part of the Post Incident Review" issue type in JSM.

[Simmo]

Right and thats not appearing in the Create issue field list?

[Michael Verdun Heath]

I'd like an answer to this too.  No it doesn't appear in the Create issue field list.  I believe it's not a true field, but some kind of way linked issues are worked.  The incident ticket specified gets linked as "is reviewed by", and on the PIR it shows as a link type of "Primary Incident" (this link type doesn't actually exist)... adding links alone doesn't do the trick. So what are we missing?

[Jose Luis Lopez]

Same issue here and we also need a solution. Any idea?

[David Laine]

This seems like a very obvious automation, spinning a PIR following a major Incident. I need to do this too!

Atlassian products in some areas can be frustrating sometimes, its like someone has not thought about this or completely missed something fundamental, or have just not finished the development evolution of something. 

I don't understand why the "Primary Incident Link" would not be identifiable from the automation engine. Is there a workaround? Please help Atlassian!

[Rus Yates-Aylott]

Yes. You can create a PIR in an automation and you can create a link back to the trigger (parent) issue but in the PIR ticket view, this appears as a standard linked ticket (as with any ticket). Ideally, a linked incident case in a PIR should appear in the Primary Incident section but there does not seem to be any way of achieving this using an automation.

Any Atlassian boffin know how to achieve this?