Separate permission scheme scoped to issue type?

[Pete P]

I have a project with two issue types.  I want to prevent users from creating issues on one of the two types as it is replaced with newer type.  However I still want users to be able to work/resolve pre-existing issues of this issue type being sunset.


What is the best way to accomplish this?  I don't see a way to associate more than one permission scheme per project.

[John Funk · Accepted solution]

Hi Pete,

You would probably have to create some type of Validator on the Create transition to not allow the certain issue type. There is no way to "disable" an issue type. If you remove it from the issue type scheme, it will make you change all of the existing issues to a new type. 

[Pete P]

Thanks again @John Funk , the validator on Create should do the trick!

[Mohamed Adel]

@Pete P 

as long as you have only one project this can be done with a plugin. I applied the same with a simple validator using ScriptRunner for Jira, on Create Issue Transition.

i hope this would help

Adel

[Pete P]

Thanks @Mohamed Adel , good answer with code sample.  I give it to John as came in first