-
Suggestion
-
Resolution: Fixed
-
Linux standalone
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We need to modify a Workflow Scheme associated to 50+ projects. (add a new issue type with a different workflow). In order to do this, we need to change the workflow scheme for these 50+ projects.
What we request is to provide the possibility for changing the workflow scheme of multiple projects at once.
- duplicates
-
- Closed
-
- Closed
- relates to
-
- Closed
[JRASERVER-25121] Modify Workflow Scheme for multiple projects at once
Eric Rawlins
added a comment - Rodolfo -
I've come across this problem many times. I'd love to edit and publish a draft workflow scheme like a workflow but in the meantime this is easy enough to change directly in the database if you're so inclined. I routinely add new issue types to existing workflow schemes without disassociating them from existing projects.
Add a new row to table workflowschemeentity and set the following values:
ID = Next sequential #
SCHEME = The ID of the workflow scheme you are modifying, from table workflowscheme - or just look for another entry referencing a workflow you recognize and get the number from that
WORKFLOW = The text of the workflow name (match column workflowname from table jiraworkflows)
issuetype = The issue type ID (match column ID from table issuetype where issuetype.pname = the issue type you're looking for, or look at the ID in the URL when viewing the issue type in the browser)
Restart JIRA and verify when viewing the workflow scheme you can click-through to the workflow so you have it configured correctly. It's a workaround, but this is by far the easiest way I've found to modify an in-use workflow scheme if all you're doing is adding a new issue type (it won't work for modifications)
Eric Rawlins
added a comment - Rodolfo -
I've come across this problem many times. I'd love to edit and publish a draft workflow scheme like a workflow but in the meantime this is easy enough to change directly in the database if you're so inclined. I routinely add new issue types to existing workflow schemes without disassociating them from existing projects.
Add a new row to table workflowschemeentity and set the following values:
ID = Next sequential #
SCHEME = The ID of the workflow scheme you are modifying, from table workflowscheme - or just look for another entry referencing a workflow you recognize and get the number from that
WORKFLOW = The text of the workflow name (match column workflowname from table jiraworkflows)
issuetype = The issue type ID (match column ID from table issuetype where issuetype.pname = the issue type you're looking for, or look at the ID in the URL when viewing the issue type in the browser)
Restart JIRA and verify when viewing the workflow scheme you can click-through to the workflow so you have it configured correctly. It's a workaround, but this is by far the easiest way I've found to modify an in-use workflow scheme if all you're doing is adding a new issue type (it won't work for modifications) 
Rodolfo Romero
added a comment - Any update on this feature request? 
Don Masten
added a comment - Would be nice if you could create a "draft", edit that "draft" and publish it. Just like editing a workflow.
Don Masten
added a comment - Would be nice if you could create a "draft", edit that "draft" and publish it. Just like editing a workflow. 
Related with this issue: https://jira.atlassian.com/browse/JRA-5254
Will be implemented on v6.0