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.
In my feature list, I want to be able to filter my feature list so that I only see features tied to a particular user story map. I need to see a view of all of the features in the story map together so I can assess which fields I still need to complete. Once I can pull up all the features tied to a user story map, I will export the list of features for folks to review that are not Aha! users.
Our teams are having to go outside of Aha! to do simple reporting including User Story Map data points (like Journey Headers) which enforced the lack of need for Aha! & wastes a PM's time. Please add this record into reporting.
Is this still up for consideration? Our business finds the story map valuable, but it is less worth doing when you cannot integrate any of the effort put into story mapping into our reporting.
Hi, yes I'm excited about Story Maps and would like to be able to see more depth to them. In particular, I'd like to see the "steps" as data items within Aha that you can link to like other records. These are in a sense a level of "container" within Aha, and there is a bunch of potential for them if you are setting them up. The contain a set of features for example, that is not otherwise grouped anywhere in Aha. For example, I'd love to see a diagram built out along the lines of the "visualize" present on all features that shows connections to linked records. This could easily become a powerful server config diagram, sitemap in the case of a website as a product, and others, with the huge benefit of actually the diagram getting created "live" via record links, and auto-updating, instead of having the user continually need to update manually, such as is the case with the current draw.io Mockups you guys have right now, if you wanted to use such a diagram to represent products and features.
Thanks for listening!