For security reasons, we cannot have Aha! set to "allow anyone to access." Still, we need the ability to provide a seamless experience for our Executives and users to derive value from the Aha! data. We want to be able to display these in Tableau ...
Guest
almost 2 years ago
in Wanted
2
Future consideration
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
about 3 years ago
in Jira
0
Future consideration
Show name of user whose token is being used in ADO integration
Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
If comment is deleted in Jira, add a tag <Deleted> to Aha to ensure users are aware of the change (& Vice versa)
What is the challenge? currently, comments that are deleted on one platform, do not get deleted on the other platform (& Vice Versa) What is the impact? Users who work dedicatedly on Aha (like Top Management) will continue to view out-dated co...
Maria V
6 months ago
in Features / Jira
0
Future consideration
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest
over 1 year ago
in Jira
0
Future consideration
Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest
about 6 years ago
in Jira
2
Future consideration
Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...
Guest
about 7 years ago
in Integrations
0
Future consideration
The API pages the data it returns, and the pages are limited to a maximum of 200 records. In scenarios where it isn't possible to programmatically iterate through the pages, such as reporting & (Power)BI, it would be incredibly useful to be ab...
Daniel McGrath
about 6 years ago
in Integrations
1
Future consideration
Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
Austin Merritt
over 6 years ago
in Jira
0
Future consideration
Allow for Lookup Fields to be mapped in SFDC integration
Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Guest
12 months ago
in Salesforce
0
Future consideration