First I wanted to say that Portfolio for JIRA is a great add on that enables us to finally create realistic release plans and manage capacities with JIRA.
We have a Kanban process for a product that is currently in MVP development stage. There are two different orders, the one of the JIRA backlog itself and the rank of portfolio.
While working with Portfolio, many questions came up:
Thanks in forward.
Hi @Stephan Dreyer,
Thanks for the questions, I'm sure this will be useful to many other community members! Please share your feedback on the ranking behavior and what you would like to see happen differently.
thanks for your comprehensive answer. I think it's hard to understand for many people (and me too) whether the Portfolio plan is a target plan or does reflect what's actually going on in a kind a status report. The difference between both is:
As a result of your answer, my feature requests / proposals to the Portfolio development team are:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot