Integrations
Sort by:
Trending
Filter by:
Status
Showing 944 of 9092
1
VOTE
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...
0
Future consideration
1
VOTE
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...
0
Future consideration
12
VOTE
Provide alternative way to match users when email address is not exposed in 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...
1
Future consideration
40
VOTE
37
VOTE
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. ...
3
Future consideration
16
VOTE
4
VOTE
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...
1
Future consideration
27
VOTE
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...
1
Future consideration
14
VOTE
Allow record mapping to Asana Projects
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 ...
0
Future consideration
23
VOTE
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...
3
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved