Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
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 ...
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
Nico Arias-Gonzalez
10 months ago
in Integrations / Jira
0
Future consideration
Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Currently custom tables cannot be integrated with Rally. In our environment we created a custom table to track Initiative Milestones and would like to integrate it with Rally Milestones, but that is not doable given the limitation.
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest
about 2 years ago
in 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
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
over 1 year ago
in Wanted
2
Future consideration
What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
CJ Jacobs
5 months ago
in Jira
0
Future consideration
Flag a broken JIRA integration to the Aha! admin so it can be resolved
What is the challenge? As an Aha! admin, I want to ensure the JIRA to Aha! integration flags errors to me proactively (via email would be great), so that errors in the integration setup can be immediately addressed. What is the impact? As an Aha! ...
CJ Jacobs
5 months ago
in Jira
0
Future consideration