-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
1
-
I would like to be able to drag and drop issues across swimlanes to re-categorize issues. Parse the JQL used to define a swimline, and update the subject issue to make the it match.
Example use case:
With swimlanes defined as follows:
| Swimlane A | priority=High AND assignee=engineering |
|---|---|
| Swimlane B | priority=Medium AND assignee=support |
| Swimlane C | priority=Low AND assignee=sales |
Dragging an issue from Swimlane B and dropping it in Swimlane A should update the issue's priority to High and the assignee to engineering. Likewise, dragging an issue from Swimline A and dropping it in Swimlane C should update the issue's priority to Low and the assignee to sales.
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
-
- Future Consideration
[JSWSERVER-4518] Ability to update issues using drag and drop between swimlanes
+1
Even if this is implemented as swimlane transitions and you have to manually tell it which fields to update when moving from X to Y swimlane, this feature would be very useful. Voted!
Yann Grenier
added a comment - +1. For even more flexibility, add "Post Function" like behavior. For example, if one of my swimlanes is configured to group issues that "Due Date is not Empty", when dragged from one swimlane to another, an issue field can be purged or populated.
Yann Grenier
added a comment - +1. For even more flexibility, add "Post Function" like behavior. For example, if one of my swimlanes is configured to group issues that "Due Date is not Empty", when dragged from one swimlane to another, an issue field can be purged or populated. 
Devu Heda
added a comment - Absolutely, I would like to move my issues between swimlanes ... and our swimlanes are not Assignee based we have swimlanes based on other custom fields
Devu Heda
added a comment - Absolutely, I would like to move my issues between swimlanes ... and our swimlanes are not Assignee based we have swimlanes based on other custom fields 
Jenny Aquilno
added a comment - I concur. I'm surprised that I cannot transition an issue between swimlanes. Please add this functionality. It would make the Kanban board so much more useful and agile as the name implies. Thanks!
Jenny Aquilno
added a comment - I concur. I'm surprised that I cannot transition an issue between swimlanes. Please add this functionality. It would make the Kanban board so much more useful and agile as the name implies. Thanks! We keep our backlog unassigned but prioritized. When a developer is ready for work it would be great if they could just drag and drop the next card to their swim lane to assign it to themselves.
Milun Tesovic
added a comment - +1 very useful for many reasons 
Michael Burton
added a comment - As a new user, it was surprising to me that I couldn't just drag items from one swim lane to another. I'm not sure how valuable the swimlane feature is without this. I was planning on using it to capture small intermediate milestones, but if it's not easy to move items between swimlanes then its value isn't clear to me.
Michael Burton
added a comment - As a new user, it was surprising to me that I couldn't just drag items from one swim lane to another. I'm not sure how valuable the swimlane feature is without this. I was planning on using it to capture small intermediate milestones, but if it's not easy to move items between swimlanes then its value isn't clear to me. 
Renee Steiner
added a comment - This would be extremely useful. We have swimlanes by assignee and Columns for "Needs Validation" and for "In Validation". Dragging from one person's Needs Validation to another person's In Validation would be great!
Renee Steiner
added a comment - This would be extremely useful. We have swimlanes by assignee and Columns for "Needs Validation" and for "In Validation". Dragging from one person's Needs Validation to another person's In Validation would be great! We have similar basic jql for our swimlanes:
| Swimlane | JQL |
|---|---|
| Interrupt | "Class of Service" = "Time Critical" |
| Normal | "Class of Service" = Normal |
| Long Term | "Class of Service" = "Long Term" |
I would like to be able to move my issues between the swimlanes, and just have the issue updated automatically to match the JQL (ie, changing class of service from Long Term to Normal, etc) the same way I can move an issue from Open to In progress.
We are using GH 6.0.1
With the current solution, how to build a real Kanban board with JIRA ?
I mean, in Kanban you are supposed to distinguish, for each major "states" in your pipeline the "todo", and the "done" state.
JIRA does not provide these "sub-state" out of the box.
As a consequence, you have to manage it by yourself:
How are we suppose to work in Kanban with JIRA ?
I vote.