RELATED IDEAS
Move epic/feature to default release when integrations unlink the release
What is the challenge? |
When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! relationship, roadmaps and reports do not reflect the correct plan |
What is the impact? |
Jira and Rally users can have plans out of sync |
Describe your idea |
When an integration includes releases in the mappings, an epic or feature in the dev tool is removed from a linked release and the release link is blank, move the epic or feature to the workspace default release setting to reflect the change made from the dev tool |
-
ADMIN RESPONSENov 7, 2024
We have introduced a new setting that allows you to configure what happens to features when their release is cleared in Jira or Rally.
When a record is removed from an integrated release in the development system, it remains in its previously linked release automatically. This setting allows you to move these records to your workspace's default release instead.
A workspace's default release can be configured on the Settings > Workspace > Configure page.
-
-
-
-
- +1
© 2024 Aha! Labs Inc.•All rights reserved
As discussed a couple of times, this is really important to us as a business.
The workaround of creating a specific 'Parking Lot' Release for Unscheduled items in Rally, would require a big change to the way in which our business handles unscheduled items - and would also impact Rally reporting, RTEs, Engineers, etc.