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

What is the best practice for features that we expect run over 1 or more sprints?

Jennifer Saunders
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 25, 2023

I am trying to work out the best practices for planning epics. I have split the epic down into sizeable chucks of feature and stories that will be tested at the same time. However the features are likely run over 1  or more sprint. And i would prefer to plan stories into sprints. My first thought was to add the features (Hierarchy level 0) and add the stories as subtasks (Hierarchy level -1). However the issue with this is you can only all subtasks under a feature to the sprint not individual ones. Another thought is to add a label to the stories that fall under a feature, but this will make planning more difficult. Is there another more effective way to do this? 

Many thanks,

Jen 

0 answers

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