Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,104
Community Members
 
Community Events
184
Community Groups

How to automate task + sub-task creation when new release is created

Hi,

 

I have quite a long list of pre-deployment and deployment related tasks that I want to have included in every new Jira release. How can I use Jira automation for Task and Sub-task creation that is triggered when a new release version is created? So far I have only managed to create automation for creating a Task automatically, but cant seem to figure out how to add Sub-tasks to that. Any advise for this?

Reason I want to have a Task and Sub-tasks is that there are multiple people involved in the process and I want to be able to assign different parts of the process to different people, instead of just having a checklist within the Task.

1 answer

Hello @Niklas Nygren 

Welcome to Community!

Did have the chance to check this tutorial? -> https://www.atlassian.com/agile/tutorials/how-to-auto-create-subtasks-with-jira-software-automation

Maybe it will help.

Regards

Hi,

 

Indeed that tutorial is where I started trying to solve this, but no luck since that trigger starts from issue creation and my solution requires it to start from release creation.

This is where I am currently stuck:
JiraAutomation.PNG

Wojciech Wardaszko _HeroCoders_
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.
May 09, 2023

Hi @Niklas Nygren

Welcome to the community!

It looks like for that rule to work you need to add a branch condition to specify with JQL the scope of the rule, so it would run against all matching issues. Without it, the rule does not have a collection of issues to run against.

Something simple like Project in ("my project") would likely suffice.

On the other hand, I noticed that you do not want to use a checklist because it cannot be assigned like sub-tasks can. I'm happy to inform you that with an app called Issue Checklist for Jira (both Free and Pro, developed by our team of HeroCoders) you can assign particular checklist items to specific people and they can see what items are assigned to them in their Jira Dashboard with the use of a simple widget that comes with our app. Maybe this approach would actually prove simpler to you.

In case you would like to discuss this approach further, please feel free to reply here or reach out to us via our service portal.

Cheers!

Hi, 

Thanks for the suggestion, I just noticed that I have tried using your app for this same purpose earlier :) The problem with that is, that I need to be able to add some additional details inside one Checklist item, which isnt possible. Hence I am trying to get this implemented with Sub-tasks.

Wojciech Wardaszko _HeroCoders_
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.
May 10, 2023

@Niklas Nygren

Would you mind sharing more about the additional details you need to put on the checklist item? We currently support assignee/mention, due date and an additional description. What else would you need to make this work?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events