Suppose I have a story which takes 2 days to implement. In our process, the story would proceed to a design review, followed by QA, then UAT. Therefore, in evaluating JIRA Portfolio, I created stages for each of these steps. Now, one would expect that for a 2 day task, you could probably implement and test that story all within a single sprint. However, JIRA Portfolio is breaking each stage out into its own sprint which is not useful and not accurate.
How I can illustrate this sequential step by step workflow and the time required to go through this workflow in JIRA portfolio?
I am not sure if what you need is possible with Portfolio. Our program management tool Cycle Control is designed to do exactly what you are describing here as a use case. You can define the start, end dates for each of the stages, you can visualize the sequence of stages on a timeline view, it has powerful metrics module, milestones, checklists. etc.
Let me know if you are interested in a demo or have more questions.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs