RELATED IDEAS
Jira sprint dates as feature end dates
With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would allow Aha to reflect the actual delivery dates of items as they are moved between sprints.
Without this capability we're either inheriting dates from the release which tends to be very wide dates, or manually having to merge information between systems.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2024 Aha! Labs Inc.•All rights reserved
I didn't realize that this idea already existed, but here's what I wrote in the other idea I created by mistake :
What is the challenge?
The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality
What is the impact?
We end up forgetting to update the feature release date in Aha! on which our integration and sales team rely when communicating with clients
Describe your idea
Syncing the individual feature date range with the Jira Sprint Start and End date would allow us to automatically calculate the related release's date range, eliminating the potential date discrepancies.
During sprint planning/grooming our team is in Jira assigning stories, often from multiple epics, across multiple sprints (future sprints are not locked in yet, we're just trying to estimate release dates). Ideally the sprint dates and story points from Jira would be reflected back in Aha Gantt charts and highlight any capacity issues (ex: our team's capacity is 50 story points, but Sprint 8 has 75 story points assigned to it).
This is a much needed feature to automate roadmaps in real time, and reduce tedious work of keeping AHA and Jira in sync. How is this not available today as part of the Jira integration?
A better notion of / managed of Jira sprints in Aha is currently the real weakness to me of aha. Releases are build through sprints and sprints have a fixed interval. Having a sprint view / planning in Aha is a view/planning that I'm really missing. So I'm definitely agreeing with the comment of Andrew below!
This would be incredibly useful. Product Managers are currently changing the dates on stories manually in Aha. But mapping the sprint start date and end date with the feature/requirements start date/End date would reduce that manual step . The integration is excellent and this would increase the value.