Automation Rule

Murugesan April 17, 2024

We've established the automation rule for the following scenarios:

Upon transitioning the workflow from "Order Validated" to "Customer/Sales Ack Received," seven subtasks will be automatically generated.

Now, I aim to implement a new automation rule for the following scenarios:

  1. Subtask-1
  2. Subtask-2
  3. Subtask-3
  4. Subtask-4
  5. Subtask-5
  6. Subtask-6
  7. Subtask-7

We plan to introduce two custom fields featuring single-select options, with "Yes" or "No" as mandatory choices. One field is designated for Subtask-1, and the other for Subtask-5.

When transitioning the workflow from "Order Validated" to "Customer/Sales Ack Received," and opting for "Yes" for Subtask-1, Subtask-5 will be set to "No," resulting in the creation of six subtasks excluding the 5th one.

Conversely, if "No" is selected for Subtask-1 and "Yes" for Subtask-5, six subtasks will be created, excluding the 1st one.

Choosing "No" for both Subtask-1 and Subtask-5 will lead to the creation of five subtasks, excluding the 1st and 5th ones.

Please advise

2 answers

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

Hi @Murugesan  - Welcome to the Atlassian Community!

I am not completely following your request. You have a rule now that creates the 7 sub-tasks based on an Issue Transitioned trigger. Correct?

And now you want to modify that trigger to to somehow prompt the user for some information when the trigger runs? Is that what you want to do? Or something else? 

Murugesan April 17, 2024

Let me explain in details:

Below are the names of the 7 subtasks:

Subtask 1: APN Creation
Subtask 2: MOP Creation & Execution
Subtask 3: SIM/Profile Ordering
Subtask 4: Commercial Mapping
Subtask 5: IP URL Whitelisting
Subtask 6: SIM Profile Manufacturing
Subtask 7: SIM/Profile Dispatch & Provisioning

We have recently introduced two custom fields with a single select option [Yes/No]:

APN Creation Needed
IP/URL Whitelisting Needed

The above 7 subtasks will be created automatically when transitioning from "Order Validated" to "Customer/Sales Ack Received."

Now, we are planning to make the above two custom fields mandatory during the transition from "Order Validated" to "Customer/Sales Ack Received." Consequently, subtasks will be created based on the options selected for those two custom fields.

1. If the user selects "Yes" for the APN Creation Needed field and "No" for the IP/URL Whitelisting Needed field, then the following subtasks will be automatically created, excluding Subtask 5:

Subtask 1: APN Creation
Subtask 2: MOP Creation & Execution
Subtask 3: SIM/Profile Ordering
Subtask 4: Commerical Mapping
Subtask 6: SIM Profile Manufacturing
Subtask 7: SIM/Profile Dispatch & Provisioning

2. If the user selects "No" for the APN Creation Needed field and "Yes" for the IP/URL Whitelisting Needed field, then the following subtasks will be automatically created, excluding Subtask 1:

Subtask 2: MOP Creation & Execution
Subtask 3: SIM/Profile Ordering
Subtask 4: Commerical Mapping
Subtask 5: IP URL Whitelisting
Subtask 6: SIM Profile Manufacturing
Subtask 7: SIM/Profile Dispatch & Provisioning

3. If the user selects "Yes" for both the APN Creation Needed and IP/URL Whitelisting Needed fields, then all subtasks will be created automatically.

Subtask 1: APN Creation
Subtask 2: MOP Creation & Execution
Subtask 3: SIM/Profile Ordering
Subtask 4: Commerical Mapping
Subtask 5: IP URL Whitelisting
Subtask 6: SIM Profile Manufacturing
Subtask 7: SIM/Profile Dispatch & Provisioning

4. If the user selects "No" for both the APN Creation Needed and IP/URL Whitelisting Needed fields, then the following subtasks will be automatically created, excluding Subtasks 1 and 5:

Subtask 2: MOP Creation & Execution
Subtask 3: SIM/Profile Ordering
Subtask 4: Commerical Mapping
Subtask 6: SIM Profile Manufacturing
Subtask 7: SIM/Profile Dispatch & Provisioning

I hope this clarifies the process. Can you assist with the automation rule for this?

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 18, 2024

You should be able to do a service if IF/ELSE conditions then. 

Murugesan April 22, 2024

Yes, Created the automation rule with IF/ELSE condition. Thanks for your help!

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 23, 2024

Is it working now?

Murugesan April 23, 2024

Yes. It's working with IF/ELSE condition. Thanks for your help!

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 23, 2024

Great! Could you click on the Accept Answer button above then to close this one out? Thanks!

0 votes
Matt Parks
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

You could create separate branch rules for creating sub-tasks 1 and 5 that would only execute the creation of the task if the condition is met. Something like this:

Note that, in our environment, the Task issuetype is actually a sub-task (I renamed it because we moved to Jira from a system where Tasks were the children of Stories, so this was less confusing).

2024-04-17_8-54-48.png

Suggest an answer

Log in or Sign up to answer