Skip to Main Content
Status Unlikely to implement
Created by Guest
Created on Dec 16, 2014

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there.

Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the person that made the integration between Jira and Aha. I think the same happens vice-versa. At the moment it gets very hard to track who is doing what between the two systems. I sometimes end up with 3 different names attached to an event.

This is due to a Jira limitation. JIRA does not allow you to create comments on behalf of anotheruser. To vote for this with Jira please go here: https://jira.atlassian.com/browse/JRA-35124

  • ADMIN RESPONSE
    Dec 16, 2015

    We can see the value of this feature as there can be confusion around who is creating comments. As noted, this is due to a JIRA limitation. We will mark as "unlikely to implement" for now, but will revisit in the future when this issue has been resolved.

  • Attach files
  • Guest
    Nov 22, 2022

    According to the voting link for Jira, this functionality is now available for users of the JIRA REST API when building add-ons for JIRA Cloud. Will this now be revisited by Aha!?

4 MERGED

The logged in reporter should always be shown

Merged
I have set up an integration between Aha and Jira. Due to too many API Tokens/Web hooks needed I ran out of of the 25 allowed in the Atlassian account. I had to get a new user with a different email account - and also a different name. Then appe...
Guest over 3 years ago in Integrations 0 Unlikely to implement
4 MERGED

Webhook user should not be used to show the "comments updated by".

Merged
User-1 updates Jira ticket. Aha imports the Jira ticket and shows that "webhook user" updated the Jira comment NOT the user-1 in Jira. This is not a reliable feature especially for Auditing purposes.
Guest about 4 years ago in Jira 0 Unlikely to implement