Thanks for the additional details and for diving deeper with our customer success team.
I've updated this idea to Future consideration as we monitor for community feedback and determine priority.
I appreciate you taking the time to share more details!
Julie, thanks for getting back to me and I did hear from Customer Success as well. Very much appreciate the attention you guys are giving me.
However I'd like to respectfully question that this "already exists." I don't see how in your current structure, Aha allows for releases to contain features from multiple products. Master Releases can contain sub releases that contain features from products the releases are in. But that's not the same. Very common in Agile development, or any web development project for that matter, you will release across various "projects," which is the container that many tools such as Jira, Pivotal Tracker, etc. use equating to your guys' "products." If I want to include in a release features from multiple products, I have to use a Master Release, and include sub releases. I don't think this is the same as just putting together a few features from various products, that my particular team would like to build and release together without the overhead of a Master Release.
Your colleague from Customer Success has suggested custom fields. I notice you guys also suggest using Custom Fields for Sprint mapping to Jira, described here:
This is another example where I think a simple container, perhaps the Release "rebranded" as a Sprint, would be better suited. Custom Fields seem like a workaround to me, and sorry to say that without the ability to simply "grab" features from multiple products and build a release, or sprint for that matter, I miss a huge part of my team's workflow that other tools can accommodate, so I'm not sure if I can fully onboard into Aha.
Again thanks for your attention, and I do hope you guys give some thought to allowing more easily multiple features to be worked on in some kind of container like releases, projects, Epics, whatever you'd call them...
Thanks for the idea!
Someone from our customer success team will reach out shortly to discuss your use case in more depth and see how we can best support it.
I am struggling with the ability to create a body of work in Aha that contains several features, but across a few products. Master releases require sub releases, and I have needs at times to add a feature or two in some mid-tier back end services in my Platform. I run a model that is very similar to this:
If I have just one feature in my platform that needs to be developed to then implement into the front end products, it seems superfluous to do a whole release for that, which I need to include work from another product, just so I can plan the work cross-product in a Master Release.
I assume you guys have thought this one through and do not allow individual features in Master Releases for good reasons, but either way this limitation is probably going to prevent me from going forward with Aha. In a word, without this capability, I don't think I can do a proper "epic" or simply "project" across my company's product lines.
Thanks for listening guys!