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

Features can be closed out / accepted without all the associated stories being in an accepted state.

Is this by design?  I understand Features can have different acceptance criteria but should features be allowed to move to accepted if all the stories are not accepted?

3 answers

1 accepted

1 vote
Answer accepted
Rich Sparks Atlassian Team Jun 30, 2020

Yes, Features can be Accepted even if all the stories are not accepted, and this is by design.

It may be the case that the Product Manager (or Chief Product Owner or whomever is responsible for the Feature) decides that it is good enough even though all the stories are not completed. The Product Manager may decide some of the stories aren't needed, in which case they should be cancelled or deleted and removed from any team's backlog. 

If the Product Manager accepts a Feature without all the stories being accepted, this will show up on the program board with a red flag in the upper left to indicate "Accepted with Planning Issues".

Screen Shot 2020-06-30 at 9.29.43 AM.png

Thank you Rich!

Like # people like this
1 vote
Tom O_Connor Atlassian Team Jun 30, 2020

@Jack Hunter _HeroCoders_ Jira Align doesn't enforce child accepted status requirement for accepting a Feature.  We often recommend handling this through your Definition of Done requirements for getting a Feature to DONE and Accepted.  Although most Product Managers would validate and require all stories are accepted, sometimes there are cases where the Feature delivered enough of the right value to Accept the Feature without getting all of the stories to done.  The question is what do we do with the remaining stories?  They could remain on the backlog, get associated to another feature or closed out as not valuable anymore. 

Your question could be submitted as an enhancement request that a rule could be added to JA for all child acceptance before you are able to accept the parent.    https://internal.agilecraft.com/ideaZone/ideas

Tom O_Connor Atlassian Team Jun 30, 2020

What @Rich Sparks said too!

0 votes

Hi @Derwin Roland,

What do you mean by "associated stories"? Do you mean subtasks or issues linked to another issue? Or maybe Epic and all its stories? 

Cheers,
Jack

The stories that make up the feature and that must be completed to make the Feature complete.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events