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,463,474
Community Members
 
Community Events
176
Community Groups

Looking for a suggested template or approach for stories with large number of sub-tasks

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?

2 comments

Welcome to the community, @NathanDouds.

I am Marlene from codefortynine.

If you're open to work with a Marketplace app, you can have a look at Deep Clone for Jira.

You could create a template story including their subtasks and bulk clone them ever 1-2 weeks.

  • Open the template story
  • Click on the three-dots (issue action) menu on the top right
  • Click on Deep Clone
  • Select "target project" (you could either clone the template into the same project or another project)
  • Select "Same as original" as target issue type
  • Select "Clone all 90 subtasks and keep the hierarchy"
  • And follow the further instructions in the Deep Clone dialog

There are many other ways to configure the clone (include or exclude certain fields while cloning, edit issues fields while cloning, ...)

If you have questions or feedback about Deep Clone for Jira, don't hesitate to contact us.

Like NathanDouds likes this

@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.

Like NathanDouds likes this

Comment

Log in or Sign up to comment