Allow User Story Maps to Span more than one product
User Story maps should be able to show Master Features and Features from multiple products. We have complex products that have to work together in order to deliver usable solutions. Any step that the user does (install, configure, receive certain ...
Julia Doyle
over 5 years ago
in User story map
11
Future consideration
Admins should have the ability to chose which records are in the User Story Mapping. We structure Aha! so that User Stories are at the Requirement Level so it makes sense for us to view as Features/Requirements
We don't use Master Features &...
Guest
over 5 years ago
in User story map
14
Future consideration
The new User Story Map functionality is really good and we've started using it for some cases. What would be really useful is to be able to configure the cards in the say way we can on the feature boards. This would allow a user to select the diff...
John Biltcliffe
over 5 years ago
in User story map
4
Future consideration
as a user, I want to be able to include the story map (Name, Description and Step, step sequence) to any report and report type, so that I can group my reporting by the story map information.
Steve Podzamsky
over 5 years ago
in User story map
5
Future consideration
To be able to easily move the features upwards in the User Story Map
When I work with the User Story Map (great tool by the way), I sometimes make mistakes. When that happens all my features ger scattered out in map height wise. Then it is a REALLY tedious work to collect them at the top level.
There should be a w...
Guest
over 5 years ago
in User story map
2
Future consideration
I use the story map as my main form of planning for sprints. It would be great if the story map view had some of the features other screens have, such as: Web view (for sharing) Progress visible Customisable cards
Guest
over 4 years ago
in User story map
4
Future consideration
New User Story Map entered Epics should still require required fields and load the standard description field template
Problem: When adding entities (e.g., Epics) via the User Story Map, the user is not prompted to enter in required fields and the predefined Epic template is not loaded in the description field. This bypasses the Epic creation protocols elsewhere i...
Peter Bongiorno
about 3 years ago
in User story map
0
Future consideration
Promoting Story Maps to a first class object would enable users to: list story maps list and select stories in a story map for bulk operations list and select epics in a story map for bulk operations Sometimes I want to tag all the stories associa...
Guest
over 4 years ago
in User story map
0
Future consideration