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...
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf
over 3 years ago
in Integrations
4
Future consideration
Ability to update Jira Affects Versions field from Aha via integration
What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner
over 1 year ago
in Jira
1
Future consideration
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest
almost 7 years ago
in Jira
6
Future consideration
Development Integration -- Support rendering of images embedded in description field
Currently when you import from Jira or Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in...
Our company is looking to adopt WorkBoard as our corporate standard for OKRs. Our development business units use Aha to manage our product strategy and roadmaps so we need to have integration between the 2 systems in order to maintain continuity o...
Joe Granville
about 5 years ago
in Wanted
3
Future consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
about 10 years ago
in Jira
17
Future consideration
Ability to map custom Initiative fields in Jira integrations
What is the challenge?
Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration.
What is the impact?
Unable to pass this information over to Jira
Describe your ...
Stephanie Lechner
4 months ago
in Jira
0
Future consideration
What is the challenge? Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! record...
Michael Bruner
11 months ago
in Integrations
0
Future consideration
Zendesk integration supports custom layout on ideas
Is it possible to have a custom field visible on the zendesk create idea/link form? We are starting to using a custom tag field to help identify product components. It would greatly help if we could apply categories and custom field information wh...
Guest
almost 9 years ago
in Integrations
9
Future consideration