+1

It's 2024... how much worse can Jira be?  

+1 

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Grouping based on custom fields for swimlanes is much needed. Adding and updating (if needed) individual entries is a overhead and waste. May be you can think of those categorical custom features or columns where classification is less or you can also restrict it to a certain number. 

Another 10 yrs to go...

Yet another feature for which Atlassian teams have been gathering interest for almost 10 years 🙃

This is definitely needed on Kanban boards! It is strange that the "Base swimlanes on Queries" feature doesn't do this as a simple option. Constantly adding new entries is tedious.

As a side note for any watchers, the Gantt-Chart for Jira plugin does pretty much exactly what we want here: automatic grouping based on field value... but unfortunately not in board form (no Agile columns), so I suppose it's a bit off-topic for this issue. That said, I find the automatic group-by on field values extremely useful, even if you don't care about the Gantt chart aspect (which you could actually just ignore, the treeview grouping part itself is awesome). As an added bonus, the hierarchical grouping has unlimited (I think?) levels. What do I mean by this? No more Jira-imposed 3-tier maximum (swimlane/epic → task → subtask)!!
 

+1

Automated swim lanes based on a single (Custom) Field value is definitely a nice feature to have 

Seems important in the CI/CD world where one might be releasing to production more than once per week. We maintain a suite of 15 interrelated services all on the same board. We are beginning to do smaller releases when individual services are ready. This has lead to 2-5 release versions being tracked in a single 2 week sprint.

Would be extremely helpful to parametrize the kanban board so that we could easily watch the board for a given release without changing the JQL for the swimlines

As a user, having this feature could enable our team to group our issues based on upcoming milestones, without regularly editing our filters manually.

I can't see why this isn't already a feature!

It would really make thing easier for me if I could tickets on a board grouped by `due date`, at the moment there is no way to do that as I see

I need to do what Matthew Walker described above, but instead of Components, I want to do this with fixVersion. Therefore, I will have new fixVersion being created regularly (1-3 per week) and unless there is some long term solution from Jira, I will have to manually add the swimlane condition for each new fixVersion.

Would be very helpful!

Voting, needing it

The simplest workaround for some of our concerns is to use Queries for defining swim lanes.  In my case, I'd like the ability to base swim lanes on Components, but since that isn't available via a simple dropdown option, as it is for Projects, Epics, Assignees, etc., I decided to base the swim lanes on Query, then created a separate query for each Component, such that [component = "Component 1"],  [component = "Component 2"], [component = "Component 3"] etc. With ten Components this took 5-10 minutes to complete.  This same process can be done for any field, such as Reporter, etc. 

However, since there's unfortunately no way to save multiple Queries for the same board, even if only one can be enabled at a time, I just created a separate board for each Query.  This means that in my case, if I want to show my team a board with swim lanes representing Components, I show them the board that queries Components; if they want to see a board organized by Reporter, I go to the board where the the swim lanes are defined by Reporter.  This means that there are multiple boards for a single project, each defined by different swim lane queries. 

In an ideal world we would have more options available in the swim lane dropdown, but since this isn't the case, using Query and multiple boards seems to be the simplest workaround.  

It would be useful to be able to have the Jira administrator at the company be able to add options to the Swim Lane drop-down as deemed necessary. That way the field would not be cluttered by trying to please everyone as different companies have different needs (we would like to have Reporter as option). I realize we can use queries, but that would require a lot of ongoing updates to queries as people come and go.  While I'm on the topic, I would love to have multi-level Swim lanes (e.g. grouping by project, then by assignee). 

Yep, broken processes or usage of "Epics" is the only at the moment. So sad.

+1. Just the possibility to choose between Epics, Request, Stories, Version, Component, Ctustom Field would be wonderful. Like many others, this impossibility lead my users to misuse Epics.

We'd really like to base our swimlanes on long-running feature branches.  This helps make it clear how the long-running feature is progressing, and helps ensure developers recognize the need for the long-running feature branch before starting work.  Currently, we're forced to do this using epics, but this doesn't align well with the meaning of an epic for product owners and management.

I have written a comment about how to configure Swimlanes for FIX Version field in GHS-5720. You may find your solution there!

swimlanes by component, way to go Ingrid! ditto

This would be tremendously useful to us.

Our Kanban boards have swim lanes either for each version, or for each component. This is very much work to maintain, and where we sometimes forget to add a swim lane for a specific value, the board loses its strength completely.

There's no further update at this time, we see it as a valid Suggestion however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

It is likely that the swimlanes per version or swimlanes per project would be implemented first so please follow those related Suggestions:
https://jira.atlassian.com/browse/GHS-5720
https://jira.atlassian.com/browse/GHS-9719

Kind regards,
Martin
JIRA Agile

Any Update on this issue? It would really be helpful to be able to define swim lanes automatically for every value in a particular field / custom field.

jeff_johnston - swimlanes by version is tracked by GHS-5720

Kind regards,
Martin
JIRA Agile

>> I have a pressing need for a Kanban that self-determines swimlanes based on fixVersion...This is just basic 'group by' functionality; I'm actually thinking I may be missing something not being able to figure out how to make it work with the current JIRA implementation.

We have the exact same request. We would like to be able to have dynamic swimlanes based on fixVersion. This would automatically do the grouping so that we could see the next few fixVersions as separate swimlanes. Right now creating new swimlanes is a manual step that we have to keep updating.

jwaligora - swimlanes by epic for Kanban boards will be available in release soon, this case is tracked at https://jira.atlassian.com/browse/GHS-9144

Kind regards,
Martin
JIRA Agile

Definitely up-vote.

I have a pressing need for a Kanban that self-determines swimlanes based on fixVersion (and also on Epic...which is available for Scrum boards but not Kanbans).

This is just basic 'group by' functionality; I'm actually thinking I may be missing something not being able to figure out how to make it work with the current JIRA implementation.

Please make it flexible enough so that the user can pick any desired field to group on.

Any progress?

This requirement should be prioritized higher!

Complementing quick filters with the ability to quickly turn swimlanes on and off, and allowing board users to choose between different swimlane criteria, including a new option for auto-generating swimlanes based on any field, would be major time saver. It will also provide significantly improved analysis capabilities, reducing the need for setting up quick filters. Kanban boards that can generate swimlanes automatically for Reporter, Assignee, Fix Version, Epic Link, Budget Account (custom field) are among my primary needs.

I would really like to be able to do Swimlanes by Projects (at least).
Thanks!
Tommy.

I'm very surprised this isn't already in JIRA, i stumbled on this ticket while just looking up how to do something I assumed was already present. fixVersion swimlanes would be very helpful.

Hey Atlassian!

This valuable input from users has been hanging around for a long time now (almost 2 years!) with no feedback from you. What do you think?

-David

+1
We need based on linked issues.

Could we include the ability to set the "swimlane mode" dynamically in this same issue? (In other words, use the "Configure Board" screen to set up the desired swimlane filters, and then have a quick menu in the board UI to change which swimlane filter is used – dynamically)

Also, would GHS-9719 be considered another duplicate of this issue?

+1. You already do this for assignee - why not for all fields? It would also be good to be able to do this for columns. Check out Target Process 3 to understand the power in this. It's a big deal.

We agree with what others are saying - having preset swimlane configurations based on other fields, similar to that based on assignee, would be very useful - e.g. component, project, fix version, priority, etc. This could probably be done in a generic way so that custom fields would also be automatically available. It's great to have queries as a fallback, but not so convenient for common use cases.
-David

Added my vote here. It's a pity that you can't have swimlines for fields like component - and manual creation is definitely not an option.