RELATED IDEAS
Map a sub-release to more than 1 master release?
This feature doesn't appear to be supported, but I want to ask anyways. I am looking to map a sub-release to more than (1) master release. The master release roadmap view is highly valuable to me for communicating "market" releases across all product lines. However, many times for us different product releases use the same version of an underlying component (sub-release) due to the commonality of our piece parts. I don't seem to be able to map a single sub-release item to multiple product master releases.
This is something that came up for us as something that would be important for our organization. We have "concepts" that can span multiple releases but we don't have a good way to show that.
This seems even more relevant with the release of alternative terminology, since wider use cases for Aha! are being recognised.
A Project Release containing a combination of a project specific Feature X and Feature A from another Project, where Feature A is already in a Release.
We still have APP-I-280 on file. We hid it from the portal since it contained a screenshot of data from your account.
This is very much of interest to us, as similarly we'd like to assign a Release to more than one Master Release, since Master Releases are a great way of pulling together meaningful viewpoints that span product lines.
I had originally raised this in Aug 14 (APP-I-280) - but this Idea doesn't appear to exist anymore (?).