How to add a number to the summary of the subtask created with automation

[Gonzalo Galdames]

Hi team,

How to add a number to the summary of the subtask created with automation in jira cloud with smart values, example:

summary :  subtask 1

summary : subtask 2

The subtask number should be generated automatically.

[Bill Sheboy · Accepted solution]

Hi @Gonzalo Galdames -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this?  That is, why do this?  Knowing that may help the community to offer better suggestions or alternatives.

Until we know that...

• What does the number represent in the subtask's summary?
• What happens to these numbers if a subtask is deleted (or moved to another parent)?
• How do you plan to create subtasks: manually, with automation rules, using issue import, etc.?

Subtasks are ordered by Rank when shown in an issue (by default), and they can be reordered by drag-and-dropping them.  And so having numbers will not prevent them getting out of this number order.

The ways you create subtasks impact the timing (i.e., the speed of adding), and the format of the summary impacts the ability to find the next number / avoid duplication.

It is possible to assign a number as you ask with automation, but there are lots of edge-cases and potential timing problems that can make accurate numbering challenging.

Kind regards,
Bill

[Gonzalo Galdames]

Hello Bill,

Thank you for your response. To provide further context, the issue involves subtasks created through automation rules with the same summary. The goal is for them to be differentiated by number. Is there any intelligent value we can add to the summary to reflect the number?

For Example:

The idea that Reprogramming can be generated with different numbers from automation.

[Bill Sheboy]

Please try to stay with one thread in posting your responses.  That will help others viewing this question in the future to know if there are multiple solution approaches.  Thanks!

Back to your original question...

If we assume you are adding all of these subtasks with one automation rule, I recommend setting the values for those numbers manually.  For example:

• action: create subtask, with summary "Reprogramming 1"
• action: create subtask, with summary "Reprogramming 2"
• action: create subtask, with summary "Reprogramming 3"

Or for the case of adding multiple subtasks with one action...

• action: create subtask,
  • with summary "Reprogramming 1"
  • with summary "Reprogramming 2"
  • with summary "Reprogramming 3"

The first approach will help ensure the order of subtask creation matches the numbers, but I do not know if the second one will enforce that.

If instead you are creating the subtasks over time, with different automation rules (or rule executions), it may not be possible to accurately assign the next number.  In this case, please post images of your rules which create subtasks so the community can provide ideas about the reliability of this numbering practice.