Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to Set a Sub-task's Original Estimate Conditionally in Jira Automation?

Karmandroid Singularity
Contributor
June 26, 2026

 

Hi,

I'm trying to create a Jira Automation rule where creating a task with a specific keyword automatically creates several subtasks with predefined settings.

For example:

I create a task with the summary:

Create Badge for Staff Party

Let's call this the Trigger Task.

Since the summary contains the word "Badge", I want the automation to:

  • Add "This is a Badge task." to the Trigger Task description.
  • Create a subtask with the summary "Badge Color" (Sub-task A).
  • Create another subtask with the summary "Badge Animation" (Sub-task B).

For Sub-task B, I want the Original Estimate to depend on the Trigger Task's summary:

  • If the summary contains "Party"8h
  • If the summary contains "Festival"16h
  • If it contains neither "Party" nor "Festival"10h

Rovo (the AI assistant) suggested using the following formula directly in the Original Estimate field:

 

{{#if(issue.summary.matches("(?i).*(Party|Parties).*"))}}8h{{#elseif(issue.summary.matches("(?i).*(Festival).*"))}}16h{{#else}}10h{{/if}}

However, the automation fails when it reaches that action.

Is this type of conditional expression supported in the Original Estimate field? If not, what would be the recommended approach to achieve this without creating multiple separate automation branches?

Thanks in advance!

3 answers

3 votes
Arkadiusz Wroblewski
Community Champion
June 26, 2026

Hello @Karmandroid Singularity 

One extra detail to last answer. Value depends on the original trigger task summary, also make sure you reference the trigger issue, not the newly created sub-task.

Like that: {{if(triggerIssue.summary.contains("Party"), "8h", if(triggerIssue.summary.contains("Festival"), "16h", "10h"))}}

Also don´t forget field must be added to relevant Sub-task field creation screen.

Best,

Arek🤠

1 vote
Nikola Perisic
Community Champion
June 26, 2026

Hi @Karmandroid Singularity 

Rovo was giving the Java formated code which is not supported by the automation. Back to the automation setup:

  • Trigger: Work item created
  • Edit work item fields: Description
  • If summary contains Badge two sub-tasks are created for Triggered work item
  • For most recently created work items branch: this branch will be always focused on the Sub-task B, and if the Summary contains Party, Original estimate will be 8h

The rest continues as described from your issue. Since you have the fixed Summaries for both sub-tasks, depending how your triggering issue is, it will only change based on it. If you do manual change, the automation won't work.

0 votes
Anurag Vipin Vaidya
Contributor
June 26, 2026

Hii @Karmandroid Singularity 

The original estimate field does not supoort if/elseif/esle smart value blocks directly so that expression will fail.

try

 

  • Create the sub-task first.
  • Then use conditional branches (If/Else blocks) to check the parent issue's summary.
  • In each branch, use Edit issue to set the Original Estimate (8h, 16h, or 10h).

 

Nikola Perisic
Community Champion
June 26, 2026

Hi @Anurag Vipin Vaidya 

Bear in mind that this only needs to happen for the Sub-task B.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events