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: Scheduling
We use different technologies and not all of our team have the same skills (eg. some know Java while others know Ruby). The estimation estimator – the thing that fills out the skills estimation in the Scope view – just dumbly assigns time by the default percentages.
It would be really useful to be able to mark what skills an issue requires and have the estimator use that information to inform its scheduling. In addition to the above example of Ruby vs Java, some tasks don't require the Design phase (such as simple Tasks).
You could add that in the components, for instance? You could also have a multiselect list that allows for more skills to be marked, such as Java, CSS and MySQL. A user could have filters open saying if not assigned, opened and component in (list of skills), allowing your individual users to only see issues in the backlog they have the skills to solve.