Custom swimlanes for features and workflow boards

My vote is for swim lane customization and defaults! Even if you do not ship new customizations or ability to change defaults - the OOTB default behavior of grouping by user in an organization with thousands triggers a prompt saying "truncated to 50 users" which is less than ideal. Please at least consider defaulting to ungrouped.

We’re preparing to introduce Program and Solution Kanban boards based on the Aha! Initiative and Master Feature Workflow Boards. It seems that Aha! intended to allow custom swimlanes to be added to workflow boards based on the November 2021 Aha! broadcast, however this feature does not work – unless using Aha! Develop. We are currently an Atlassian shop and have no plans on replacing JIRA with Aha! Develop in the foreseeable future.

Our request is that we have the capability to group Master Feature Workflow Boards by Initiatives, which will effectively allow us to implement Program and Solution Kanbans.

Not having this capability might be the "straw that broke the camel's back" - meaning the final issue we are willing to tolerate prior to switching to JIRA Align, Planisware, or some other solution to manage strategy.

I have just added an idea which radiates this requirement A-I-12101, however it is disappointing to see an idea with 106 votes still being in 'Future Consideration' after 5 years!!

Our team would love to see swimlane by Initiative. This would make it easy to go Initiative-by-Initiative and update status on related Epics.

There are use cases for needing to be able to choose any number of fields for the Group By option that governs swimlanes in a workflow board. The most important ones are

• Assignee-based--like is currently available by individual but instead by Scrum Team

• Schedule-based--e.g., sprint, release

This would be great for some of our big customers

My two cents: 

Example use of custom swimlanes

- showing stories with epic swimlanes (story=requirement, epic=feature)

- showing epics with release swimlanes (epic=feature)

- showing initiatives with goal swimlanes 

Even the ability to turn off the swimlanes would be beneficial, it's quite messy as it is.

I really like the Initiative workflow view -- simple and clean, and if you want more detail you click and dig in.

This would be an amazing feature to have, and would make our teams work so much more efficient and increase adoption of the Aha! tool.

We're running programs, and have large teams so being able to have a Kanban style board, without defined swim lanes, or being able to custom define them, would make a monumental difference to our work. We're running scrum at scale in a very large company. Dozens of teams, and each team has dozens of individuals who contribute.

It's honestly frustrating that the tool doesn't have a function to do this already, and focuses so much on the micro-managing detail. Pivot tables to try to view this information are incredibly difficult to work with, and we almost have to revert to using another application just to update/plan our sprints because this doesn't have it.

Could we also include enhancements mentioned in https://big.ideas.aha.io/ideas/AFPR-I-7769

Agree with all the comments here.  Our company is using the SAFe framework, which relies heavily on the use of Kanban boards, but the swimlane by user makes the board limited in value.  The ability to customize swimlanes, or not have to use swimlanes at all on the workflow board within features, would be very beneficial.

I am with the below suggestions re swimlanes 'by release'. I don't find 'by user' that useful. 

I second the motion

Absolute "must have" for anyone working at scale. (SAFe for example.) We don't work at the user level but at the team and program level.  Rows could be product, product line, or even priority.  Limiting to users just doesn't work for us. Redirecting folks to a pivot table is not a valid option: incredibly hard to use/read, can't drag and drop, etc.

Yes! Swimlanes should be configurable based any any field; with a default.

Hello All -

This will help us manage however, we deem fit. 

Is it possible to look at the potential to customize the "Y" axis of the workflow? We use SAFe and have the value Class of Service which is a custom field. We would like have the ability to set the swimlane to this custom value rather than the person.

Currently, we are using a Pivot and having to either click three or four times to move the story along or click into multiple reports when having a standup.

This is increasing the amount of time that we spend on a standup as the pivot does not allow you to drag and drop across the Kanban board.

Can we move this prioritization of this request up so that we can be more efficient and save time from updating a tool and doing more communication and development.

Bumping for attention!

This would be great. The same automations that happen between requirements and features would be helpful to have between features and master features to cut down on manually having to manage/update. Any program manager / product manager who is trying to stay at the 'master feature' or 'epic' level will find this beneficial. After all, the ability to create visibility at this level while connecting different development tools is why I was drawn to Aha! 

The ability to customize swimlanes in the workflow view is critical for agile/SAFe product managers who are using Program Kanban boards to capture stakeholder requests, prioritize and visualize WIP before pushing features to team backlogs. 

if we are talking about the "workflow" board for features, then I would like this too!  I was just looking for a way to define swimlanes by something other than assignee (e.g. Product).