Skip to Main Content
Status Future consideration
Categories Jira
Created by Guest
Created on Feb 7, 2018

Run As User JIRA Webhook Integration Account should not consume a license seat tells us that if we don't want all imported changes from JIRA to Aha to appear as though a regular "Contributor" or "Product Owner" account has made the changes, we need to create a Paid account just to change the integration name for ingested changes.

Frankly, this feels a little preposterous.

What you're asking me to do is burn a license seat ($1200 a year on our tier) just to change the name on imported records.

I would strongly recommend that you consider for any JIRA Integration, you work out a way to provision a read-only sync account with global access to be selected as the Run As User. 

It is not fair to ask customers to burn a licence just for this feature.

  • Attach files
  • Guest
    Nov 8, 2022

    I received the same guidance today on my request to either mask or otherwise tag integration updates to a generic 'Jira Integration' user/account. Using a paid seat for this purpose is unreasonable.

    I have logged a few Aha Ideas, and voted on several existing requests, in hopes that simple/no-brainer updates would be made. I'd encourage anyone reading this to put pressure on Aha to take action on common sense updates. It seems unreasonable that a request for admin functionality such as this created in 2018 with 80 votes (power users/admins), and pretty steady recent engagement on this topic, has not been delivered.

  • Gene Lewin
    Aug 3, 2022

    Couldn't agree more with this idea ... it's pretty crazy that we have to consume a paid seat for this purpose.

  • Zoë Frances
    Jun 15, 2022

    Agreed, I now have the same problem as everyone who has commented here. I set up the integration so now it looks like I'm commenting on work items in Azure DevOps. It would be nice if the user name could just be replaced with "Aha! Integration" or something. I do appreciate that at least the comment includes the name of the person who actually commented in Aha!.

  • Sarah Gulczinski
    Dec 21, 2021

    Our solution was to use my name. So whenever a change originates in Jira users are told that it's me. (We didn't want to pay a whole license for this.) But it's painful because I get messaged sometimes from people asking me if I made the update and why I was working on their stuff. We really need this resolved.

  • Guest
    Sep 8, 2021

    Yes, badly needed. We use DevOps but similar issue

  • Eva Altass
    Jun 1, 2021

    Totally agree, it is not a good user experience to see a person's name making changes to aha records when it is the integration making the updates - we added a JIRA Bot user name to avoid confusion, but it is a PAID seat which is exorbitant!!

  • Walter Capitani
    May 25, 2021


  • Andrew Brooks
    Mar 5, 2021

    I completely agree with everyone on this one!

  • Rachel Jones
    Dec 15, 2020

    The same also happens in DevOps with integrations. Would be useful to be able to set it to an "Integration" person rather than an individual.

  • Guest
    Dec 15, 2020

    This is definitely required. I shouldn't have to use a paid license for this. I've got users asking me what I'm changing and why because I'm the user that set up the integration. I can set up a generic "Jira Integration User" but shouldn't have to use a paid license for this. You should be able to set up a user that can only be used for integration and not have it be a paid license.

  • Guest
    May 11, 2020

    Yes, same issue here with GitHub Enterprise integration. It's hard to view Aha! as a serious enterprise product without this capability.

  • Dave Tucker
    Apr 7, 2020

    Agreed. We have exactly the same issues as those outlined in the other comments

  • Dan Jeffery
    Dec 20, 2019

    Please could we get an update on this. I have no solution to deal with it. We are starting to switch our integration on and every single update has my name against it in the history. I am getting emails from Product Managers aksing why I have changed certain fields on cards, but it is changes that are coming from Azure DevOps. Please help. Azure DevOps have service accounts to clearly identify that is was a 'system integration' change. We also don't have to pay for an additional licence for service accounts with Azure.

  • Dan Jeffery
    Nov 14, 2019

    This is something that Aha need to address ASAP! It is totally unacceptable to expect us to have to have a paid for seat for something that other applications manage perfectly well as standard. Each paid for seat should be able to deliver the same level of value... this scenario doesn't.

    We have a big audit issue in that my name is the one currently showing as making certain changes that are coming from the integration. I have no way of defending what is genuinely changes that I have made versus the integrated tool. Furthernore, I have no way of creating a dummy account as we are not able to create additional email accounts here so that means I cannot achieve this even if we were happy to pay for an additional licence every year.

  • Tiffany Long
    Aug 9, 2019

    Totally agree. We are a small business and we are forced to have everything go under one PM's name or pay for another license when we had a hard time getting approval for the limited number of licenses we needed already. To get an extra just so we don't have everything so under one name is ridiculous. 

  • Guest
    Oct 25, 2018

    Yes this leads to confusion where others receiving the notification don't know if it's coming from me manually (and is therefore worth checking into) or whether the notifications are just from the JIRA integration but have my name because I set up the integration.

  • Avigail Ehrenhaus
    Aug 2, 2018

    STRONGLY AGREE!  This should be applied to other integrations as well.

    It's not just a cost issue (although that is important given how $$ Aha is), it's also an issue because if someone leaves the company , and no one remembers to update the integration that runs under their account, the integration will break.  


Add ability to change webhook owner that is displayed in Rally

When an update is made in Rally due to an integration with Aha, in Rally history, it shows the webhook owners name. This is confusing as it is hard to tell if a change was made by an actual person or by the integration. It would be helpful if it c...
Karla Johnson 7 months ago in Rally 0 Future consideration