The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Showing tasks by Skill Level

Teage Watson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2018

My company is preparing to move to Jira, one of the features our old system provides is "Assignment Class". What this does is allows us to set one or more classes on a task. If the user has the same class or an inherited class, they will see that task in the backlog. The task will be hidden from them if they do not have the matching class bound to their user account. Is there a way that we could achieve a similar result with Jira?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 31, 2018

@Teage_Watson, i'm not 100% sure where you are going w/ this but one option I would look at is the use of either Components or a Custom Field. Then you can create queues based on the field and direct the appropriate agent to 'their' queue. With that said, the tasks are not hidden from them.

Teage Watson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 16, 2018

Sorry I wasn't clear at first. We have multiple developers at varying skill level. In order to try and get the work to the person best suited to the job we have classifications like Developer 1, 2, or 3. If a specific task is more difficult we may classify it as Developer 3. Then a person with the Developer 1 classification would not see it in the TODO list as a task that they should work on next.

I was hoping we could do something similar in Jira

TAGS
AUG Leaders

Atlassian Community Events