We are evaluating Portfolio for Jira, and the Stages feature looks very useful. We want to be able to include estimation for development and QA for stories, and Stages seems to allow that.
When you have stages set to concurrent, they get scheduled into the same sprint. Presumably, this means that if you actually assign those stories into a sprint, you would work on those stages and when they are complete, your story would be complete. Is there any way to actually keep track of having "done" a stage for a story? Or is it just conceptual for planning?
If you have stages scheduled into consecutive sprints, this seems to violate the way Jira Agile works. A story is meant to be put into a single sprint, and if you carry it over into another sprint, the work isn't counted for the first sprint and its velocity drops, and you use up some story points capacity for the second sprint. How are you supposed to reconcile this?
A shorter version of this question is, "What do stages mean in the context of Jira, versus Portfolio?"
The documentation doesn't really address this.
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