We are trying to setup Portfolio for the first time. I entered 2 epics, although, they do not require the same skill set and do not have the same stages. Must all epics share the same "stages" and "skills". What if one project (epic) is kanban with multiple stages and the other is scrum with one stage? Can they be in the same plan even though they have different stages?
What if I have one "implementation" stage with 4 skills: Developer, Database, UI, QA. One epic needs only developer and qa, the other needs all 4 skills. How do you configure such scenarios?
I think this question has already been answered above, but I found it difficult to follow and implement. I'm hoping the following instruction will help others.
First click on the Epic Details link...
You'll see a screen like this appear on the right. Click Edit...
When it first displays, the default estimates/percentages will be calculated for you based on Stages and Skills...
If this Epic only requires Front and Backend, then type those in manually (and it will SUM them for you) e.g...
Now close that pane using the X at the top right. You'll see that the Epic is no longer red because the team assigned has both the required skills...
Regarding percentages and skills- I have one stage and 3 skills (dev 33%, UI 33 %, test 33%). I have epic1 which requires all 3 skills and epic2 which requires only dev and test (no UI). In this scenario, it will not graph the epic2 and tells me I am missing the UI skill. I can change the percentage to 50% dev and 50% test, but then that changes epic1 (where I want dev 33%, UI 33 %, test 33%). How do I configure different skill sets for different epics and still graph them within one plan?
For now u can only work on "estimation level" so for example you can say that your EPIC1 nees not 3days of work, but 2 days of Developer and 1 of UI
Problem is that this estimation has to be done at portfolio level and isn't synched back to JIRA
In Portfolio 2.0 you can customize the estimates across the skills in the scope view by adding the estimates into the list of fields shown in the scope view. Then you can update the estimates directly and change the allocation of the estimate across the skills
We've just launched a brand new guide to help you get started with Portfolio for Jira. This guide is a companion piece to our new demo. The guide walks you through use-cases, best practices an...
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