RELATED IDEAS
User story map card configuration
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 different fields which are visible from the data model (for example integration ID, assigned user) so once you'd created the map you could then track the status as you would from the features board.
Also would be nice to be able to switch between a small and expanded view as you can on the features setup. For items with large numbers of items then being able to reduce the un-used space and see more items would be helpful
1
MERGED
Customize card layout for User Story Mapping
I'd like the ability to customize card layout for the user story map. This will allow me to see things like tags, assignment, themes, etc. It'll help better distinguish cards better and identify dependencies and connections better.
0
Future consideration
2
MERGED
1
MERGED
Story Map - Customize card layout
We are using the story map for building a new system. From those cards, we are building features with requirements. We'd like to be able to customize the story map card to add the status and # of related requirements - similar to what we can do on...
0
Future consideration
1
MERGED
Feature cards info on user story map
Hi, Would it be possible to add function of displaying other information of Features cards on user story board? It is already available on feature board. I think it would be really useful to have that on user story map as well. Thanks, Patrick
0
Future consideration
8
MERGED
In the User Story Map view, display attached tags with the cards representing epics/features
We use tags to indicate general categories of concern, often mapping to particular teams. When a team leader looks at a user story map, seeing tags would allow them to quickly parse which sections are relevant to them and dig into the details with...
0
Future consideration
8
MERGED
In User Story Map view, include tags attached to Epic and Feature cards
We use tags to indicate general categories of concern, often mapping to particular teams. When a team leader looks at a user story map, seeing tags would allow them to quickly parse which sections are relevant to them and dig into the details with...
0
Future consideration
8
MERGED
I love the story maps! I would love them more if I could customise the cards
This function is extremely useful for working with teams and facilitating story mapping sessions, particularly if they are distributed geographically.
In order to enrich the information recorded in the card and make it immediately visible in the S...
0
Future consideration
1
MERGED
Customize cards in User Story Map view
I would love to customize the fields on the cards in the Story Map view. Specifically, I want a really easy way to see the estimates...since that's the next step once the story map has been completed. And, when we do that over multiple sessions, t...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
It would be also good to be able to add filters to the User Story Maps. That way only the cards needed could be displayed, based on the field value selected (e.g., Status, Assignee, tags, etc).
There should be a way to display the score, rank, etc. for each feature/epic, while in story view. Why? I've already done my scoring on an atomic level for features. If could see a score, I’d know better which features are worthy of including in a story map, that I take to an executive for approval.
We've started using the user story and colleagues like it. We want to view personas associated with steps, epics, features, etc. on the view. Also share the other suggestions made here.
I was just about to post a similar idea. I was looking at the feature board side by side with story map and noticed the status, for example, displays on the feature card on the feature board, but not the story map. Can't figure why the feature cards would need to be different between the two views. The feature is the entity and it's status and such should be the same no matter how you slice it, yes?