Jun 06 2019 09:57 AM
Jun 06 2019 09:57 AM
another topic asked frequently is the ability to add Swimlanes in Planner. Is this considered?
Jun 06 2019 09:58 AM
Jun 06 2019 10:02 AM
Jun 14 2019 06:29 AM
@Joanna Parkhurst I agree with @Konstantina Antoniadou . Planner is very interesting for our organisation, but the ability to "cut" plans into swimlanes would be a great feature. Just imagine it as a capability to visually organize your plan into "custom rows" to separate tasks (eg : you could for example keep your "to do", "in progress" and "done" columns, but categorize them into "test" and "production" swimlanes.
May 14 2020 08:00 AM
@Yohan30 @Joanna Parkhurst I am interested in the Swimlanes as well. A use case I am trying to put together is to conduct a Scrum Story Mapping session. if you set up the Buckets as features ( Deliverables to a client) and then apply Sprints as Swimlanes, the mapping would move the story card under the features and into the sprints. this mapping process gives a good visual representation of when a feature can be delivered. See the image I added
Aug 20 2020 10:49 PM
I'll add to the conversation that for a small team, you sometimes need to explore different areas of a topic separately. Swimlanes would make organisation of the tasks much easier. I'm not at liberty to go into detail about what we're working with, but an example would be that our team is responsible for the design of a house. A few members will research exteriors, a few members will research interior, a few will research electrical, a few will research ventilation etc. Having those tasks all in the same bucket with no dividers makes it unpractical. The labels aren't enough.
May 28 2021 08:25 AM
swimlanes would be great. ultimately I think planner needs 2 things.
1) swimlanes which is essentially the ability to not only group by on he top axis but to also group by on the left axis, this swimlanes.
2) to make the swimlanes really work well I think planner needs more custom fields besides 'bucket' and 'label'. I think planner would be more powerful with let's say 10-15 customer fields that can be defined as text, dropdown or select etc. if those additional fields were then made available in the group by it would make planner more robust.