| Reporter |
Dan Michaelson (danmichaelson)
|
|---|---|
| Created | Aug 5, 2013 8:49:02 PM |
| Updated | Aug 7, 2013 5:57:43 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Dmitry Krasilschikov (dima) |
| Subsystem | Agile Board |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Create a swimlane and some tasks in one sprint
2. Now try to move some or all of the swimlane's tasks to a different sprint
A) If I change the fix version of the swimlane, the swimlane's tasks wind up in the orphan tray of the original sprint. Then I have to select all of them and change their fix version too. Instead, tasks should move along with the swimlane. This should be how you move a swimlane with all of its tasks to a new sprint.
B) If I first select all or some of the swimlane's tasks and change their fix version, they wind up in the orphan tray of the new sprint. Then I have to select the swimlane and change its fix version too. Instead, expected behavior should be the swimlane should appear in the new sprint, and the tasks under it. Tasks should not lose their swimlane just because I move them to a new sprint. This should be how you move just some of a swimlane's tasks to a new sprint. I thought YT did behave this way previously; seems to have broken in 5.0.
C) If I try to prevent the above frustrations by first editing the swimlane and giving it multiple fix versions for the two sprints, NOW it applies both fix versions to all of the swimlane's tasks (contrary to behavior in A). So I have to go remove the unwanted fix version from some of the tasks. That was extremely frustrating.
Can someone advise as to the recommended workflow to move some of a swimlane's tasks to a future sprint?
1. Create a swimlane and some tasks in one sprint
2. Now try to move some or all of the swimlane's tasks to a different sprint
A) If I change the fix version of the swimlane, the swimlane's tasks wind up in the orphan tray of the original sprint. Then I have to select all of them and change their fix version too. Instead, tasks should move along with the swimlane. This should be how you move a swimlane with all of its tasks to a new sprint.
B) If I first select all or some of the swimlane's tasks and change their fix version, they wind up in the orphan tray of the new sprint. Then I have to select the swimlane and change its fix version too. Instead, expected behavior should be the swimlane should appear in the new sprint, and the tasks under it. Tasks should not lose their swimlane just because I move them to a new sprint. This should be how you move just some of a swimlane's tasks to a new sprint. I thought YT did behave this way previously; seems to have broken in 5.0.
C) If I try to prevent the above frustrations by first editing the swimlane and giving it multiple fix versions for the two sprints, NOW it applies both fix versions to all of the swimlane's tasks (contrary to behavior in A). So I have to go remove the unwanted fix version from some of the tasks. That was extremely frustrating.
Can someone advise as to the recommended workflow to move some of a swimlane's tasks to a future sprint?