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

Executing transitions via buttons on issue or drag and drop.

Paul Zubkov

This has been on my mind for quite some time and I can't seem to find a good answer, so I hope I can get some help on this topic. Workflow is set up, there are swim lanes, transitions that would add labels and or assign users when needed. When I look at the diagram it looks completely fine. Once we are using the workflow, Post Functions outlined in Transitions are only done if someone clicks on the button with current status and changes issue status by selecting "Transition To ->"

Now, is there a way to make sure that when someone moves an issue from swim lane to swim lane or on the backlog, right clicks the issue to "Send To ..." the same post functions are executed? I am guessing the link between drag and drop and transitions as they outlined in the workflow is not existent and how to establish this?

Thanks.

Accepted answers

John Funk

Hi Paul - Welcome to the Atlassian Community!

Whether you are doing a drag and drop or changing the status via the Send To or Transition To functions, they are still executing the same exact Transition. So whatever post functions you have on the transition in the Workflow should still fire.

All comments

John Funk

Hi Paul - Welcome to the Atlassian Community!

Paul Zubkov

Yeah, I thought so too, but so far if I create two issues of the same type and scope and move one issue via clicking on the status and selecting transition I get completely different results comparing to just drag and drop actions. What makes it even more interesting, it isn't all transitions either.

For instance, if I have a set up similar to Backlog / Kanban where backlog is set up with Deep Backlog -> Backlog ->To Do post actions are not firing when you drag things around the "Backlog" board but when I navigate the ticket via current status button, I get it right. Weird, right?

John Funk

That is very weird. Do the transition names appear with the same wording? And you are sure there is only one transition in your workflow to the given status?

Paul Zubkov

John, thank you for staying with me here. So there is one status to which all other statuses can transition to, the rest of the statuses are restricted by specific transitions. I think at the end of the day, I am going to have to just create a dummy project and try to polish it up. You brought up some good points, it helped me to move in the right direction.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software