Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

version-based swimlanes for a kanban powered story map

Bryan Collick
Contributor
February 20, 2018

I am using a kanban board to track an initiative, its various parts (as epics) and their corresponding user stories. I want stakeholders to see and participate in the prioritization of work that is being grouped by release.

To ensure that only one project's work shows up, the board's filter is:

project = foo and "parent link" is in (initiative, epic 1, epic 2, epic3, epic 4, epic5)

Although I can see (via issue view and via Portfolio) that the stories have been assigned to releases, I cannot seem to generate version-based swimlanes on the story map. I read this document explaining how to sequence issues, but the associated image does not match what I see (see below); moreover I cannot deselect the option "no swimlanes."

Let me know if I'm missing something and/or if this is possible to do. Can you actually create a story map with version swimlanes from a kanban board?

Screen Shot 2018-02-20 at 9.20.43 AM.png

1 answer

1 accepted

0 votes
Answer accepted
Seamus Kieran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2018

Hi Bryan, thanks for reaching out.

There are a number of reasons as to why this may be occurring. I have included a brief summary below, you can read about them in more depth and find the solutions in this knowledge base article.

1. Your agile board spans multiple projects. If the (scrum or kanban) agile board's filter you're using to create your story map contains more than one project, the Versions swimlane option is disabled. This is because we cannot currently support cross-project version changes.

2. The Fix Version field not present on the project screens. When the fixVersion field is not on the screen for the issues it is not accessible by Easy Agile User Story Maps.

3. The Fix Version field is hidden on the field configuration. When the fixVersion field is hidden on the field configuration for the project/s it is not accessible by Easy Agile User Story Maps.

Please let me know if one of these is the cause of your issue. If not, could you please send me an email at support@easyagile.com with a copy of your troubleshooting information so we can investigate further.

Thanks Bryan.

Kind Regards,
Seamus Kieran
Easy Agile Support Team

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events