Skip to Main Content
138 VOTE
Status Future consideration
Categories Features
Created by Thor Taylor
Created on Aug 12, 2016

Custom swimlanes for features and workflow boards

Currently swimlanes are by owner which is helpful when micro-managing resources however we group resources into teams and focus features on given teams. It would be nice to support custom fields/groupings on the swimlanes so I could choose how i want to see the content grouped when making decisions.

  • Attach files
  • Tim K
    Reply
    |
    Jul 18, 2023

    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.

  • Jason Domask
    Reply
    |
    Aug 23, 2022

    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.

  • Steve Treagust
    Reply
    |
    Feb 3, 2022

    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!!

  • Alia Connor
    Reply
    |
    Mar 31, 2021

    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.

  • David
    Reply
    |
    Jan 26, 2021

    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

  • Guest
    Reply
    |
    Jul 8, 2020

    This would be great for some of our big customers

  • Daniel Pokrývka
    Reply
    |
    Feb 27, 2020

    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 

  • Guest
    Reply
    |
    Jul 2, 2019

    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.

  • matt lenning
    Reply
    |
    Jun 26, 2019

    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.

  • Marina Reyna
    Reply
    |
    Jun 11, 2019

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

  • Katie Tokarz
    Reply
    |
    Jun 7, 2019

    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.

  • Michael Toose
    Reply
    |
    May 22, 2019

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

  • Guest
    Reply
    |
    May 9, 2019

    I second the motion

  • Lowell H
    Reply
    |
    Apr 1, 2019

    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.

  • David Vins
    Reply
    |
    Nov 8, 2018

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

  • Guest
    Reply
    |
    Nov 7, 2018

    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.

  • Guest
    Reply
    |
    Oct 8, 2018

    Bumping for attention!

  • Guest
    Reply
    |
    Jun 22, 2018

    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! 

  • Guest
    Reply
    |
    Jun 21, 2018

    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. 

  • Guest
    Reply
    |
    May 18, 2018

    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).

  • Load older comments
  • +40
1 MERGED

Add release grouping to the workflow kanban

Merged
When using the workflow view of the Features and Epics board (Kanban) there is a default option to group the cards by 'Assigned to'. If we could select other options for this such as release it would add huge value to this view
Steve Treagust about 2 years ago in Workflow boards 0 Future consideration
1 MERGED

Workflow: Swimlane per Team

Merged
Features -> WorkflowView: Feature Allow to show swimlanes per Team
Guest almost 3 years ago in Features 0 Future consideration
1 MERGED

Workflow board should group by custom fields

Merged
On the workflow board, there's only group by assignee. I want to be able to group by: a Feature custom field that is the "predefined choice list" type Epic This would really help for visualizing swimlanes and planning work over a long period.
Michael Gillis over 2 years ago in Features 0 Future consideration
1 MERGED

Workflow: Allow Swimlanes per Releases

Merged
Features -> WorkflowView: Epic: Aloow to shoe swimlanes per Release
Guest almost 3 years ago in Features 0 Future consideration
1 MERGED

Allow to assign tasks/features/epics to Virtual Users or to a Team

Merged
We are using the Workflow View and use swimlanes by assignee. Having swimlanes on a person level is too granular for us, so we created dummy users to represent a team. Dummy users are not allowed in our company. I tried alternatives like assign e....
Guest over 2 years ago in Workflow boards 0 Future consideration
12 MERGED

Group by Product on Epic Workflow Board

Merged
Removing the group by Assignee was a great feature add. However, now I would like to group by potentially a few different fields. Product Custom Attribute (we assign teams to our epics so this would be used to see what each team is working on ac...
Kenny Burnham over 4 years ago in Features 2 Future consideration
55 MERGED

Kanban Board: View/Pivot by different categories

Merged
The new kanban board is great, but I would love to be able to pivot it by different categories other than the "assignee" and have the order of the cards be faithfully reflected within each of the categories. I can see the use for pivoting by a who...
Guest almost 9 years ago in Features 3 Future consideration
11 MERGED

Workflow board based on tags rather than assignees

Merged
Is there any way to replace a user name with a tag in a workflow board? We are trying to create a workflow board using team names rather than named individuals. We have created a pivot report for this as a workaround but we like the look and feel ...
Cindy Datlof almost 4 years ago in Roadmaps 0 Future consideration
1 MERGED

Add Additional Group By Options

Merged
When organizing a features board based on feature or user story, users should be able to group by more than just by Assignee. For example, when organizing a board view, I'd like to see user stories grouped by feature. Currently, you get separate c...
Guest about 2 years ago in Features 0 Future consideration
12 MERGED

Configure group by options on Feature/Epic Workflow Board

Merged
The drop down for selecting how to group by only has two options: none or assignee. The fact that it's a drop down vs a toggle box tells me more options are coming or that the options are configurable. But after poking around it looks like that's ...
Guest about 4 years ago in Features 0 Future consideration
1 MERGED

Group Feature by custom fields on feature workflow page

Merged
Aha! has almost zero Kanban functionality, adding a way to group feautures on the workflow by anything else than just assigned person such as some custom fields would enable classes of service to be added simply and quickly and make that board muc...
Mike Lowery over 1 year ago in  2 Future consideration
14 MERGED

Under Activities >> Workflow option for swimlanes by Project

Merged
The Workflow board would be even better if we can add swimlanes by project. Much better user experience.
Guest over 4 years ago in  1 Future consideration
2 MERGED

Group features workflow board by workspace

Merged
There's only an option to group features currently by assignee, having more options available such as workspace to get a master view would be very helpful
Parmeet G over 1 year ago in Workflow boards 0 Future consideration