Features created due to integration to appear on Releases - Overview, Details view
This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...
Add configuration to JIRA integration so that version creation is optional
Some users may not want versions created in JIRA for each release in Aha! Add an option to the JIRA integration configuration to disable the creation and linking of releases to versions.
Allow Created By User Field to be Updated in UI and via Integration
Currently, there is no way to edit the "created by user" field in Aha! Even though if you go to integration mappings, it allows you to map that field with the Jira "Reporter" field and allows you to toggle the integration to "2-way", yet Aha! Supp...
Mapping of Initiatives to other ticket types in Jira
Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...
As an Aha Administrator, I have a large number of products that link to one JIRA project and having to setup the same integration over and over again for these products is time consuming and painful. Setting up a JIRA integration at a higher level...
Add ability to bulk send features to JIRA when there are multiple JIRA projects
We have 5 teams and in each release, there are dozens of features. We are going to use tags to categorize which JIRA team will work on which features. Example: "Find Team" features will be tagged with "Search", "Recommendation" or "Catalog Managem...
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
Emily Yankush
almost 3 years ago
in Jira
0
Shipped
Engineering has made many attributes in JIRA mandatory, which means I need to create custom fields. They would be OK with a static value that would identify it as coming from Aha!, as they want to make sure they are filled correctly manually but t...
Daniel Hirschberg
over 9 years ago
in Jira
3
Shipped
Track effort (estimates) to prepare features for JIRA separately
When Aha!-JIRA integration is enabled, updating the features estimates on one of the tools, will cause an update on the other.
We suggest to have the possibility to un-map the estimates fields between the 2 tools. So updating on one tool won't aff...