Dead workflow step (can't use, can't delete).

[f***@atlassian.com]

Hello again,

Still testing jira...

I want to delete an "old" workflow step.
This step has no more incoming or outgoing transition.
I have tried to delete it from the active version or from a draft, I never saw the delete option.

So I finally choose to reuse it because it is still using a linked status.
I can add incoming transition from another workflow step,
but I can't add outgoing transition.

I have tried to delete all issues too, with the same results, can't delete workflow step.

Any help appreciated,
Vincent.
--
Post by vgrillot - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

You'll need to make the workflow inactive before you can delete the unused step.
--
Post by sunderhill - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

Why the draft is an active workflow ?

I was thinking that it was just an automated way to do a copy of the current workflow to be edited and then saved at the original place.

With a copy it's working, but I have to replace workflow everywhere.

Is there another simplest way to inactive a workflow ?

TY,
Vincent.
--
Post by vgrillot - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

Before Jira 3.13, you could not edit a workflow that was active. This was a complete pain because to make even the most minor tweak, you had to copy your workflow, edit it, (ideally, test it!), and then migrate the entire set of projects to use it, one at a time.

Jira 3.13 introduced the drafts as a partial fix for this - the "draft" creates the copy, and then allows you to edit some of the workflow elements. Generally, it lets you edit the parts of the workflow that *do not affect issue information*.

As an example, under the old way of doing things, let's say I had a "condition" on a workflow that said "only assignee can resolve the issue" and I wanted to change it to "assignee or reporter". I would have to copy, edit, test the workflow, set up new schemes, and then migrate all the projects using it. The issues themselves are not really affected by this change, because it's related to *procedure* not the actual *information* on the issues, but we still had to migrate. With the new draft facility, I can simply click "publish" and the workflow in place changes, without looking at the issues.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

I'm using Jira Enterprise Edition, Version: 3.13.2-#335

Unfortunately the draft don't allow me to delete a workflow step, even with no transition at all.


Another thing I did'nt understand: on the draft workflow, it's impossible to try to reuse a workflow step who doesn't have anymore outgoing transition.
The error message is : "The step Assigned_OBSOLETE has no outgoing transitions in the Active workflow, so you cannot add any outgoing transitions in the Draft workflow. "
I can't understand why !

TY for help,
Vincent.
--
Post by vgrillot - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

As Nic said there are a few restrictions when using draft workflows. Forget about the draft, make a copy of the workflow and make your changes. Then copy the workflow scheme and replace the workflow with the updated one. Then apply the new workflow scheme to your project...

jamie
--
Post by JamieEchlin - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585

[f***@atlassian.com]

I will do that way.

TY for help,
Vincent.
--
Post by vgrillot - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=33585