we are using one issue type scheme for all projects and after creating projects we are mapping this issue type scheme but now we want to disable one issue from the list.how this can be acheived.If the user select this X issue type he should create any issue under this.
You can edit the issue type and make it available only to the required project. By doing so this will be available only to the project you already added though the issue type has many other projects mapped.
Also, if you need to make it read-only ( ie no one should be able to create though they can view already created jiras ), you can edit this workflow for 'Create' step and change the permission validation from 'Users with create issue permission' to 'an unused permission'.
Hmm, but this would require creating a new issue type scheme and re-associating his projects to this new scheme... Might be troublesome if he has many projects. Is there any other way to do this? I might be missing something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, that's the whole point of the issue-type schemes, it's what they're for.
Mass-association of schemes is a bit of a pain in Jira, and it would be nice to be able to have proper issue-type security in a project (only people matching condition X can create issue type Y), but they're both separate from the core "issue type schemes determine what issue types belong in a project"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm yes, well that makes sense. But harish mentioned he has only 1 issue type scheme for all projects, if he already has many issues using Issue Type A, and he uses another scheme without Issue Type A, he would have to convert the issue type. Not exactly "disabling" I guess. But this is probably the *only* way to do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a feature request tracked here: https://jira.atlassian.com/browse/JRA-6839
I don't think there is a workaround for disabling issue types while still maintaining that issue type inside an issue type scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.