You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This question is in reference to Atlassian Documentation: Understanding stages and skills
The JIRA Portfolio adds the concept of percentages for the stages and skills, but the documentation doesn't explain how this impacts planning. I also see that for issues I can specify specific skills, but when doing that I will assign either story points or days/hours. So, why the percentages?
A suggestion is to customize the time allocated to that skill that is either not needed or doesn't need to be what % is defaulted to. In the Scope listing, add the Estimates column to the list. Then modify the allocations manually in the list. In this way I have been able to set a given skill to 0 and remove those errors if that skill is not needed.
Same question here, why do we always end up with the following error message: Missing Skill for sub Task.
Even if we have covered all the skills for our only stage by the teammates (virtual users), some of the Sub Tasks and corresponding Stories cannot me planned in the Portfolio because of that error.
The work around is to define one or more user with all the skills.
Why doesn't it accept to plan according to user availability based on the fact that our team does actually cover all the stage's skills?