RELATED IDEAS
Show more info of a Master Feature when connecting a Feature to a Master Feature
We have Master Features with the same names in multiple releases, so when we are connecting a Master Feature to a Feature, there are duplicates in the list of Master Feature but we cannot tell which Master Feature is with which release to connect it to the correct one.
Example:
1. Create the following Master Features for Version 3.0, Version 3.1, and Version 3.2
Product Name
- XXX
- YYY
- ZZZ
2. Go into a feature within Version 3.1 and link a Master Feature, the list of Master Feature shows:
Product Name
- XXX
- YYY
- ZZZ
- XXX
- YYY
- ZZZ
- XXX
- YYY
- ZZZ
-
ADMIN RESPONSESep 20, 2024
Thank you for the idea. Given the low volume of support for this idea, we do not have plans to make updates in this area at this time. It is currently possible to view the reference ID when linking records together to distinguish between epics with duplicate names, or you can link features across multiple releases into the same epic. We hope that helps!
© 2024 Aha! Labs Inc.•All rights reserved
Faced same kind of issue on other tools as well. If you have recurring mater features, like "UI Enhancements" or "Integration Improvements" you can do one of 2 things:
I did the second option for a while, but moving into the first one since a couple releases back.
Very helpful! Thanks! I have tested it out and understand what you have explained. I hope you will still move forward in implementing the idea of showing more information when linking a Feature to what Master Feature. Thanks for the help!
That is helpful, thank you Dale. Master features can span multiple releases. In your example, you could create a single Integrations master feature and place it in the 3.2 release which is where you would anticipate it will have been fully developed. You will deliver it incrementally over the three releases, so the features in those individual releases can all be linked to the same master feature. If you display it on your Features roadmap, the icon for the Integrations master feature will show up across all three releases. I hope this helps. Thanks!
I may not be utilizing Master Features correctly, but here is my understanding. The company creates a release cycle, and I manage my product versions (3.0, 3.1, 3.2, etc.) and decide which version will be committed to which company release. I will create the required features (let's say 25 for version 3.0) for a release, then select on Master Feature and create Master Features (let's say 7 for version 3.0) for those to be associated to. Then I will do the same for version 3.1 and 3.2, etc. Let's say that in ver 3.0 I have a Master Feature called Integrations and I have 3 Feature integrations linked to it. in ver 3.1 I will have a Master Feature called Integrations and have 4 Feature integrations linked to it. In ver 3.2 I will have a Master Feature called Integrations and have 2 Feature integrations linked to it.
Does this help? Is there a way to span Master Features over multiple releases?
Hi Dale, thank you for the idea. Can you give us more insight here? Why is it that you are creating duplicate master features for each release? Thanks!