Integrations
Sort by:
Trending
Status:
Shipped
Showing 310
63
VOTE
9
VOTE
6
VOTE
Update Jira integration to use "Parent" instead of "Parent Link"
Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...
2
Shipped
47
VOTE
13
VOTE
Improve visibility of integrations update modal
When users set up an integration and select "auto import records", they are not immediately aware that some records will not just automatically import into Aha! (i.e. those that don't have a parent record that is sync'd). These users are not able ...
0
Shipped
41
VOTE
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
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...
7
Shipped
50
VOTE
Re-enable conversion of Features to Requirements when JIRA integration is active
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...
4
Shipped
56
VOTE
Update Salesforce.com (SFDC) opportunity value automatically from SFDC to Aha! Idea
If we create a feature request based on a SFDC Opportunity, the information presented in Aha (such as dollar value) does not seem to update if that opportunity changes in SFDC. Makes it difficult to determine the actual value of opportunities from...
8
Shipped
52
VOTE
52
VOTE
© 2024 Aha! Labs Inc.•All rights reserved