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

    Ask a question

    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.

    Productivity enhancements for better workflows

    Productivity enhancements for better workflows

    Default Values for Create Screens

    Essential Validators - e.g. make fields required

    Create new issues with a post-function

    Pre-fill certain fields on the create screen. These extensions can give your users new templates. Provide default values on the first workflow step.

    Many new workflow validators and extensions. Require fields in certain workflow steps - make them mandatory. Includes client side validation for many fields.

    Workflow post-function extension can create new issues and link them to the original issue. Copy the description, assignee, and other fields.

    More details

    Design professional workflows:

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


    • Mandatory Field Validator: Make custom and system fields required in a workflow transition
    • Compare two fields with each other. Supporting number and date fields. For all other types only equality
    • Date Validator: Compares a date field with a fixed date or a variable expression like "7 days"
    • Parent Issue Type Validator for sub-tasks
    • Linked issues in Status Validator
    • User In Project Role Validator
    • User in Field Validator: Validate that the user is set on a certain (custom) field
    • Parent Issue in Status Validator

    Conditions: Linked Issues In Status

    Post Functions:

    • Update/Set custom field to pre-defined value. Allows to set default values, can remove values
    • Copy field value from parent to subtask
    • Copy attachments from linked issues
    • Assign issue to unassigned / specific user
    • Add/Delete watcher
    • Create issue on transition, link to original issue and copy values

    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.

    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.3 JIRA Server 7.0.0 - 7.2.6 Released 2016-11-21


    New Validator and Bugfixes


    • New Validator: Parent Issue in Status Validator. Validate that the parent issue is in one of the configured status.
    • Default Values for Create Screen
      • Bugfix: Do not overwrite fields with blank / empty value and do not override the custom field default value;
      • Improvement: When the user started to fill out values on the create screen and changes the issue type then don't override it anymore with any default value (Thanks Frederik for this suggestion!);
    • Mandatory Fields Validator - Improvement: For multiple tabs on the screen focus the tab where an error message is displayed.


    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