RELATED IDEAS
Feature linked to multiple epics
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams.
Currently we have multiple teams enabling a feature and we can't show the epics that this single feature supports.
© 2024 Aha! Labs Inc.•All rights reserved
Got a time, thanks!
Steven
Yes, that would be amazing. Thank you for the offer to help!!
Steven
Hi Austin, checking back if you received this email? On the support team if Austin didn���t get the email, can you forward to him?
Steven
Hi Austin, yes our use case is simple for Nike (probably every other company is a little more sane and logical!). The multiple epics it belongs to would allow us to manage the work in 2 ways listed below.
1. Primary team ownership of functional roadmap ��� Commercial Analytics
* This team owns a roadmap for their work and ensuring their leadership is aware of the value being added for their ���piece of the pie��� and looks across all of the Analytics team work
2. Business team ownership of business roadmap ��� Business Product Management
* This team owns the roadmap for all the work no matter what functional team is delivering the work ��� we own the ���whole pie��� and look across the functional teams delivering various features (engineering, analytics, UI, database, etc.) to ensure the epic is tracking for all teams
Without the ability to link the feature of the functional team to the epic of the business team we have to keep the manually in sync or duplicate them, creating a headache of pain for quality of data.
All the other features of releases & epics work great, it���s just at the feature level we deviate from the rest of the functionality and not being able to link the feature to multiple epics it enables, limits our ability to effectively use Aha.
Hopefully this helps explain it?
Steven
Hi there, thank you for your idea. I would love to understand more about this use case. Is there an example you could share?
It is quite common among other customers for features to support other epics as dependencies, but we have not encountered a use case where a feature is actually a child to multiple epics. Our recommendation is to use record links to show the relationship between features and other epics that are not the parent epic to the feature.
I am going to mark this unlikely to implement based on the recommendation above. But again, it would be great to understand more. Thanks!