Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,888
Community Members
 
Community Events
168
Community Groups

How to move tasks from one swimlane to another?

 

3 answers

1 accepted

1 vote
Answer accepted

Edit the task that needs to move, changing the data such that

  1. It stops matching the selection rule for the swimlane that it is in now
  2. It starts matching the selection rule for the swimlane you want it in

Hi Nic, is it possible to move tasks between swimlane by using drag and drop?

No, because a swimlane is a grouping selected by data on the issues, and there's no way JIRA can know what moving between swimlanes might be doing in most cases.  It's ok for the clear simple standard ones (e.g. change the story or assignee it belongs to), but as soon as any clever filters are used, you need rules which can't be fixed.

Think of a simple example of two swimlanes - one is "priority = high" and the other "colour = blue".  What do you need to change and what should you change if a user moves an issue from one lane to the other?

 

Hi @Nic Brough _Adaptavist_ ,

I have requirement and need you help.  

 

We have a sprint board and we have stories and Subtask for those one. Lets says if have a stories DDD and Subtask below it are 1- Subtask1 , 2 -Subtask 2  etc.

 

When Dev team work on it, only Subtask move from one Column to another one, but not the stories

 

is there Anyway i can only have stories only moving from one column to another in swimlane ? 

Columns are collections of issues by status.  So move your issues from one column to another by moving them through the wrorkflow.

This is a limitation of Jira, which limits the creative flexibility of Kanban (Azure DevOps has this capability).  As a workaround:

- Create a custom field "Swimlane" and assign the selection choices of each swimlane (e.g. 3rd tier, Escalation, Product Group, Help Desk, etc.).  Add the custom field to the issue so you can select it upon creation.  The board swimlanes will be based on JQL where Swimlane = each selection choice.

- Create another custom field doing the same thing, except title it "Automation Swimlane".  A

- Add a board column for each selection choice of the swimlane with a status of the same selection choice name.

- Create an automation for each swimlane move to state: when Automation Swimlane status is changed from [any] to 3rd tier, Escalation, etc. then update the custom field "Swimlane" to the respective status (3rd tier, escalation, etc.).

Now, you can simply drag and drop an item in one swimlane into it's respective swimlane column, and the item will get moved into the correct swimlane.  You'll also need to hit refresh for it to be reflected in the browser.  

Really, this should be part of the core product but I hope this helps!

There is one non-standart easy way that can give you 2 easily controllable swimlanes - by misusing the Flag capability and setting swimlanes by queries. Then you can get two lanes - one with filter "Flagged is not empty" and second without any. Works as you need - not via drag and drop, but via right-click and set/remove flag.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

175 views 1 6
Read article

Atlassian Community Events