Jira

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.

E.g. if engineering has reported that 100% of work on a release is complete via the Jira integration, update the status to 'ready to ship'

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...

When sending an Aha record to Jira and there’s an error, a message appears with a “Review the errors” link. This opens up the Integration Updates modal. From this page, it's not obvious that you can view the error by hovering over the info icon to...

Often times we only want a subset of what's in Aha! in our JIRA project. In some cases, when things get deprioritized, we want to remove them from JIRA but keep them in Aha! Would love the ability to do that FROM Aha! because keeping things in syn...

Right now you cannot link themes and epics from Jira to Aha- Themes are detached from Epics

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...

Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...

In the Aha! user profile, request the Jira credentials of the user. When making updates to Jira tickets, use these credentials so that we can see in the JIra ticket who actually mae the update. Kendis does this.