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:
this is the first post-function which moves the issue to the step you chose. it will do exactly what it says....moving the issue to the destination step where a Status is linked.
i can't figure out how you've had a global "Back" Transition that (let me guess) was available in every Workflow Step and moves you back to the previous step.
i wonder how this transition should know where the issue was transitioned from cause there can be different steps that allow transitions to several destinations. this needs to be tracked (maybe from transition history) to work correctly.
what exactly is the goal you want to reach?
|STEP A|STEP B|STEP C|STEP D| (lets assume this is your worflow direction left > right)
when an issue is in |STEP D| you want a transition that moves the issue back to |STEP C| so you call that one "Back"
how was that working before? the only way i know is to add a transition and set destination step to the previous.
i might be completely wrong about this....if so lets wait if any user user here has a clue on that
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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