Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


New Feature versus Story

Team I am supporting is using New Feature > Story as their hierarchy to deliver on work. They are gross-estimating for purpose of PO prioritization at Feature level and then teams breakdown Features into Stories; and estimate on actual work. 

**What is considered features in this case IS NOT really features - they used it "simply because".**

Since estimates are at both Feature & Story level, the story points are a summation however really the Feature shouldn't have any story points. I am concerned that the various Reports are representing incorrectly. I also find it difficult to visualize the parent>child relationships since Jira doesn't view it that way. Can use some sound boarding on this approach.  What does everyone else do? 

1 comment


Log in or Sign up to comment

Hi Simran,

I would consider changing either the New Feature to an Epic, or the stories to subtasks. This should help you with the parent child visualization and give your tasks a more natural progression through your process. 

Hope this helps,

AUG Leaders

Atlassian Community Events