Customers have installed this add-on in at least 87 active instances.
    by codecentric AGfor JIRA Server 7.0.0 - 7.3.0 and more versions
    Versions available for JIRA Server 6.3 - 6.4.14
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    codecentric AG supports this add-on.

    Get support

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

    Quickly create custom Workflows with new Validators, Conditions, Post Functions and Default Values

    Quickly create custom Workflows with new Validators, Conditions, Post Functions and Default Values

    Default Values for Create Screens

    New Validators & Conditions

    Great Post Functions

    Prefill fields on the create screen of Issues and Sub-Tasks.

    Define complete templates or provide simple default values on the first workflow step. Find out more..

    Require fields on transition screens - Verify that a date is in the future or past - Compare fields with each other - Make sure a field value has been changed - Check that a user is in a custom field - and many more..

    Create and link issues on transition - Copy values from field A to field B, from parent to sub-task and sub-task to parent - copy attachments from linked issues - add watchers via a custom field - and many more..

    More details

    Design great custom workflows:

    • Define Default Values for Create-Screens - globally or project-specific


    • Compare two fields with each other
    • Date Compare Validator
    • Field Values Changed on transition
    • Linked Issue Status Validator (includes sub-task link type)
    • Number Compare Validator (e.g. "votes" > 3 or "story-points" < 20)
    • Parent Issue Status Validator
    • Parent Issue Type Validator
    • Required Fields Validator: Make custom and system fields mandatory in a workflow transition
    • User In Project Role Validator
    • User in Field Validator

    Conditions: Linked Issues In Status

    Post Functions:

    • Add / Remove Watchers via Custom Field
    • Assign to User specified in a (Custom) Field
    • Copy Attachments From Linked Issues
    • Copy Field Value From Parent Issue to Sub-Task
    • Copy Field Value From Sub-Task to Parent Issue
    • Create And Link Issues Post Function
    • Set Assignee to specific User
    • Update/Set Custom Field to predefined value (can be used to set default values on transition)

    more functionality

    User reviews

    Sign in to write a review »
    by Danny Prill on 2016-11-25
    Whenever I create new workflows, Workflow Essentials provides lots of workflow functions that make our workflows better and I as an admin am missing in JIRA Core.  For example, when the user creates a subtask and did not specify a due date, we copy this value from the parent issue. An improvement could be, that the value is pre-populated in the create subtask-mask so that the user can see it instantly. I'm looking forward to it. ;)  Also it's very nice that the required field validator enables you to set mandatory fields on transition screens. A nice feature is that required fields a highlighted with a red asterisk just like globally required fields.  Nice!
    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.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on is technically available across the whole JIRA instance. Therefore the above guidelines for the license tier still apply.

    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


    codecentric AG supports Workflow Essentials for JIRA. You can ask a support question via Atlassian Answers to get help.

    Ask a question


    Version 5.4 JIRA Server 7.0.0 - 7.3.0 Released 2016-12-13


    New workflow functions and improvements


    New Features:

    • New Post Function: Copy field values from Sub-Task to Parent Issue
    • New Validator: Verify that a field value has been modified on a transition screen
    • Date Compare Validator: New option to compare a field with current date/time
    • Number Validator supports "Votes" system field.
    • Required Fields Validator now supports "Assignee" field.
    • Default Values for Create Screens: Issue Types are ordered alphabetically


    • If Sub-Task and Parent Issue has a different Workflow and transition is triggered from a context menu, the red asterisks was not placed on the correct fields.
    • Removed sub-task issue types form create-and-link post function (because they are not supported atm)
    • Fixed URISyntaxException when saving Default Values


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

    Similar add-ons