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'.
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"
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.
[Note: So it was my turn for Friday Fun and sadly I was sick thanks to rubbish sinus infection... so apologies to most of Europe and Asia for the delayed post. However, I finally got out of bed for t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs