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

Does your team use Epic, Story and Feature ticket types in the same project?

We have Epics for larger features. 

I want to replace Feature with Stories, but product team wants to keep Features as a high level request with use cases.

Wondering how your teams work with these 3 issue types and if one just gets cloned or promoted when needed.

1 answer

0 votes
Warren Rising Star Sep 13, 2017

I think if you ask 10 different companies, you'll probably get 10 different answers. :)

However, the generally accepted idea (supported by the Scaled Agile Framework SAFe) is a hierarchy where many stories form part of one feature and many features form part of one epic. Essentially it is a size description.

Have a discussion with the product team, try to understand why they want it like that and let them know why you want it changed, but in the end it doesn't make a huge difference

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events