I want to create a Automation Rule in JSM which when "Chage Request Approved" then it will go

[Sreenadh]

Hi,

I want to create a Automation Rule in JSM which when "Change Request is  Approved" then it will go to In Development

note: here approval process is included in the workflow

Parent CR: Change Request Approved

Subtask1: Ready for Approval to In Development

Subtask2: Ready for Approval to In Development

Subtask3: Ready for Approval to In Development

is it possible in Change request and Subtask

If i Click on Approve then all the respective subtasks are Auto approved and status is moved to In Development.

I have approved the change Request then it is moved to In Development

Here i want to change the subtask status = "In Development" auto approved.

Thanks.

[Stephen Wright _Elabor8_]

Hi @Sreenadh 

Is this related to your other question?

In the other question, the rule copies the Status from the Sub-tasks to the Parent - but the logic in this question appears to be the opposite...

• If Parent CR transitions to "In Development"
• Then copy this Status to its Sub-tasks

...is this correct?

Ste

[Sreenadh]

As per the above question

I want to create a Automation Rule in JSM which when "Change Request is  Approved" then it will go to In Development

then all the subtask statuses are move to In Development

[Stephen Wright _Elabor8_]

Hi @Sreenadh 

Awesome! Because the parent is transitioned to "In Development" when it is Approved, it doesn't need to be transitioned in the rule - it is the trigger for the rule to execute.

The rule will look something like this:

• Trigger: Issue Transitioned
  • To Status = In Development
• Condition: Issue Fields Condition
  • Field = Issue Type
  • Condition = equals
  • Value = Change Request
• Branch: Related Issues
  • Type = Sub-tasks
  • UNCHECK this checkbox: Only include issues that have changed since the last time this rule executed 
    • Branch-Action: Transition Issue
      • Destination Status = In Development

---

Note: In this example rule, I've set the Destination Status to be a specific Status - but you could also use the value Copy from Trigger Issue or Copy from Parent if you prefer a more dynamic option.

Let us know if this works for you!

Ste

[Sreenadh]

Hi,

Can you please check the attached screenshot.

Thanks,

[Sreenadh]

@Stephen Wright _Elabor8_ 

Actually here approval process is included.

Please find the attached screenshot.

[Stephen Wright _Elabor8_]

Hi @Sreenadh 

This all looks correct!

Have you tested it? Does it work within your instance?

Ste

[Stephen Wright _Elabor8_]

Hi @Sreenadh 

For the second set of Screenshots, this error usually happens when the Rule's Actor does not have Permission to either see the Issues, or transition them.

The Actor can be found in Rule Details, is this set to a specific user? Or Automation for Jira?

---

How to check the Project's Permissions will depend on the Project Type - is this a Company-managed or Team-managed Project?

Ste