nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Sreenadh_5t0th7

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.

Accepted answers

All comments

Ste Wright

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_5t0th7

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

Ste Wright

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_5t0th7

Hi,

Can you please check the attached screenshot.

Thanks,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management