Customers have installed this add-on in at least 13,049 active instances.
    by Adaptavist for JIRA Server 7.0.0 - 7.1.5 and more versions
    Versions available for JIRA Server 3.7 - 6.4.13
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Atlassian Verified
    Adaptavist is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    Adaptavist supports this add-on.

    Get support

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

    Enhance and automate JIRA workflows, JQL functions, custom fields, listeners and more using Groovy

    Enhance and automate JIRA workflows, JQL functions, custom fields, listeners and more using Groovy

    Built-in administration/maintenance scripts

    Powerful JQL functions

    Scripted Fields

    Useful default functionality for administrators, for instance "su" to another user, copy a project etc etc, or run your own groovy scripts.

    ScriptRunner ships with a long list of extremely powerful JQL functions. For instance, query for parent tasks on attributes of their subtasks, find all issues that are blocked by unresolved bugs.

    Create your own calculated custom scripted fields with groovy, the simple scripting language. You may never need to learn maven!

    More details

    ScriptRunner is a collection of powerful but easy-to-use workflow functions, JQL functions, listeners and services.

    Either augment the ones provided with groovy, or write your own. You may never need to write your own java Add-on again.

    • Extra JQL Functions (like hasComments, hasAttachments, hasLinks, lastUpdated, workLogged, dateCompare, hasSubtasks, parentsOf and many more
    • Added Workflow functionality - the ability to extend your workflows to include built-in and scripted Validators, Conditions and Post-Functions
    • Scripted fields give you the ability to show fields with calculated data in issues
    • JIRA listeners gives you the ability to automate JIRA based on certain events
    • Administration built-in scripts give you the ability to bulk update issue resolutions and much more
    • Change the Behaviour of your JIRA fields
    • Make fields mandatory or Read-Only under certain conditions
    • Ability to apply server-side validation before JIRA issues are submitted and much more

    User reviews

    Sign in to write a review »
    by Todd Alden on 2016-03-31
    Like the tool. Currently we only use it for one triggered script, but it works well for that. My complain, as others have, is with the new pricing. To go from free to 10+ % of the cost of JIRA Software is out of line with JIRA pricing (2750 for 2000 user). I also agree with others that the price tiers are very odd and counter to the pricing curves for any other plugin (or any other SW tool that I know of). License for 25 is $25, but license for 2000 is $2750??? Anyway I can buy 80 quantity of 25 user licenses and combine them to save $750? ;-)
    Was this review helpful?YesNo
    by April on 2016-03-23
    ScriptRunner is quite possibly the most useful add-on ever written for JIRA Server. Scripted fields and listeners are awesome, but that's just part of the incredible usefulness of this app. For example, JIRA provides a basic field configuration, where a field is either always or never required. However, JIRA issues are living objects with a life cycle, such that information which is not known when they are created may be required knowledge later in a ticket's progression. Only ScriptRunner can require data entry at a point in time, or easily monitor aging tickets without installing some other add-in. Need to create a subtask or an issue in some other project based on that data? That's covered too. Similarly, JIRA standard perms can be set for the Resolved and Closed transitions, but these apply to all project users, and can't be configured for any other transitions. Only ScriptRunner can provide for mixed usage, by checking group membership when a transition is attempted. These functions are used in nearly every workflow we have. Speaking of functions, the additional search functions ScriptRunner adds to JIRA make this app worth buying even if you never use the other advanced features, like "linkedIssuesOf," "subtasksof," or "datecompare." The built-in administration/maintenance scripts make actions that would take hours or even days into a few minute's work. These scripts make it possible for a single person to support over 1,000 users. Lastly, ScriptRunner's support is simply OUTSTANDING. If you've every asked a question on Atlassian Answers, you are well aware that manay vendors never respond, or take days to notice your question. This team often answers in less than an hour! Bonus, the answers are super-helpful :)
    Was this review helpful?YesNo
    by Filip Heyns on 2016-03-07
    We use ScriptRunner to automatically set the due date based on the priority assigned to the issue. This works great and it reduces the time spent on the handling of incoming Service Desk tickets. We are currently looking into the escalation function to further improve our SLAs. Also the copy project script has proven to be a timesaver. For our user base of just 100 users, the price is acceptable looking at the functionality provided. Has anyone implemented a script to automatically deactivate users that have not logged in for a number of days? I know there is a paid add-on for this, but a script should work just fine.
    Was this review helpful?YesNo
    by Zeeshan Malik on 2016-02-23
    We have been using the ScriptRunner since time and the features are really helpful. We mainly use scripted JQL function like ‘linkedIssuesOf()’ function which are extremely useful. Similarly we also use some built-in scripts for e.g. bulk fix version. There are also many other excellent and useful features in the plugin. I recommend this is a must-have plugin if you want to extend your Jira functionality.
    Was this review helpful?YesNo
    by Tessa Gillson on 2016-02-15
    Is this something that can be used to connect our Service Desk tickets to our Software Project tickets? Currently, we are having to clone tickets and copy/paste information back and forth manually to have our development side tied to the customer's ticket which isn't very efficient but we need the two connected.
    Was this review helpful?YesNo


    Hi Tessa,

    My name is Rafael Franco, I'm the Tech Lead of the Product Team here at Adaptavist. First of all, thanks for using ScriptRunner for JIRA.

    Secondly, regarding your question, it is definitely possible to clone tickets and/or copy information back and forth in an automated way.

    Besides regular support (dealing with bugs, etc) we also provide Consultancy to help our customers write their own scripts and further customise their own use cases. If you're interested, please contact us using our contact form: http://www.adaptavist.com/w/about/contact-us/

    Have a good day,



    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


    Adaptavist is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Adaptavist supports ScriptRunner for JIRA. You can ask a support question via Atlassian Answers to get help.

    Ask a question


    Version 4.3.0 JIRA Server 7.0.0 - 7.1.5 Released 2016-04-19


    Customise the UI with web fragments: http://bit.ly/1Nzb3a5, and minor fixes


    See full release notes at



    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 ScriptRunner 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 ScriptRunner for JIRA. You're prompted to log into MyAtlassian. ScriptRunner 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 ScriptRunner for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons