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; } } }

How to add a condition about subtasks created in automation rules

Raquel Muñoz Gutiérrez

Hi!

I want to create subtasts automatically but only once. I created a rule to create several subtastks with the "manual" trigger.

The problem is that I wanted to add a condition so the subtasks only can be created the first time you action the rule, so the subtasks aren't duplicated, but I don't get how to configure that condition.

Any idea?

Accepted answers

Atlass Monster

@Raquel Muñoz Gutiérrez Hi hi to you.

This should work

Screenshot 2025-01-16 185538.png

JM Perrot

Hello @Raquel Muñoz Gutiérrez and welcom among us!

I think you can add a hidden (or visible, your choice) numeric custom field and incorporate two steps into your automation.

At the end of your automation, set this field to "1" to indicate that the automation has already been executed.
After the trigger, check the value of this field. If it is already set to "1," the rule will not execute further.

This approach should help prevent duplicate executions of the rule. Let me know if you need further clarification!

Step-by-Step Guide:

Create a Numeric Custom Field:
- Go to Settings > Issues > Custom fields.
- Create a new Numeric custom field, e.g., "Subtask Created Flag"
- Associate it with the appropriate screens.
Modify Your Automation Rule:
- Trigger: Set the trigger as "Manual" (you already have this).
- Condition: Add a Condition step right after the trigger:
 - Select Advanced Compare Condition Or issue field Condition.
 - if you choose Advanced Compare Condition, set it to:
```
{{issue.Subtask Created Flag}} != 1
```
 This condition ensures the rule won't proceed if the flag is already set to 1.
- Actions:
 1. Add the actions to create subtasks as usual.
 2. Add an action at the end of the rule to Edit Issue:
 - Set the "Subtask Created Flag" field to 1.

Optional Tweaks:

Make the Field Hidden: If you don't want users to see this field, you can:
- Remove it from all screens.
- Use Jira's API to check or reset the value if needed.
Reset the Field: If you ever need to allow the subtasks to be recreated, you can manually or automatically reset the custom field to 0.

All comments

Atlass Monster

@Raquel Muñoz Gutiérrez Hi hi to you.

This should work

Screenshot 2025-01-16 185538.png

JM Perrot

Hello @Raquel Muñoz Gutiérrez and welcom among us!

I think you can add a hidden (or visible, your choice) numeric custom field and incorporate two steps into your automation.

At the end of your automation, set this field to "1" to indicate that the automation has already been executed.
After the trigger, check the value of this field. If it is already set to "1," the rule will not execute further.

This approach should help prevent duplicate executions of the rule. Let me know if you need further clarification!

Step-by-Step Guide:

Create a Numeric Custom Field:
- Go to Settings > Issues > Custom fields.
- Create a new Numeric custom field, e.g., "Subtask Created Flag"
- Associate it with the appropriate screens.
Modify Your Automation Rule:
- Trigger: Set the trigger as "Manual" (you already have this).
- Condition: Add a Condition step right after the trigger:
 - Select Advanced Compare Condition Or issue field Condition.
 - if you choose Advanced Compare Condition, set it to:
```
{{issue.Subtask Created Flag}} != 1
```
 This condition ensures the rule won't proceed if the flag is already set to 1.
- Actions:
 1. Add the actions to create subtasks as usual.
 2. Add an action at the end of the rule to Edit Issue:
 - Set the "Subtask Created Flag" field to 1.

Optional Tweaks:

Make the Field Hidden: If you don't want users to see this field, you can:
- Remove it from all screens.
- Use Jira's API to check or reset the value if needed.
Reset the Field: If you ever need to allow the subtasks to be recreated, you can manually or automatically reset the custom field to 0.

Raquel Muñoz Gutiérrez

Wow! Thank you so much! It's a simple and easy solution, I can't believe I didn't get to it myself.

Raquel Muñoz Gutiérrez

Thank you!!! I was searching something like this but I wasn't using the functions properly.

JM Perrot

You're very welcome, Raquel! Sometimes the simplest solutions are the hardest to spot when you're deep in the problem.

Don't hesitate to reach out if you have more questions or need help fine-tuning your automation.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

subtasks

cloud-automation