Automation rule to edit the work items linked to the work items in a released version

Parag Shah

Folks,

Need help on a tricky automation rule that I am trying to setup.

I have 4 work items - A, B, C, D.

I have cloned B from A and D from C.

Created a version, 1.0.0 and included A and C.

When I release this version, I want label in B and D to be set to Released. These are actually the linked items of A and C.

I don't want to use any add-on like ScriptRunner. Native Jira cloud automation solution will be much appreciated!

Trudy P Claspill

Hello @Parag Shah 

You could accomplish this with 2 automation rules.

Rule #1 would be triggered by the version being released. It would loop over the items in that version and call Rule #2.

Rule #2 would look up the items linked to the items in the released version. It would iterate through the linked issues and transition them.

Let's start with Rule #1. It is pretty simple. When the version is released, collect the issues in it, iterate through that list, and take some action. For now we will use the Log action as a placeholder.

The above Log action will eventually be replaced by a call to Rule #2, supplying the item key of each item in the released version.

 

For Rule #2 we start with the basic structure that we can test to make sure it works

TRIGGER: Manual
FOR EACH: Related item/JQL
-- JQL: issue in linkedIssues("{{triggerIssue.key}}","is cloned by")
  CONDITION: Field Value
    Field: Status
    condition: does not equal
    Value: Released

  ACTION: Transition Item
    To status: Released

You may want to test this with a dummy project, dummy release, and dummy issues.

Trigger it from an item (abc-1) that has items linked to it as "is cloned by" to confirm that the items created by cloning abc-1 are found and transitioned.

In my example the status value is "A Done".

After you are sure that is working properly, then we modify the rule.

Change the Trigger from Manual to Incoming Webhook.

In the branch, change the JQL to:

issue in linkedIssues("{{webhookData.issue.key}}","is cloned by")

{{webhookData}} is the smart value for the data passed to this rule in the call to its incoming webhook.

From the Incoming Webhook trigger for this rule, copy out the Webhook URL value and the Secret value. We're going to use those in Rule #1.

 

Now, back in Rule #1 we are going to add a Send Web Request action after the Log action.

We'll paste the Webhook URL from Rule #2 into the Web Request URL field of this action. And at the end of that pasted URL we are going to add ?issue={{issue.key}}
That will cause the current issue referenced in the branch iteration to be passed through the webhook to Rule #3, where we extract it with the {{webhookData}} smart value.

For the Web Request Body we will select Issue data (Jira format)

In the Header section in the Key field we paste in X-Automation-Webhook-Token
And in the Value field we paste in the Secret from Rule #1

 

So, for Rule #1 we have:
WHEN a version is Released
FOR EACH item in the version
EXECUTE Rule #2

And for Rule #2 we have:
WHEN triggered
FOR EACH item linked as "is cloned by" to the item from the trigger
IF the item's Status is not Released
THEN transition the item to Released

The JQL in Rule #2 can be refined so it selects only the linked issues that are in a status currently that has a valid transition path to "Released".