Jira Automation - Update multiple links in additional fields

David D.

Hello,

My issue is as follows.

I am writing a Jira Automated Rule that will create multiple "Task" tickets upon an Epic creation using a specific label. I have some intricate dependencies that are important in the end result. For the sake of an example, let's use the following diagram:

My Jira automation rule works almost completely. If an Epic is created, it checks the label, if so it Creates Ticket 1. Then it creates a variable ticket1Var = {{createdIssue.key}}. Then it creates Ticket2. In Additional Fields of Ticket 2, I have: 

{"update": {
  "issuelinks": [
   {
     "add": {
       "type": {
         "name": "Blocks"
       },
       "inwardIssue": {
         "key": "{{ticket1Var}}"
       }
     }
   }
  ]
 }
}

It creates ticket2Var = {{createdIssue.key}}. It then creates Ticket3 and does the same.

Finally, it creates Ticket 4 but then I don't know what to do to have Ticket 4 blocked by Ticket 2 and Ticket 3.

I think I have tried everything I could.

• Asked ChatGPT that can't answer the question.
• I have searched online, found this page: [JRACLOUD-81845] JIRA REST API: only a single issue link can be added when editing or creating an issue - Create and track feature requests for Atlassian products.. The solution is false. The answer is that it would be a choice from the dev team but I don't get it other than code limitations which would be really unfortunate.
• I have reviewed the documentation here: Advanced field editing using JSON | Cloud automation Cloud | Atlassian Support which doesn't provide a possible solution.
• Testing something, I got an error that got me to this page: LinkIssueRequestJsonBean (Atlassian JIRA 7.2.1 API) It looks like the Class construct only allows one issue link to be passed...

So am wondering:

• Can this be done with additional fields or not?
• If it can't be done this way, can it be done by editing the issue in another action, if so how? I don't understand how I can edit a newly created issue via a Jira automation.
• Anything else I can consider?

David D.

So I just figured out an alternate solution... (ecstatic!)

After Ticket 4 creation, I went ahead and created a Branch Rule for "Most recently created work item". Then I perform a new action "Edit work item fields" which will directly edit the work item related to that branch. 

I could not do "Edit work item fields" in the main branch because there is unfortunately no solution to select the Issue key that we want to Edit (not manually nor using smart values).

In the "Edit" action, I went ahead an modified the additional fields section to take into account the same JSON structure and add the inwardIssue link from "{{ticket3Var}}".

By doing this, I get the exact dependencies as I wanted in the Ticket diagram I shared.