Story map should have a setting allowing to block automatic adding of rows
Story map should have a setting allowing to block automatic adding of rows especially when features are moved vertically for reorder . Today for larger maps the map grows vertically in uncontrolled way making it difficult to manage
Why a Release created from "User Story Map" directly going into Mainline on the "Feature -> Board" page.
When a user creates a "Release" from "User Story Map", the created "Release" will go at the left side (mainline) on "Feature -> Board" page (not in Parking Lot). While creating a Release user should have an option to select where he/she wants t...
Currently adding existing features is not very convenient as they just get thrown somewhere into the map It would be great to see whether a feature has already been added to another map (sometimes I would like to know whether I can delete a featur...
Allow items to be moved from one story map to another
It does not appear to be possible to move/copy Epics and Features from one Story Map to another. This is as essential as the ability to pick a post-it from one white board and stick it on another: at allows re-partitioning of the problem and exper...
Allow to lock items when date is synched with integration
Currently when Epics, Features and Requirements use a Date Sync with our DevOps it would make sense to be able to lock the dates in UI and Bar-Lenght handles as they are exclusively coming from the external system. This would avoid: A contributor ...
about 3 years ago
in User story map
Pretty straightforward, would be great to be able to # mention user story maps in Aha! records. Today I was working within a strategic model and wanted to reference a brand new workflow opportunity for a product. Instead of mentioning individual r...
over 3 years ago
in User story map