I was really excited to see this update: https://blog.aha.io/epics-and-features-planning/
However, I turned on the feature to show master features and immediately turned it off, and went back to my old way of just showing the epic name on the story cards.
It adds too much vertical height which is already limited in Aha (the top of the story and epic views take up too much valuable screen real estate) and the cards feel disconnected from each other. Stories that happen to be next to each other that are in the same epic should have one epic name listed and be grouped together. JIRA does something similar if you include subtasks next to each other on a sprint or Kanban board. The subtasks are enclosed in the same gray box that encloses the consecutive subtasks in the same user story.
Also I don't necessarily want all stories in the same epic to automatically be next to each other in a release column. I might have my reasons for not having stories from the same epic grouped together. For example, sometimes I place stories at the top of the release as an FYI to myself there is an action item on it, or I put all of my "will not implement" stories at the bottom of the release so they don't distract me from the ones that need work.
|Release time frame|