Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...

It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...

We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...

In workspace settings, once an integration is established, it would be nice to be able hover over the integration and see at a glance the project and board without clicking into the integration and looking at the project/board setup.

There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...

I want to be able to map 1-way a specific status change between Aha and Jira

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...

Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...