Today, in Scrum and Kanban boards, it is possible to have Swimlanes based on

• queries
• stories
• assignees
• epics
• projects
• None

Now, the obvious request is to have swimlanes based on 

• component
• team
• label
• fix version

in Scrum boards and in Kanban boards.

It could all be so easy.

Looking for this as well. Only option is to manually add versions for swim lanes, which is a pain..

+1

+1

That would definitely be an improvement, and a very big one for our team.

Jira certainly has a lot to do, but isn't this issue a quick win ?

Cheers

would live this as well, using queries for every fix version is very tedious

@Jenna Corbett:        If they fix it now it will be too easy to break the record. They should give it another 10 years. 20 years will be hard to break.

This request will be celebrating it's TENTH year anniversary soon. Ten years. A decade. This must be a record for longest time to give users what they asked for. 

I think with 403 votes, this is far past the point of gaining interest and should be something put in place. 

Would very much like this for our team - it would save us from so much manual configuration

My team would like to be able to select fix version as a way to define different swim lanes to manage our releases. Maintaining every separate swim lane is a massive overhead which we don't want. Please prioritise this request. Thanks

My teams is working on Kanban boards, and we are using versions for short term planning (we find it more flexible than the Scrum board). For planning, it would be really useful to see swimlane per version, thanks.

What do the devs at Atlassian do all day?

Seems like all the useful functionality is only available in paid 3rd party add ons.

Let's hope Microsoft Teams crushes these guys into delivering something that looks like it's from the 3rd decade of the millenium and not the first!

Very much interested in basing swimlanes on FixVersion in Scrum/Kanban boards!

I've resigned to using Epic swimlanes, but it would still be a great feature to use Versions.

To everyone who is interested in this feature: make sure you add your vote! It will help this ticket in climbing up to the top of JIRA's TODO list. You can achieve this by clicking the "Vote for this issue" link on the top-right corner. Cheers!

PS: I am still interested in this feature as well!!

still interested

Insane how this hasn't been done when it would be amazingly simple to implement.

I am using a kanban board to display epics so that I can manage their decomposition and estimation. To filter the epics I'm having to use manual queries to put the epics into swimlanes by fix-version. In general the whole process is messy. Jira doen't undersatnd heirachy of items and counts both the epic estimate and the decomposed story points.  If you use initiatives as well it triple counts unless you remove the story point from the parent as you create the children. To manage this process I need the kanban board so I can track the epics through creation, estimation, decomposition, implemntation and validation. 

I'd like to use the backlog board but it doen't have any way to see epic status or estimation.

REally??? People have been asking for this since March of 2013 – 6 years? – and you still haven't implemented it? Our team also needs this. If you are going to allow swimlanes, why not allow it on types that people use? Why is using Jira always just one huge hack away?! 

We need this for Cloud. I get that it's messy because there's the possibility of a ticket having multiple versions, but please. You're killing us by not making this available. Manually creating swimlanes by query for each fix version is fine if you only have one project; not so great if you have several dozen.

Please

Yes please!

+1

Yes please, to split by versions would be a great feature.

need it as well! 

we could truck the roadmap and development of the project on the board

Upvoting as well. Now that I made versions, swim lanes based on priority mix multiple versions...

voting, need it

I think version is just one of many more ways that one would want to divide up the board into swim lanes.  Why not have them based on the unique values in any issue field?  E.g. maybe I want to divide it up by label (which might be important for particular applications), or by issue type (so I see my defects separate from my stories), or component?  It seems limiting to consider adding version lanes and then the community will turn around and make a separate request for other useful divisions.  You might have to limit the total number of lanes to something (15? 20? 50?) and put the rest in an 'other' lane (in case where someone picks a weird field like comments).  Another consideration is whether you want to see duplicates or not (e.g. if an issue has two components, would you want it shown in both lanes?  Possibly.)  The Structure plugin already has this sort of capability in their 'group by' filter – it's just that the UI is different.

Besides "versions", a lot of users asking also for components. As of today they are using swimlanes based on queries, but it becomes tricky on very dynamic projects.. Would be easier, if users could just select it..

Would be useful for us too!

"Gathering Interest" for 6 years?...  This is incredibly useful functionality for anyone with sprints that span different fix versions (i.e. nearly everyone).  

Would be a great feature. Or even better a way to freely define autmatically extending swimlanes

Is there an update on this ticket?  We would love this function as well.

We would love such function.

I see that this issue has been open for over 6 years and there is a lot of questions and requests for it. Are there any plans to resolve this issue? This would be a big help for my team. Both in Scrum board and Kanban board.

We would love a function like this in order to track our release management a lot better...

This would be a very useful feature for our team

One has to wonder at the logic employed within Atlassian when instead of having "swimlane by X" they are implementing individual requests for "swimlane by epic" or "swimlane by project" - any developer worth their salt would've suggested a more flexible solution.

Talk about making a sow's ear out of a silk purse.

Is there a ticket for this for JIRA cloud?  

This has been an issue since 2012? Why not do it Atlassian? Its just a foreach loop

+1 Swimlanes by Epic are good, by fixVersions would be even better.

+1

We also have users who need to quickly see issues by fixVersion on a board.

+1 Definitely

For us we're managing 20+ Epics in a release and we want to do release planning by moving Epics between versions.  Thus the Epic swimlane isn't really a workaround and custom queries for each version isn't maintainable.

+1

+1 We would use it to quickly sort/see issues on a per Release basis.

+1 to this feature which I am surprised has not been implemented!

My use case is that I have created a Kanban with a very high level view of my projects and would like to have a swimlane per team/project release to track the progress of each,

+1

Would be very helpful to have dynamic swimlanes based on fixVersion

+1 
I did find the 'FixVersion in unreleasedVersions()' option, but it doesn't split the swimlanes out by version. It just displays everything in one, big chunk (by the query name). It's not maintainable/extensible to create a query for every version and doesn't make sense to use epic link for this purpose when there is a version setting to serve that purpose.

Any update on this. Would be great to have swimlanes automatically by all unreleased versions in a project.

+1 Very chore to add versions every time