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.
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot