Currently, if you need to use a custom roadmap and the "show text inside thick line" option, text doesn't wrap. So if you need to display a good amount of text - a feature or master name, tags or labels, short summaries etc - you just get this extremely ugly UI where all of that just extends off into the white space next to the thick line.
Conversely, if you also need to show tags in this stream of information and try using the "Thin lines with text above" option - the design of the tags makes it so they hit the thin line, instead of being clear above like the text. Really bad UI, especially if you have a lot of items to show.
PLEASE ADD THE OPTION TO MAKE THE TEXT WRAP AND THE THICK LINES VARIABLE SIZES BASED ON TEXT WRAPPING!
Currently this is the only way to make a type of starter roadmap that shows masters features vs releases vs initiatives and goals, and to not force use of a pivot table when you really need some type of gantt timeline view (Speaking of, master features can't be part of the release gantt view?)
Saving overhauling my global teams' JIRA use, there is no way to make a visually appealing roadmap with master features and other information.
Selling point for me and Aha was to not have to duplicate work and have a roadmap i can update as product priorities change, but I can't share this with stakeholders internally or externally. Simply not enough information can be shown
This would be very important for our organisation who are consistently duplicating roadmaps on PowerPoint, making the use of Aha! pointless as it's not being kept up to date in favour of PowerPoints. A visually appealing alternative is essential that doesn't look clunky when it's exported to PowerPoint.
It would be nice to have this prioritized sooner, given that AHA's fundamental feature is roadmap planning.
I have the same issue, in this way the custom roadmap is not useable or shareable
Like Rachel, I have run into this issue on the starter roadmap. This in turn makes the roadmap looks pretty unprofessional when sharing with stakeholders.
I've attached a sample.
I have a similar need on the starter roadmap
I have a field attached to the release called "hypothesis". This is important for an executive roadmap reader to understand was they are getting out of a release.