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!


Does Portfolio consider statuses mapped to Done in a Board as Done or does it use the status mapping

I thought I saw that Portfolio was considering an issue done if the status it is at was mapped to the last column on a board. I have mapped our deployment process statuses which aren't considered Green/Done to the last column on the board which is Done. In Portfolio they are still being scheduled as In Progress instead of Done. Yet on the Board they are considered Done.

We are using story points to estimate work and track velocity. We have deployments steps in our workflows after we want to consider our teams done with their work. We have both Scrum and Kanban teams and are pulling both into portfolio from Scrum boards so every team is using Story Points for scheduling.

My desired outcome is issues that are in the last column of a Board are displayed in Portfolio as Done. This keeps them visible in Portfolio, shows them as completed in the progress bar, and keeps them out of the scheduling calculation.

Am I missing a configuration setting or did I dream Portfolio uses the imported Board's definition for what statuses are considered Done? Is there another way for me to solve this scheduling challenge without a lot of extra work or switching to hours, or do I need to exclude the deployment statuses from my Portfolio plan? 

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events