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:
Does anyone have any ideas of how we can save our ScrumMasters' time with the repetitive task of creating subtasks?
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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG