I have a project with two issue types. Old-Item and New-Item. There are also two workflows, Old-Workflow and New-Workflow.
I would like to be able to allow all the Old-Item issues to continue with the Old-Workflow, but I do not want to allow Old-Item s to be created. How can I do this?
Based on the feedback I think I know what my options are for the original question. Does the answer change at all if I ddo not have a need for the tasks to be on a separate workflow? As far as I know, the issue type need to be in the Issue Type scheme for the project, which is where the "Create New Issue" options are fed from.
Thanks for your feedback. I will consider it. I found a temporary workaround of modifying the Old-Workflow "Create" transition to require Admin privileges. This will prevent users from creating the issue type, but they could still waste time filling out the form and won't know they can't create it until they press the "Create" button.
Just to add to the first point of restricting the issue types by admin permission, you may also add a field "message custom field for edit", associate that with the screen scheme for the Edit for that issue type and put in some HTML in red colour stating that "Do Not Create Issues of This Type". This will help users not wasting time.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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