We have a template that we use for each release. There are predefined to-do's that we must consider but many times several are not relevant. It would be great to be able to select a few and delete
Release Owner Sync to Non-Version JIRA Ticket Type as Assignee in 2.0 Integrations
Allow the Release Owner to be sync to JIRA ticket as Assignee for JIRA ticket types like Epics.
User Case Scenario
Releases as they have a timeline and show prominently on the Aha! Release Chart, they are use to timeline/roadmap tasks. When col...
Currently, Release Phase dates are 100% dependent on the Features within, however, we often need time after dev work is complete to finish the To-Do's (non-technical work) of the Phase itself - but you can't extend out the phase.
It makes more se...
Import release-initiative links during a CSV import of releases.
It would be valuable when doing bulk imports of releases to be able to associate any related initiatives to them at time of import. Especially as the Initiative ID can already be retrieved via the Aha! interface or via the ID column when exporting...
I want to create a report of my release milestones, and their dates, in a list report. You've got this awesome new way to iteratively specify the content of your reports, but I only have options to use a release, or a release phase. Not a release ...
Ida van Jaarsveld
over 6 years ago
in Releases
12
Shipped
The ability to configure the default release template at the account level
Whilst we educate people not to use the default release phase option if phasing is not relevant to them (which is all of our product managers), it is preferred if we can set what the default release phase values are. If you apply this option at ac...
Project Parker
almost 7 years ago
in Releases
0
Shipped
When creating a release template, it is today not so easy to validate from the list of phases that the overall planning makes sense. To do so, I need to create a new fake release from the template, look at the Gantt and check what was wrong. Then ...
When sending an Aha Release to Jira all Aha features in that release get sent to Jira, creating duplicates.
My requests: Like for features, there should be a function to link an Aha release to an existing Jira release without sending any issues.
A...
When the Parking Log contains a long list of features, the call to action (CTA) in the releases area is out of sight because it is positioned to be vertically and horizontally centered. Consequently, it's not always visible.