We have a scenario where project administartors need to be able to move a simple bug issue type to a more complex bug issue type after triage has been done and it is determined how a bug will be fixed. Is it possible in JIRA 4.4.5 to set it up so the complex bug issue type does not show up in any create issue drop down at all and only shows when a project admin uses the move function?
Ok, then how about we simplify the ask...
Can we restrict "create issue" to a limited group for only one issue type in a project while the other issue types are open to "anyone"?
We tried that using the workflow but the solution was inelegant. The user was able to select the issue type in the drop down and didn't get an error until they had filled out teh create screen and clicked on create.
Nope, similar problem. You've already run into the clumsy workaround by blocking it in the workflow.
But it is a bit easier. I think the behaviours plugin can do this for you.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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