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; } } }

Workflow Back Button does not work.

MayBe

We are using a global transition which we named "Back". This transition uses the target destination (-1) no result step (loop). Till now this worked perfectly as a Back button to the last ticket status.

Now this button stoped working from one day to another for all workflows. Now my question:

Did we misinterpret the functionality of this generic destination step?
Is there a special condition to make it work again?

Accepted answers

C_Faysal _CFcon_

what did you changed?

you say it worked before...so i suggest something changed to break it up...

All comments

C_Faysal _CFcon_

what did you changed?

you say it worked before...so i suggest something changed to break it up...

MayBe

Only thing that i remember is that I activated the feature "Unassigned Ticket". But the project has a default user.

C_Faysal _CFcon_

that transition has a "status" linked with doesn't it?

how & where you added the "target destination (-1)" and what is that? i mean this value should be the status itself reduced by 1 if i get it right.

i've never seen sth like this before but i will try to reproduce if i can

MayBe

Do you mean this? "Set issue status to the linked status of the destination workflow step. "