Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,367
Community Members
 
Community Events
176
Community Groups

Can I mark the skills an issue needs?

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).

1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events