PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Linking record to integration - display source of truth for each field
When linking a feature to an existing record in another system, when you hover over the system to choose it, Aha! will highlight those fields in green and the others in red. This is not always accurate, in the case of one-way mapped fields. Instea...
Peter Whisenant
about 2 years ago
in Integrations
0
Future consideration
What is the challenge? We use checkboxes for our Acceptance Criteria (AC). Sometimes, it makes sense to add additional detailed ACs under a bigger AC. We use an indent for this, however, after Jira sync, these indents are removed. What is the impa...
Manuel Froehlich
6 months ago
in Jira
0
Future consideration
Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...
Guest
over 7 years ago
in Integrations
0
Future consideration
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.
What is the challenge? When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected a...
Brittani Carmandi-Weber
6 months ago
in Integrations
0
Future consideration
Integration with Smartsheet - Indentation Mapping (Task Name)
What is the challenge? When establishing the integration Smartsheet with Aha!, the integration is very basic. It only allows us to map the information in Smartsheet to one type of item in Aha! (like Releases, Epics, Features ), and it only pulls i...
Albert Pivonka
6 months ago
in Integrations
0
Future consideration
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi
over 9 years ago
in Jira
11
Already exists