RELATED IDEAS
Webhook Notifications from the User making the Change
Product Integrations are set-up by a system admin to run through a webhook. We used an Automated User account to set up the webhooks so it's not attributed to anyone specific but the feedback we get from users is that of frustration.
PMs want to see who is making changes to their tickets not "automated user" in the notifications. I also can't ask every user to go into the admin section & update EACH integration for EACH product to 'run as user'. We have 19 products & 20+ integrations. It's illogical to ask hundreds of users to do this.
Most people turn off Aha! notifications in favor of JIRA notifications so we need the Webhook notifications to reflect whoever is actually making the change.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
1
MERGED
Edits made in ADO should be attributed to the integration, not the owner of the Personal Access Token
With the ADO integration, comments made in Aha or ADO when sent to the other side, "owned" by the name of the integration. The comments are then prefixed with text like "Comment made in Aha by Fred:" However, if Fred were to make a change in ADO t...
0
Future consideration
1
MERGED
Integration Webhook Communications
Add an optional field in Aha! for an Administrator to select to envoke a more generic name for these system communications (e.g. "integration user") as an alternative to having to either create a generic account or see all messages as if they were...
0
Future consideration
1
MERGED
Integration notification says that someone else made a change
What is the challenge? When I get notified there was a change, no matter who made the change (even if it was me) it states it was our admin making the change. This is confusing and inaccurate. What is the impact? We have to deep dive every time a ...
0
Future consideration
1
MERGED
Map user from Azure Devops
Rather than the webhook 'run as' user being shown in Aha! for every change that is made via an ADO integration, it would be great to know which ADO user made the change or, failing that, that it was an ADO integration that made the change rather t...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved
This creates traceability issues. If we need the history notes as a record of what happened in Aha, this information is not reliable. This assigns responsibility for so many of the changes in ideas / features to the integration owner which is incorrect and unfair.
We find it confusing as well. Seeing who actually did the work would be fantastic.
Would be great to get this feature - very confusing for the users.
Same here, we use Azure DevOps which has a feature to create things on behalf of a specific user, Aha could definitely implement this feature.
Same here, we need to be able to see the colleague who made the change or at least have the webhooks running under a different identity
Agree with the other comments. This is one of the most frustrating items because for our Product team, all the changes look like they are coming from our Director, who set up the Git integration. Another option would be to include an integration account that could be used for these purposes....anything except having it look like an actual colleague made changes to your features.
Same issue as the others. Not having the ability to see in the subject line of a notification who actually makes the changes is incredibly inefficient and keeps us from using this tool more. Please expedite this as it has been inactive for a long time.
We have this problem too. We have also used the same solution as there is no other alternative. I think ideally SSO could be used so that users don't have to be manually on-boarded or come up with different passwords for the two systems. This would help identify the user who made the change on one system to the other. You guys are the kings of integration. I was surprised this hadn't been done.
My team experiences this frustration also. We want to see who made the change, not the default webhook user. We went to the trouble of adding all the Jira users as Aha! reviewers so they were known to Aha! hoping that would help. Alas, it did not. :(
Please make it possible for Aha! to note who actually made the Jira change.