RELATED IDEAS
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release.
Now that this date is set manually, it should be possible to map these 2-way so they can be imported and/or updated from the development system.
| Release time frame | 1 month |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +4
5
MERGED
1
MERGED
Include Release "End Date" for integration field mapping
Who would benefit? Any user that needs to integrate Aha! with a 3rd party development tool What impact would it make? Allow better mapping of date data How should it work? In Aha! a release has a distinct start date, end date, and release date. Pr...
1
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
This seems like a simple change and has been languishing for 4 years. If I can change the date manually why not allow me to set it using Jira like so many other important fields between the two systems??
This feature would be a massive quality-of-life improvement to the way we use Aha! and Jira together. Please give this idea some serious consideration. It would be a tremendous help to us.
I'd also like to see release end date to be mappable to Dev Ops. Since we work in scrum, our release date range is our 2 week sprint. Having the internal/external release date mappable to Dev Ops doesn't make sense, since that is when the features would be shipped. Not when the sprint ends.