You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In our organization, we have a team that wants to use Jira, but they haven't figured out a way to make it work for them. In the current tool that they use, each team member works from essentially a large story (though that story still only takes them 1-2 weeks to complete, fyi - definitely not an epic). Every story is made up of copies of the same repeatable 90+ small sub-tasks that must be done to call the story complete.
So what this team needs in Jira is some type of story template that supports subtasks. Again, the subtasks (i.e. steps to complete the work) are always the same, it's just the core description of the story that changes each time.
Any suggestions here?
@NathanDouds You can use Automation for Jira to create a rue that states any time a Story is created, create these subtasks. If not all Stories need the subtask, you can add a component to the rule that states anytime a Story is created AND field [X] contains [this value], create these subtasks.
With 90+ subtasks you can either manually set the all 90 subtasks in the rule or you can call a file that contains the list of subtasks to create. The file option takes a bit more configuration and scripting, but it can be done.