As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release
No description provided
Dec 14, 2017
We have launched an enhanced Jira integration. This integration will allow you to make the release field a 2-way sync, along with several other new capabilities including the ability to:
Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
Automatically send outgoing changes from Aha! or choose to review and approve them
Import records directly from Jira to make getting started in Aha! easy
When moving a JIRA issue from a linked fixVersion to another linked fixVersion, update Aha!'s release
In the mapping:
Feature -> User Story
If you create a new user story in a fixVersion that's linked to an Aha! release, Aha! reflects a new feature. If you move a user story from one linked fixVersion to another linked fixVersion it is not cha...
over 8 years ago
Jira updating fix version
It would be fantastic if you could allow Jira to push through updates on fix version to Aha!. I was discussing this briefly with your support team and they mentioned that the goal is that Project Managers are managing releases through Aha!. Howeve...