Automation to Create Sub-Task Based on Multi-Choice/Checkbox Field

[Drishti Maharaj]

Hi,

We seem to be having a bit of an issue with an automation to create sub-task based on a

Multi-Choice/Checkbox Field.

The idea is that when the field is edited, different sub-task are created based on the options. The dilemma is that the user could pick one option then decide to pick another option an hour or two later.

When the field is edited, it then re-creates the first sub-task based on the option.

Example:

Field Options

Option A

Option B

Option C

- User picks Option A at 10:00 and sub-task for Option A is created.

- User picks Option B at 11:00 and then sub-task for both Option A & Option B is created

How would you prevent the sub-task for Option A duplicating when the field is edited?

Thanks.

[Trudy Claspill]

Hello @Drishti Maharaj 

When asking for help modifying a rule it will enable us to help you more effectively is you provide screen images that show your entire rule, and the details of each step.

Possibly, in your Automation rule where you have determined that Option A has been selected, you might be able to follow that with checks to see if the corresponding subtask already exists by using a Lookup Issues action to search for a subtask under the trigger issue with the specified Summary used for the Option A subtask, and then checking to see if the Lookup Issues action found any issues (using a smart value condition to check {{lookupIssues.size}} )

[Drishti Maharaj]

Hi @Trudy Claspill  - I have been trying to play around with this and I found a few other posts also on Atlassian Community but I cannot seem to get it right.

This is the automation I had that I went off base don this with some modifications (https://community.atlassian.com/t5/Jira-questions/Automatically-creating-Subtasks-from-a-Checkboxes-field/qaq-p/2515668) but the issue is that the other sub-tasks are still getting created so there is probably an issue with the "Lookup issues" and "Compare values".

[Trudy Claspill]

Hello @Drishti Maharaj 

Please provide screen images that show the entire rule, not just the branch.

Also, please provide the details of your For Each: Smart Value step.

And, as @Bill Sheboy note in the other post where you asked for help, you need to enclose Department in curly quotes where you are trying to use it in the JQL of the Lookup Issues action.

[Drishti Maharaj]

Hi, managed to actually get it right and the automation is working as it should now. Thanks. 

[siviani.madrigal]

Hey @Drishti Maharaj  how do you fixed?? Im interesting to understand how this automation rule can be config, I have same situation. 

[Drishti Maharaj]

Hi @siviani.madrigal  - here are some screenshots of what I did.

[siviani.madrigal]

Thank you very much!!