You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I can't seem to find any documentation that explains what the status of "missed" represents for Objectives. Is this a phantom value that crept into our configuration or an earlier status that has been depreciated and isn't worth mentioning anywhere?
Marcie,
hope this help
Nohma Abboud
that makes sense, but if the objective was expected to be delivered mid PI, then what happens? do you just change the expected date to shift the objective out along the PI timeline and it will always maintain the missed status even when it's delivered?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marcie Mierz - If the Objective was planned to be completed within the PI, but it didn't occur [for whatever reason], then it gets re-labeled as "Missed" per what @Nohma Abboud shared.
That Objective does not rollover into the following PI. It stays for tracking purposes and overall ART metrics, etc.
If the work (ie. Feature) is going to rollover into the the following PI, then you would simply create a new Objective.
Hope that response helps and is of value!
-Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.