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?
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events