Preinstalled
This add-on comes pre-installed in JIRA Cloud instances.
5,223
Customers have installed this add-on in at least 5,223 active instances.
    by Innovalog for JIRA Cloud, JIRA Server 6.4 - 7.1.0 and more versions
    Versions available for JIRA Server 3.10.2 - 6.3.15
    Supported
    Innovalog supports this add-on.

    Get support

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

    Learn more

    Supported
    Innovalog supports this add-on.

    Get support

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

    Workflow conditions, validators and post-functions that you can use to implement custom workflows in JIRA

    Workflow conditions, validators and post-functions that you can use to implement custom workflows in JIRA

    Workflow Validators

    Workflow Post-Functions

    Workflow Conditions

    Enforce custom rules on the data that must be input during a transition, such as requiring that a field is modified, that a comment is provided, or that a multi-select field has a single value.

    Assign an issue to a role member, set a field to a constant value or Groovy expression, copy field values to/from the parent issue or linked issues, and much more.

    Disable (hide) a transition based on the previous status or the actors of an issue, or simply unconditionally hide a transition that is only used indirectly (e.g. through a post-function).

    Workflow Validators

    Workflow Post-Functions

    Workflow Conditions

    Enforce custom rules on the data that must be input during a transition, such as requiring that a field is modified, that a comment is provided, or that a multi-select field has a single value.

    Assign an issue to a role member, set a field to a constant value or Groovy expression, copy field values to/from the parent issue or linked issues, and much more.

    Disable (hide) a transition based on the previous status or the actors of an issue, or simply unconditionally hide a transition that is only used indirectly (e.g. through a post-function).

    More details

    The JIRA Misc Workflow Extensions plugin provides an assortment of workflow conditions, validators and post-functions that you can use to implement custom workflows in JIRA.

    Conditions:

    • Previous Status
    • Separation of Duties
    • Hide Transition

    Validators:

    • Field has been modified
    • Comment required
    • Field is required
    • Field has single value
    • Previous status
    • Parent status

    Post-functions:

    • Assign to role member
    • Assign to last role member
    • Set Field Value to constant or Groovy expression
    • Increase value of field
    • Set field to user property value
    • Copy field value to parent
    • Copy Value from Field to Field
    • Add field value to parent
    • Set field value from parent
    • Copy Field Value to Linked Issues
    • Set Field Value From Linked Issue Function
    • Set Field Value Of Linked Issues
    • Set Issue security from user role
    • Transition Issue
    • Transition Parent Issue
    • Transition Linked Issues
    • Comment Issue
    • Comment Linked Issues

    More details

    The JIRA Misc Workflow Extensions plugin provides an assortment of workflow conditions, validators and post-functions that you can use to implement custom workflows in JIRA.

    Conditions:

    • Previous Status
    • Separation of Duties
    • Hide Transition

    Validators:

    • Field has been modified
    • Comment required
    • Field is required
    • Field has single value
    • Previous status
    • Parent status

    Post-functions:

    • Assign to role member
    • Assign to last role member
    • Set Field Value to constant or Groovy expression
    • Increase value of field
    • Set field to user property value
    • Copy field value to parent
    • Copy Value from Field to Field
    • Add field value to parent
    • Set field value from parent
    • Copy Field Value to Linked Issues
    • Set Field Value From Linked Issue Function
    • Set Field Value Of Linked Issues
    • Set Issue security from user role
    • Transition Issue
    • Transition Parent Issue
    • Transition Linked Issues
    • Comment Issue
    • Comment Linked Issues

    User reviews

    (88)
    Sign in to write a review »
    by weaponZhong on 2015-10-16
    I'm in the free trial. There is a big bug-- "copy field value to parent" doesn't work! My scenario was - In parent issue and subtask there is a field named "Any subtask?" Initial value was "N". When user create a subtask, I set this field value "Y" successful, but when I use post function "copy field value to parent", I even couldn't create the subtask at all. Your attention please! If this bug could be fixed, I would like buy right now.
    Was this review helpful?YesNo

    Vendor response

    Please contact our support (see https://innovalog.atlassian.net/wiki/display/HOME/Getting+Support) so that we can help you.

    by Eric Daily on 2015-06-08
    i'm just reviewing it because it wouldn't let me see which modules were enabled otherwise. probably good tho
    Was this review helpful?YesNo
    by Esraa Masoud on 2015-04-26
    Very helpful plug-in
    Was this review helpful?YesNo
    by Niall Deasy on 2014-12-17
    Can this be upgraded to the latest version? We have a strong requirement for Transition Linked Issues (new in 3.1.1)
    Was this review helpful?YesNo

    Vendor response

    I assume you are talking about our plugin for JIRA Cloud (formerly JIRA OnDemand)? Unfortunately, we have been discussing upgrading JMWE on JIRA Cloud with Atlassian for more than a year now, and it is moving forward slowly. It should be happening early next year (cross fingers). Note however that JMWE became non-free starting with version 3.0.0, so the new version of the plugin on JIRA Cloud will also become non-free.
    by Stephen Etheridge on 2014-10-28
    This is frankly annoying. JIRA hasn't got 10% cheaper but this plugin, which is extremely embedded in certain organisations' workflows, has suddenly made JIRA 10% more expensive. This feels like a price gouge from Atlassian, which is disappointing not only for the financial hit but because it hurts my image of the company itself. It would be great to have some more transparency here, maybe that would restore my faith in the direction of the Atlassian brand (more pro-development, less profit-led). How many people make use of this plugin and does that justify the motivation to make it an 'optional' cost for licensees? What proportion of development time is spent on updating and maintaining this plugin versus 'core' development, and does that justify the 10% price tag? At the moment it looks and feels like a price gouge, and that it saddening from, a company I have grown to really trust. *** Response to Vendor *** - Yes, I agree this functionality should come as standard with JIRA. It's incredibly useful to be able to: * Force a comment when transitioning an issue through the workflow * Force a changelog reference/version number when resolving an issue * Force an estimate before beginning work on an issue * Force a specific Resolution as the result of a test, review (or other) process, without necessarily closing the issue - No, I didn't realise this was not a 1st-party Plugin. The reason I didn't realise this is because the tools I have hitherto been using for free for years are still visible and selectable as options within the workflow WITHOUT the plugin installed. Only when I try to use one of these functions does some red text come up stating I haven't got the plugin installed. The way this is currently implemented, Atlassian are basically 'selling in' the Plugin insofaras it is so heavily endorsed there is an implication that it is 1st-party (or obfuscation of the contrary). There is no mention of Innovalog in the dialog. - Yes, my score is based on my frustration with Atlassian for embedding what is essentially a 3rd-party plugin so deeply into their software without regard for the implications of failing to ensure it is supported it in new versions. I think you can see this frustration throughout the scores and comments here and I would implore you to direct Atlassian this way so they can see for themselves the annoyance this is causing their customers. For what it's worth, I would prefer if they purchased the plugin from you and take on its maintenance or remove all traces of it from the visible default functionality of JIRA to avoid confusion and frustration. I think you've made and supported a good plugin. I think you deserve getting money for your efforts, but the approach for implying the functionality is there and then flagging up a pay wall in red text when you try to enable it is deceptive and wrong on Atlassian's part.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo

    Vendor response

    Stephen, I believe you don't realize that the JMWE plugin is in no way related to Atlassian. It has been developed, maintained and supported since 2008 by me, initially as a free plugin, and when JIRA 6 was released, the API changes were so significant that I was faced with two choices: either drop the plugin, or compensate the migration efforts by making it paid-via-Atlassian. I chose the latter, and the plugin became non-free on May 29, 2013, starting with version 3.0.0 (the previous versions remain free). I understand that you feel the features of my plugin should instead come standard with JIRA. This is an understandable comment, but it should be directed at Atlassian instead of Innovalog. I also have a question for you: is your star rating based on your frustration with Atlassian, or on the quality and usefulness of my plugin? Cheers, David. P.S. : don't hesitate to contact my at atlassian@innovalog.com

    Pricing

    Pricing details are loading…

    This add-on is free and pre-installed on your Cloud instance.

    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

    Support

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

    Innovalog supports JIRA Misc Workflow Extensions. You can visit the support site to get help.

    Get support

    Innovalog supports JIRA Misc Workflow Extensions. You can visit the support site to get help.

    Get support

    Versions

    JIRA Cloud Released 2015-11-04

    Summary

    Major bug fixes

    Details

    Bug fixes:

    • [JMWE-395] - Transition Issue post-function does not work after upgrading to JIRA 7
    • [JMWE-396] - Field is Required Validator not compatible with JIRA 7
    • [JMWE-397] - Post-function "Assign to last role member" broken on JIRA 6

    Versions

    Version 4.0.2 JIRA Server 6.4 - 7.1.0 Released 2015-11-04

    Summary

    Major bug fixes

    Details

    Bug fixes:

    • [JMWE-395] - Transition Issue post-function does not work after upgrading to JIRA 7
    • [JMWE-396] - Field is Required Validator not compatible with JIRA 7
    • [JMWE-397] - Post-function "Assign to last role member" broken on JIRA 6

    Installation

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

    This add-on is pre-installed on your Cloud instance.

    Similar add-ons