RELATED IDEAS
Allow "don't export releases" on Rally integrations
I need to use Aha to do customer facing release planning. I also need to use Rally and its project parent-child rollup capability to show my dev team's productivity and hit MBOs.
We have a hack solution whereby we export features (and corresponding release) from Aha to Rally; then create a Rally release with its corresponding child releases; then move the features into the Rally-originated releases so we can do the rollup. We then delete the Aha-originated release from Rally. We also delete the record link from Aha.
It would be far less of a pain simply to eschew exporting the release in the first place.
© 2024 Aha! Labs Inc.•All rights reserved
Which product is this for? Do we really need to think in terms of customer facing release planning anymore? For many products that concept is no longer relevant since we're shifting to a continuous delivery model.
Do you have an estimated due date to implement?
I agree that it would be beneficial to not send over the release when sending features from Aha to Rally. I have 2 products under a product line in Aha that correlate to a single Rally project. When I have a release for each product under a master release, it creates a release for each product in Rally. Then I have to go back to delete one of the releases in Rally and reassign all features to the other release.
Original poster here. Actually - come to think of it - This is NOT what I need most of all. What I need most of all is
- When I am setting up my integration with Rally...
- Give me the option of checking the box that creates matching releases in all my child projects (see picture)...
- So that I can create a release that originates in Aha and that release will behave (within Rally) exactly as if I had created it in Rally.