Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

Swimlane

Created by Rosie Jameson [Atlassian], last updated on Apr 29, 2013 1 minute read

スイムレーンは、Agile チームが次に取りかかるべき課題を見分けられるように課題を分類する方法です。

GreenHopper provides:

課題の垂直カテゴリー化は作業モードの "列" 経由で課題のステータスに基づいています。列の設定を参照してください。
課題の水平カテゴリー化は作業モードの " スイムレーン" 経由で課題の優先度に基づいています。スイムレーンの設定を参照してください。

ラベルなし

6 Comments

Alexander Verharen
Dec 06, 2012
How would one establish a Swimlane that shows items added after the start of the sprint?
I would use a JQL statement such as dateCreated >= StartofWeek() or something like that, but not sure how to identify the start date of the sprint.
The main idea would be to see stuff that was not planned for so I can identify and improve on the discipline of scrum. (Over time, this swim lane would not be necessary).
1. Rosie Jameson [Atlassian]
  Dec 16, 2012
  The Sprint Report should help you with this
Anonymous
Feb 19, 2013
We use stories as swimlanes so subtasks are grouped under them. The subtasks are mainly technical, so they make no sense for the testers. They test the main task where the user story is. Is there any way possible to use swimlanes but at the same time show the status for the main tasks and easily move the main task between statuses?
As is, our testers have to expand each swimlane to see if all subtasks have been moved to ready for test. And if so, they test the main task and then move all the subtasks either to accepted or rejected. It would be nice if the testers didn't have to deal with the subtasks at all, but at the moment there's no way to see the status on the main task. Would be nice if if we could say that when all subtasks are ready for test, the status on the main task should automatically be set to ready for test. And that status should be clearly presented on the swimlane. Then there should be some easy way for the tester to move the main task to accepted or rejected and the subtasks should follow.
1. Rosie Jameson [Atlassian]
  Feb 20, 2013
  We have actually implemented this the other way around, i.e. when all sub-tasks have been completed, you will be prompted to move the parent issue (the parent will be moved automatically if you accept the prompt). Please see Transitioning an Issue
  1. Anonymous
    Feb 20, 2013
    But that only happens when all the subtasks have been completed. Not when they are in test... Our testers would prefer to see only the main tasks, as the subtasks are only confusing for them, and our developers wants to only deal with the subtasks. The subtasks can not be closed until the main task have been tested and accepted. Therefore, it would be nice if when our developers have moved all subtasks to "ready for test", the main task is automatically moved to the same. And the status on the main tasks clearly shown in the board so the testers find the ones ready for test.
    1. Rosie Jameson [Atlassian]
      Feb 22, 2013
      
      You may like to log a request for this at https://jira.atlassian.com/browse/GHS