Right now the aha release phases just seem like an informational overlay with no connection to the features themselves or their JIRA equivalents. So when work gets estimated in jira or progresses these timelines don't change. I have to keep them in sync manually.
If I could associate a aha release phase with a sprint and have the duration and time frames stay in sync that'd be a great start
As to when I need it ... without it, I'm just going to use milestones only and that's not nearly as useful
Releases contain release phases and milestones to help you manage customer launches -- when specifically looking at release phases, they typically contain both technical and non-technical work.
Features can also be placed into release phases, to help with better understand the different aspects of the launch.
We would suggest adding a custom field at the feature level to track sprints. It would require manually updating the field, but would allow for reporting by sprint. At this time, we do not have plans to make updates in this specific area due to community feedback and current priorities. We hope you can understand.
Aha should absolutely support synching for Release Phases and Sprints. They are exactly analagous - just containers of tickets with a date range. Will try the workaround, thanks.
I had wanted something like this for a long time. However the workaround I am using now is pretty robust.
I use a filter in Jira to find all issue-types that are assigned to the current sprint that do not have a label matching the current sprint name (in my case it's "Sprint-###") and then I use bulk edit to apply a label with the current sprint name.
In aha I've synced (two-way) the Aha Tag field with the JIRA Label field. This makes is very easy to filter any report in Aha by corresponding Sprint in JIRA. I generally do this process on the first and last day of a sprint and maybe once of twice in between but it only takes 1-2 mins so you could do it as often as needed.
That said if Sprints ever did sync to Aha that would be awesome too!
I'd also like to have phases be set to jira sprints and sync'ed to jira.
I like to plan at the high level a the release level but as time gets closer to release date, sprint level detail is useful.