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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create Common Default Subtasks in User Story (JIRA Cloud)

We have common sub-tasks for many of our user stories. For example Write Acceptance Tests, Write Unit Tests and Code, Run Acceptance Tests, Review Code and Merge Pull Request, Product Owner Review, etc.

For bugs it's something like Write Failing Unit Test/Fix Bug/Retest and Review Code and Merge Pull Request.

Today, the ScrumMaster creates these subtasks manually for the stories at the top of the backlog prior to each sprint planning meeting, for those that are likely to be included in the next sprint. This takes a lot of time and we'd like to automate it.

Here are the solutions we've looked into, none of which appear to handle our needs nicely:

  • Quick Subtasks for JIRA plugin - This looks like EXACTLY what we need; we could have the sub-tasks listed in our wiki for each type of parent issue. Not available for JIRA Cloud.
  • Cloning an issue with its subtasks - The problem here is the product backlog gets created weeks or months prior to issues being added to a sprint, and as time goes on the project team may discover they want a different set of default subtasks so they wouldn't want them all to have subtasks when created.
  • Create on Transition for JIRA - Looks like it might work if there was a way to capture when an issue was added to a sprint. Not available for JIRA Cloud.
  • Clone Plus for JIRA - Looks like it might work, not available for JIRA Cloud
  • CLI Plugin for JIRA - Looks like this may be a solution, but at first glance it looks overly technical and not something that would appear to fit into our ScrumMasters' level of technical ability

Does anyone have any ideas of how we can save our ScrumMasters' time with the repetitive task of creating subtasks?



4 answers

If you don't plan to move out from jira OnDemand to standalone version - the best solution is to create a script that will use CLI or REST API. So your scrum master start the file on his local computer, enter the key of needed field subtasks should be created - and that's all. Actually you can develop/order some GUI for that.

Hi Dave,

I have exactly the same problem. Did you find a good solution to this?

Thanks for any pearls of wisdom!



Unfortunately, no. It appears the only way to populate sub-tasks into a story electronicallly is to import both the story and sub-tasks together. This doesn't work for us since we create the stories on the product backlog and only create sub-tasks when the sprint containing the stories is planned.

The problems of default sub-tasks and estimating the story are apparently unresolvable shortcomings. The only thing we can do is try to work around them as best we can.

0 votes
ptitdab6 I'm New Here Feb 09, 2021

Bonjour, voilà comment j'ai fait : 

project setting / project automation / add component / new action / add sub-tasks


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you