Customers have installed this add-on in at least 30 active instances.
    by David Ericksonfor JIRA Server 7.1.0 - 7.2.3 and more versions
    Versions available for JIRA Server 6.0 - 7.0.11
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    David Erickson supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Enable administrators to run REST API commands as other users

    Enable administrators to run REST API commands as other users

    Accurately Automate

    Simple to Use


    Properly attribute work on issues to the user that actually did the work, rather than to the account your automation scripts use.

    Administrators simply add the "sudo" or "sudo-email" header to the REST call to select the user that performed the work.

    Only administrators can act on behalf of other users. Other users can only attribute work to themselves.

    More details

    This plugin allows administrators to execute commands via the REST API as other users. This is useful for example when triggering Jira issue transitions and time tracking via commit messages from another system. It can allow you to perform these commands as the actual user that made the commit, and attribute it to them, rather than to the automated administrative user.

    === Usage ===

    Issue a REST API command (/rest/api/2/*) as a user with administrator privileges and include a sudo or sudo-email http header in the request. The sudo header should specify the username of the user to perform the command as, ie:

    sudo: testuser

    The sudo-email header will try to locate the user with the supplied email address to perform the command as, ie:

    sudo-email: test@test.com

    User reviews

    Sign in to write a review »
    by Matt Doar [ServiceRocket] on 2015-11-18
    What an excellent idea for an add-on! It makes all those admin tasks using the REST API so much more useful. And the price is very reasonable too.
    Was this review helpful?YesNo


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    David Erickson supports Sudo for Jira. You can ask a support question via Atlassian Answers to get help.

    Ask a question


    Version 1.0.2 JIRA Server 7.1.0 - 7.2.3 Released 2016-08-22


    Adds support for Jira 7.1.X


    This version adds support for Jira 7.1.X.


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Sudo for Jira via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Sudo for Jira. You're prompted to log into MyAtlassian. Sudo for Jira begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Sudo for Jira versions compatible with your instance, you can look through our version history page.

    Similar add-ons