• 24
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Problem

      Currently, there's no way to link an incident ticket as Primary Incident via Automation.

      There are instances in which it'd be ideal for users/teams to be able to use Automation to identify whether an incident requires a PIR, by validating conditions and creating a PIR ticket if the conditions are met.

      Suggested Solutions

      Have functionality to link issue to Primary Incident.

      Current Workarounds

      Manually clicking Add PIR in issue view

            [JSDCLOUD-15113] Automation action to link issue to Primary Incident in PIR

            Is there any workaround until Atlassian provides a solution ?

            Maansi Vyas added a comment - Is there any workaround until Atlassian provides a solution ?

            It would be immensly useful to have this available in the automation workflows. It's a pity that it can't even be updated through the fields or custom fields.

            Fabio Germann added a comment - It would be immensly useful to have this available in the automation workflows. It's a pity that it can't even be updated through the fields or custom fields.

            Using automation, you can raise a PIR and link it back to the Trigger issue (The Parent incident). However, in the PIR case, the ticket view shows the link in the normal ticket link area and NOT in the Primary Incident section.

            In automation, when a PIR case type is raised, there needs to be a way of creating a link in the Primary Incident space.

            Rus Yates-Aylott added a comment - Using automation, you can raise a PIR and link it back to the Trigger issue (The Parent incident). However, in the PIR case, the ticket view shows the link in the normal ticket link area and NOT in the Primary Incident section. In automation, when a PIR case type is raised, there needs to be a way of creating a link in the Primary Incident space.

            Why was this not implemented the standard way on how things are linked in Jira? There already was issuelinks and remotelinks! Why implement a completely new link type unavailable in Jira Automation AND REST API?

            Dear Atlassian, sometimes I really have my doubts about your product design decisions .

            Well, it's implemented the way it is. So the question is: When can we have an automation action or at least a REST endpoint? Creating PIRs fully automated and then being forced to link them manually is so 1995. Come on!

            Thanks, Romano

            Romano Sommer added a comment - Why was this not implemented the standard way on how things are linked in Jira? There already was issuelinks and remotelinks! Why implement a completely new link type unavailable in Jira Automation AND REST API? Dear Atlassian, sometimes I really have my doubts about your product design decisions . Well, it's implemented the way it is. So the question is: When can we have an automation action or at least a REST endpoint? Creating PIRs fully automated and then being forced to link them manually is so 1995. Come on! Thanks, Romano

              36bd3fea80e3 Makarand Gomashe
              7481a4925172 Rex
              Votes:
              51 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated: