Forums

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

Need only one Assignee on creation, but multiple assignees for reassigning

Sarah Elmer
Contributor
September 15, 2011

In a project in JIRA Studio I want only one assignee listed for the creator to choose from (done through Permissions); however, after creation, I need the multiple assignees listed for reassignment of the issue. How can this be done?

3 answers

1 accepted

0 votes
Answer accepted
Sarah Elmer
Contributor
February 13, 2012

Found obscure answer to my question during research. Secret is to remove the Assignee field on the creation page. This will not affect the Assign tab on future actions nor will it affect the list of Assignable users.

0 votes
Nikhil Naoghare
Contributor
September 18, 2011

Hi Selmer,

This can be done through the Components. as there is the hierarchy of the assignees according to which the created issues are assigned. That is, the default assignee for any issue is the Project Lead, but if the issue is crated for specific component then as per the component lead, assignee changes. It means, if we have defined a Component A and its corresponding assignee is User1 then whene ever any issue is created and it has the component A then the issue will be assigned to User1 automatically.

The reporter doesnot need to add the assignee manually, it will be done by default. So, for this you need to add the Component for the project and remove the assignee field from the create issue permission.

Make sure that the component lead defined must have assignable rights in the project. And, once the issue is created, you can assign the issue to the user who else have the assignable rights. Please try this if possible.

Thanks,

Nikhil.

0 votes
MinC
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.
September 17, 2011

Multiple assignees for a single issue is a limitation in JIRA and this feature request has been set to 'Won't Fix': https://jira.atlassian.com/browse/JRA-1397

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events