nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding Outgoing Transition to Active Workflow

Cory Levine

A previous admin set-up a workflow/schema with a closed status that does not have any outgoing transitions. I need to add a re-open status to the workflow and allow the users to transition the status of an issue from "closed" to "re-open", but the system will not allow me to create the transition - stating "the step 'closed' has no outgoing transitions in the active workflow, so you cannot add any outgoing transitions in the draft workflow."

Is there any way around this? Or is my only alternative to create a new project with the correct schema/transitions and then migrate the existing issues to it?

Accepted answers

Thomas Schlegel

Hi Cory,

according to https://confluence.atlassian.com/display/JIRA/Configuring+Workflow this is correct. You cannot do this with an active workflow.

But you don't have to create a new project. Create a copy of your existing workflow, edit it and add it to a new Workflow Scheme. Add this scheme to the existing project. Every issue will be converted to use the new workflow, but this is maybe better than creating a new project.

Best regards

Thomas

All comments

Thomas Schlegel

Hi Cory,

according to https://confluence.atlassian.com/display/JIRA/Configuring+Workflow this is correct. You cannot do this with an active workflow.

Best regards

Thomas

Cory Levine

That did it - thanks for the quick and accurate reply.

Thomas Schlegel

you're welcome :-)

John Rojas

Thank you so much for posting this answer. IT WAS SO HELPFUL !!

I wasted about 2 hours before finding this answer.

I really don't like and understand why Atlassian had to make this SO COMPLEX, UNINTUTIVE, AND DIFFICULT TO USE. URGH !!

JIRA is now officially the most difficult tool to use at our disposal.

Sergii Mostovyi

Agree, this part is

SO COMPLEX, UNINTUTIVE, AND DIFFICULT TO USE

Nitin Malhotra2

Just jumping in here Thomas... i have the same problem.

So I have this workflow which is part of 2 Workflow Schemes. Each of these schemes are attached to projects with thousands of historic & current issues/items.

What's the step-by-step process if I wanted to create a transition out of 'Deferred' (to 'Ready for Dev') in this workflow?

Is it..

1. Create copy

2. Edit Copy (add the transition)

3. Add this 'new' workflow to the 2 schemes?

4. Remove the 'old' workflow from the 2 schemes?

Confused with the last 2 - especially since it'll all explode like a big bang if issues do not stay in their old statuses!

Cheers mate.

Anoop Wilson

I have some 3000 projects using same scheme.Hence I need to manually associate the new scheme with all the 3000 projects.Any other methods?

Jobin Kuruvilla [Adaptavist]

In 6.x, you can edit an active scheme. You don't have to do it project by project.

Yves Martin

You also can automate such tasks with JIRA CLI https://bobswift.atlassian.net/wiki/display/JCLI/JIRA+Command+Line+Interface and a loop in any scripting language

Alex S

Not entirely true, in 6.x you can update active workflows except for closed transition. You cannot add a transition (reopen) to closed transition while active.

vitaliy zapolsk1

I have workflow with global transition from everywhere to Closed.

But JIRA thinks Resolved is a terminal state! And doesn't allow to add outgoing transition, just like topic started described!

Yves Martin

Do you have "close" permission in your permission scheme ? Or is there any condition registered in your transition to "Closed" that may prevent it to be available for your user ?

vitaliy zapolsk1

The case is about inability to save draft workflow. Jira allows to edit active workflow then refuses to save your work. You must abandon your changes and create a copy of workflow then edit it and replace old workflow with a new in the scheme.

Nicola Bearman

It's just great how they tell you you can't do this after you've spent all the time adding the transitions...

Yves Martin

From https://community.atlassian.com/t5/JIRA-questions/How-to-reopen-a-closed-issue-in-Jira/qaq-p/434925

I found reference to Atlassian JIRA KB quoting official product documentation section: https://confluence.atlassian.com/jirakb/cannot-add-transitions-or-delete-steps-in-draft-workflows-203392961.html

Jeff Aguilera

So, 5 years later and this is still not any better. This is one of the reasons that I ALWAYS give Atlassian 0 stars when they ask for a review; and would NEVER recommend their product to ANYONE.

unknown

amen to that. ridiculous.

unknown

Hard to believe this is still an issue 7 years after it was first reported- UGH!!

Jeff Aguilera

You must be new here. 5-10 years to solve simple usability problems seems to be the norm. I wish I were being cynical or exaggerating.

Joe Elizondo

It would be helpful if someone could explain what this error even means? In my case I had an 'open' state that I removed all the transitions from and pointed them to a 'ready for dev' state instead. Then later I decided to move them back to open, the way they were originally working and moving them back triggered this error. Open had outgoing transitions originally, I moved them and then put them back, and it tells me there are no outgoing transitions? What is it even saying?

Greg Macdonald_yq8294

@Jeff Aguilera You must be an optimist. You think that at some point they will fix it.

L. Cornelius Dol

There is a relatively painless way to fix this (apart from losing the changes already made to the workflow) without reassigning the workflow scheme to every project that uses it.