My ideas: Jira

JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...

JIRA Portfolio allows for the notion of Initiatives. Portfolio is good for provide views for about 3 months (short-term), beyond that we have found it to struggle. It will be good to sync initiatives so it is possible for engineering to see what i...

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...

When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...

We would like to roadmap product releases with new up-coming features and bug fixes. Aha features currently map to Jira stories but we'd like to map to Jira 'Bug' and possibly 'Improvement' types as well.

Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...

What is the challenge? When mapping Components in Jira to a predefined choice custom field in Jira, you are not given the option to map the values. If there is a failure in the import due to this field, no record or error information is displayed....

If we already have issues in JIRA that are duplicates of features in Aha! we want to be able to manually create a link between them.