Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
A swimlane is a horizontal categorisation of issues in Work mode on a board.
次の表に示すように、スイムレーンを設定するさまざまな方法が選択できます。
Note that only the owner of a board (or a person with the 'JIRA Administrators' global permission) can configure a board's swimlanes.
On this page:
| ベース スイムレーン | 説明 |
|---|---|
| クエリ | スイムレーンごとに JQL クエリーが 1 つ設定されます。（下記を参照）。既定では、2つのスイムレーンが作成されます。
JIRA 「優先度」フィールドの他の値にマッピングされたスイムレーンを追加すること、またはスイムレーンを分類するために別のフィールドを使用することができます（以下の例を参照）。 |
| ストーリー | One parent issue per swimlane (i.e. each swimlane contains all of the parent's sub-tasks), with issues that have no sub-tasks appearing below. Example (click to enlarge):  |
| 担当者 | スイムレーンごとに担当者が 1 人設定され、未割り当ての課題はスイムレーンの上または下に表示されます (選択可) |
エピック (in GreenHopper 6.2.1 and later versions) | (Scrum boards only) スイムレーンごとにエピックが 1 つ設定され、どのエピックにも属さない課題は、スイムレーンの下に表示されます。 |
| スイムレーンなし |
別の種類のスイムレーンを選択する
ベーススイムレーンを JQL クエリ、ストーリー、担当者のどれにするか（または、スイムレーンなしを）選択する方法は、次のとおりです：
- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
- スイムレーンタブをクリックします。
上記の分類にしたがい、「ベーススイムレーン」のドロップダウンで、クエリ、 ストーリー、 担当者またはスイムレーンなしのいずれかを選択します。
Screenshot 1: the 'Board Configuration' screen — 'Swimlanes' tab.
クエリをもとにしたスイムレーンを変更する
スイムレーンが（ストーリーまたは担当者ではなく） JQL クエリをもとにしている場合は、次の手順で JQL クエリの作成、削除、変更ができます
- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
スイムレーンタブをクリックします。
スイムレーンがクエリをもとにしている場合は、次の表とスクリーンショット 1 （上）に示すように、スイムレーンを編集できます。
編集項目
操作方法
新規スイムレーンの追加
In the blue area, type the 'Name', 'JQL', and optional a 'Description', then click the 'Add' button. Your new swimlane is added in the top swimlane position.
スイムレーンの名前の変更
スイムラインの「名前」エリアをクリックして、既存の名前を変更し、「更新」ボタンを押します。
スイムレーンの JQL 変更
Click in the 'JQL' area of the swimlane, modify the existing JQL and click the 'Update' button. (See the examples below for some suggestions.) For syntax, see the JIRA JQL documentation.スイムレーンの削除
スイムレーンの右側にある「削除」ボタンをクリックします。
スイムレーンの移動
Hover over the vertical 'grid'
icon, then drag and drop the swimlane up or down to its new position.
スイムレーンを設定する JQL のサンプル：
特定のコンポーネントに所属する課題すべてを表示します。（例：'User Interface'）：
project = "Angry Nerds" AND component = "User Interface"
24 時間以内に期限が来る課題すべてを表示します。
due <= "24h"
特定の優先度を持つすべての課題を表示します。例：
priority = "Minor"
および
priority = "Major"
For more details, see the JQL documentation.
概要
コンテンツ ツール
アプリ
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
38 Comments
Mark Gibaud
May 24, 2012I would like to put "everything else" in a position elsewhere than the very bottom, as I'd like a swimlane called "next version" at the bottom. How can I best achieve this? What is the equivalent JQL for everything else such that I can create a similar swimlane which I can then position myself?
Anonymous
Jul 24, 2012Did you ever get an answer to this? We like the story swimlanes, with the exception that you lose priority order if a story (or stories) don't have sub-tasks.
Daniel Eichling
Jan 18, 2013I hope this doesn't get lost because this is one of the biggest complaints we have currently with the new boards. All the other features are great but we would really like a way to have a swimlane that could be under the "default" so that we don't always have to create filters for what should be "standard" work!
Amanuel Burhan
Aug 15, 2013Hey,
I was also annoyed that the "Everything Else" column was at the bottom. So to get around it I set up a separate "Everything Else" column (which I dragged to the top) with the inverse conditions. I called this new swim lane "All other stories". but you could leave the name as Everything Else and apply the same conditions.
For example: 2 swim lanes Design tasks & All other Stories ( and the third swim lane "Everything Else")
In the Design Swim lane the JQL statement was Summary ~ Design
In the All other Stories swimlane the JQL statement is Summary !~ Design
This does mean that the design tasks had to have the work "design" contained within the Summary AND the All other Stories had to NOT contain the work "design"
I know this is a bit of a work-a-round but it gets the same result as long as you're not having loads of swim lanes.
Note: - If you do have more swimlanes - then bear in mind that the JQL statement (for "All other stories") will have to incorporate the corresponding NOT statement. i.e. Summary !~ design AND Summary !~ SPIKE etc.
Hope this helps but also hope JIRA allows you to drag the default "Everything Else" swim lane to the top
Anonymous
May 28, 2012Does anyone know if you can set up a swimlane constraint like you can a column constraint?
Anonymous
Jun 05, 2012Swim lanes are great for organising the Work mode.
Any chance of incorporating them into the Plan mode?
I have quite a few projects in my Rapid Board, swim lanes in the Plan mode would provide a neat way of viewing my backlog.
Anonymous
Aug 15, 2012hey,
Does anybody know how can I change the priority of a parent issue when using the swimlane by stories?
Thanks
Tal
Rosie Jameson [Atlassian]
Aug 20, 2012You can drag the issue higher or lower to change its rank. To change its priority, you will need to edit the issue.
Jason Brison
Aug 28, 2012Hello,
Will there be plans to allow us to drag issues between swimlanes?
Rosie Jameson [Atlassian]
Aug 29, 2012You may like to watch/vote/comment on GHS-4518 - Getting issue details... STATUS
Marko Djukic
Sept 07, 2012Salem Korayem
Oct 22, 2012For functions like QA and Design that serve multiple projects at the same time, it would be great to have swimlanes based on Projects/Component.
Currently this is doable by adding multiple queries for each project which is cumbersome. Any plans on having this in the near future?
Anonymous
Oct 31, 2012What permission grants access to create swimlanes? Some members of our project can add new swimlanes, while some can't. Is there a per-project setting or just a global setting somewhere?
Jason Brison
Oct 31, 2012Swimlanes are configured in the Board Configuration options which can only be accessed right now by the board owner
Anonymous
Nov 02, 2012Thanks Jason. That answered my question.
Anonymous
Nov 06, 2012We are quite keen on improvements to the story-based swimlanes since we would like each story to keep it's priority (visually) when it's dragged between columns.
We like the Kanban flow, though it is quite hard to quickly identify if somebody is working on something with a lower priority than they should. Then we have to use the "classic" boards which obviously has its own flaws.
Is there a plan to improve this flow?
Anonymous
Nov 22, 2012Subtasks are not shown automatically under a story, if you use stories for swimlanes and the subtasks are not covered by your filter. I assumed that all subtasks would be visible, regardless of the filter, as long as the story itself matched. Why is this design decision made?
Rosie Jameson [Atlassian]
Dec 03, 2012You may like to watch/vote/comment on GHS-6309 - Getting issue details... STATUS
Anonymous
Dec 12, 2012I would like to have swimlanes based on fixVersion - is this possible (swimlane for each unreleased fix version)
but can only figure out how to create swimlanes based on a single fixVersion -
Can anyone tell me how to do this?
Anonymous
Dec 13, 2012You have to set up each fixversion swimlane manually. Put in the jql as: fixversion = blah for each swimlane.
We use this a lot. It's crap. It should be dynamic.
Rosie Jameson [Atlassian]
Dec 16, 2012You may like to watch/vote/comment on GHS-5720 - Getting issue details... STATUS
Pavel Bulanov
Mar 16, 2013So far any swimline can indicate only one filter - i.e. by specific version, component, priority, etc.? Is there no way to "iterate" through all versions or components or priorities - like it's happening for user-stories and assignees in pre-defined swimlines? Is it complicated to be able to have swimlines shown by any field, not just those two? Are there any tricks with it?
Rosie Jameson [Atlassian]
Mar 18, 2013Hi, you may like to watch/vote/comment on GHS-5720 - Getting issue details... STATUS (version-based swimlanes) and/or GHS-4669 - Getting issue details... STATUS (field-based swimlanes in general)
Anonymous
Jan 10, 2013I would like a swim lane for tickets related to Epics (versus tickets not part of any epic), but it looks like swimlanes are only defined with JQL. Is it possible to access the GH 'Epic' field in JQL?
Rosie Jameson [Atlassian]
Jan 13, 2013Epics will be searchable in JQL in the very near future — please watch our Release Notes.
You may also like to watch/vote/comment on GHS-6426 - Getting issue details... STATUS (built-in option for Epics-based swimlanes)
Anonymous
Jan 25, 2013It seems like the swimlanes used to filter the view by Stories isn't working. It works for Assignees but not for Stories. This is a problem since we can't see subtasks for the stories in the columns. This happend after the last update recently and looks like it might be a bug.
Anyone else get this problem?
Anonymous
Feb 07, 2013Yes I have this problem also
Serge Kruppa
Jan 29, 2013There seems to be a hard limit of 10 swimlanes in Greenhopper, including "Everything Else". I configured an 11th swimlane and it didn't show up on the Agile Board (Kanban) work view. No error, it just isn't displayed. Is that a bug, a configurable limit or a design limit?
The issue is that I'm trying to create a Kanban board with swimlanes for all of the 20+ components that my team is working on. That way I can minimize the amount of clicks to see dev. work in progress for each component - very convenient, except I'm stuck right now.
Any feedback would be most appreciated. Thanks in advance.
Rosie Jameson [Atlassian]
Jan 30, 2013I haven't encountered this limit. Please note that a swimlane won't appear on your board unless it currently contains issues. For further assistance, you may want to contact http://support.atlassian.com
Serge Kruppa
Jan 30, 2013You are absolutely right, there was no issue matching the JQL query that I wrote, hence nothing to be displayed. Having created a first issue for that new component, it does show up in its own swimlane. Many thanks for your prompt response!
John Hermary
Jan 30, 2013I have a project named EPT that I tried adding as a swimlane to my Kanban board, however it doesn't show up on my board. I tried each of these JQL queries:
project = EPT
project = 'EPT'
project = "EPT"
but none of them work. My other projects show up in the swimlane no problem. Any suggestions please?
Rosie Jameson [Atlassian]
Feb 06, 2013You may need to check whether the project has been included in your board's filter? If that doesn't help, please contact http://support.atlassian.com
marco san juan
Feb 25, 2013hi
we noted that, by configuring stories as swimlines, when a high priority story with top rank doesn't have sub-tasks, it's degraded down as "other issues", so the team can't see it at the top of the board to be the first to be started, as occurs on phisical boards.
it's really a unexpected behavior that is forcing us to create sub-tasks for very small stories.
do you plan tu prevent this behavior by forcing stories to be presented as swimlines even those without sub-tasks? we think priority rank should allwais be more important than presentation or anything else.
(we are using a installed GH v6.1.3.2)
thanks!!
Rosie Jameson [Atlassian]
Feb 25, 2013Hi, you may want to consider basing your swimlanes on Queries (instead of Stories).
Or if that doesn't meet your needs, you may like to log a feature request at https://jira.atlassian.com/browse/GHS
Jim Lesko
Jun 27, 2013We have this problem as well, if there is a good query-based solution out there I'd love to get a chance to see it.
Ivo
May 22, 2013When a user story got sub tasks the estimation of the user story is not shown on the board. How can I configure this?
Rosie Jameson [Atlassian]
May 24, 2013Hi, you may like to vote, watch, or comment on GHS-6531 - Getting issue details... STATUS and/or GHS-8134 - Getting issue details... STATUS
MattS
Jul 25, 2013There are a number of helpful tips in these comments that could usefully be added to the main part of this page. E.g. swimlanes based on queries don't show up unless at least one issue matches, and if an issue could match multiple queries it is displayed in the first swimlane that the issue matches