Integrations
Sort by:
Recent
Filter by:
Status
Showing 846 of 8098
1
VOTE
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
0
Future consideration
3
VOTE
Provide error if the Jira webhook "Exclude body" checkbox is selected
When configuring a webook in Jira, there is a checkbox: ☐ "Exclude body" Request with empty body will be sent to the URL. Leave unchecked if you want to receive JSON. If someone accidentally checks that, Aha! won't get any updates. There is no log...
0
Planning to implement
1
VOTE
Ability to customize Aha panel in Salesforce
Today, we can customize almost everything in the portal we use in Aha-Salesforce integration, excluding the panel itself that is shown in Salesforce. I would like to be able to: custom the wording of the fields there - e.g. if in the portal I rena...
0
Future consideration
1
VOTE
Need to be able to connect Google Drive files
Looks like Aha! is not approved by Google's application security process? This is a huge issue for us as we are in the middle of planning for upcoming quarters and using Aha! for the first time. Is this likely to be fixed in the future? Is there a...
2
Will not implement
7
VOTE
1
VOTE
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
0
Future consideration
8
VOTE
Show required fields in integration mapping
When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
1
Future consideration
8
VOTE
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
0
Future consideration
12
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
Likely to implement
11
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