Change issue type but only admin

[Georgi Kostadinov]

Hello

I would like to be able to change between different issue types but this to be possible only by admins of the project, not by users. How to do that?

Thank you

[Josh Costella · Accepted solution]

Hi Georgi,

I would love to know more about your use case to fully understand the ask. You can put validators on the create transition but that would not prohibit being able to change the issue type. 

You would need to make sure all the issue types were sharing the same workflow if you wanted to change the issue type via the issue type field. Otherwise, you would need to use the Move feature. That can be restricted via the project permissions scheme. 

More info on the permissions can be found here: https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html

You would want to make sure that only the Administrator project role was added to the Move permission.

[Georgi Kostadinov]

Thank you @Josh Costella . 

Yes the three different issue types has same workflow but I am wondering still if its possible to have this logic: when creating new issue -> go always by default to issue type 1 and then only Admin user to be able after review issue to be able to change to Issue type 2 if required?

Is the mentioned logic possible only through change the Issue type field or I need to look to Move functionality?

[Josh Costella]

So, to prohibit creation of the other issue types, you would need to put a validator on the create transition in the workflow that would stop creation of them unless it was Admin. The other issue types will still show in the drop-down but only designated Admins would actually be able to create them. Everyone else would get an error message that you can customize.

Once you did that, you would be able to just use the issue type field to change to another issue type and move would not be required. You still need to make sure that Admins have the move permission though. 

[Kian Stack Mumo Systems]

@Georgi Kostadinov, 

The most likely explanation is that the project admins have the "move issue" permission and standard users do not.

Move issue Permission:

Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission.