Forums

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

Automation: Create sub-tasks for every member of a user group

MidnightExe
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2025

Hello Community,

I'm currently working on an automation rule in our Jira Service Management (Data Center) instance and would appreciate your expertise.

The specific requirements for the automation are:

  1. If an issue is created

  2. And the issue has a specific label, e.g., TODO

  3. Action: For every single member of a defined user group (e.g., team1), a sub-task should be created // if its possible also assigned to that respective user.

My Question: What is the most efficient way to implement the third step creating sub-tasks for an entire group?

Thanks in advance for your help and ideas!

Best regards!

3 answers

2 votes
Jayesh Raghuvanshi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2025

@MidnightExe 

Below is my suggesstion to follow

  • Automation Rule configuration
    • set a trigger when issue is created
    • use the below issue field condition
      • field: labels
      • Condition: conatains any of
      • Values: TODO
  • Get group members via Rest API
  • Advance Branching for each user
    • Smart Value - {webResponse.body.values.accountId}
    • Variable Name - groupMember
  • Create Subtask for each user
    • Project: Same as trigger issue
    • Issue type - Subatsk
    • Assignee - Group member

Reference KB article: https://support.atlassian.com/jira/kb/how-to-add-group-members-as-request-participants/

 

If you like the suggestion kindly accept the solution.

Thanks
Jayesh R

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2025

Hi @Jayesh Raghuvanshi 

The original poster asked about Jira Data Center, which does not have advanced branching for automation rules, and thus your suggestion cannot work.

To learn more, please see the supported branch types for Jira Data Center and the suggestion to add the feature:

 

Kind regards,
Bill

2 votes
Mohamed Benziane
Community Champion
October 10, 2025

Hi,

This should be possible, you will need to make a api call to get all users from a group : 
Setup automation rule to get all the users added in a group and then create issues and assign them to each user | Automation | Atlassian Support

MidnightExe
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2025

Hei, 

so it's not possible with Scriptrunner or Project Automation? Would be alot easier, rather than the option you provided

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2025

Hi @MidnightExe 

This would be easy if Jira Data Center's automation had advanced branching over smart values, which it does not yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749

Possible workarounds depend upon your assumptions and the effort to solve this:

  • When this need is infrequent, use a CSV import to create the subtasks
  • When the user group is stable and has just a few people in it, hardcode the subtask creation for each user in your automation rule.  That is, there is no looping or branching.  Depending upon how the rule is implemented, it could handle 60 users or more this way, although it will be quite difficult to maintain.
  • Use two different rules, where
    • One rule, triggered on issue create, gets the users in the group and then triggers an Incoming Webhook Trigger rule using the Send Web Request action
    • The second rule, with the Incoming Webhook Trigger is recursive...
      • When the rule triggers, use the passed data to add the first subtask for the user
      • Remove the user from the list
      • When there are more remaining, the rule triggers itself to run again with the remaining list
  • Build your own app using the REST API endpoints and a computer language which supports the looping
  • Investigate the Atlassian Marketplace for apps to automate this issue creation, such as with scripting addons

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer