Better UX and configuration options for user story maps

User story maps only work with certain record types and you can't change how the cards look. This makes it hard for teams who organize their work differently. For example, our team tracks user stories as requirements instead of master features. So the default setup doesn't match how we work. We also can't customize which fields show on the cards. This makes it harder to track our work and work together as a team.

Story maps don't work well for teams with different ways of working. Users can't pick the right record types or change how cards look. This means teams have to change how they work to fit the tool. As a result, fewer people use story maps, teams get confused, and it's harder to plan and see the big picture.

We need more flexibility in user story mapping to make it fully useful for our workflow.

• Record type flexibility

  • Admins should be able to choose which record types appear in the user story map

  • We structure our work so that user stories exist at the requirement level, meaning our maps should show features and requirements

  • We don’t use epics and don’t want Aha! to enforce a specific record type simply because we’re using the story map

  • This would cause confusion for our team

• Card customization and layout options

  • It would also be helpful to configure cards the same way we can on the feature board (e.g., integration ID, assigned user, status)

  • That way, once the map is created, we can use it to track progress just like we do from the features board

  • Additionally, providing small and expanded card views (like on the features board) would improve usability, especially for maps with a large number where reducing unused space would make navigation easier

See merged ideas for additional use cases.