What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
Michael Tucker
2 months ago
in Jira
0
Planning to implement
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer
almost 7 years ago
in Dependencies / Jira
3
Future consideration
The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.
Daniel Lynch
about 3 years ago
in Salesforce
0
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
2 months ago
in Jira
0
Future consideration
Map detailed estimates by initiative in Jira integration
What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus
2 months ago
in Jira
0
Future consideration
When using Import Records, not retaining parent/child relationship (AzDo Integration)
Who would benefit? Aha users when setting up a new workspace What impact would it make? Improves ability to only bring in needed records How should it work? After setting up integration mappings with parent/child relationships, have import records...
Guest
10 months ago
in Integrations
1
Future consideration
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei
almost 3 years ago
in Asana
0
Future consideration
Including Attachments from Comments for Jira Integration
It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi
over 4 years ago
in Integrations
3
Future consideration