6,576
Customers have installed this add-on in at least 6,576 active instances.
6,576
Customers have installed this add-on in at least 6,576 active instances.
    by InnovalogAtlassian Verified
    Innovalog is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Cloud, JIRA Server 6.4 - 7.2.5 and more versions
    Versions available for JIRA Server 3.10.2 - 6.3.15
    Supported
    Innovalog supports this add-on.

    Get support

    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 extensions that you can use to implement sophisticated workflows in JIRA Server and JIRA Cloud

    Workflow extensions that you can use to implement sophisticated workflows in JIRA Server and JIRA Cloud

    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

    NOTE: for JIRA Server, click here.

    JMWE for JIRA Cloud provides a collection of workflow conditions, post-functions and validators giving you all the building blocks you need to extend your workflows quickly and without code.

    Post-functions:

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

    Conditions*:

    • Previous Status
    • Separation of Duties
    • Hide Transition
    • Scripted Condition

    Validators*:

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

    *Note to JIRA Cloud users: for technical reasons, JMWE conditions and validators are preinstalled into JIRA Cloud.

    More details

    JMWE for JIRA Server provides a collection of workflow conditions, post-functions and validators giving you all the building blocks you need to extend your workflows quickly and without code.

    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

    Conditions:

    • Previous Status
    • Separation of Duties
    • Hide Transition
    • Scripted (Groovy) Condition

    Validators:

    • Field has been modified
    • Comment required
    • Field is required
    • Field has single value
    • Previous status
    • Parent status
    • Scripted (Groovy) Validator

    User reviews

    (127)
    Sign in to write a review »
    by Thiago Casagrande on 2016-11-24
    We choose to use Jira because the powerful environment that Atlassian provide. Besides the slowness to solve problems and to implement new funcionalities, is a bad decision from Atlassian to basically cut functionalities from Jira and sell it as a third party. After the split in a third party add-on, all the transitions stopped to work, which left really upset the board of my organization. By the way, I needed help to configure dynamics situations in my workflow and Innovalog support rapidly help us to solve all the problems. Now everything is working nicely. Ps.: I know that this is a place to talk about Innovalog's solution, but, Atlassian cutting functionalities left us to think if Jira is the best solution.
    Was this review helpful?YesNo
    by Roland Stens on 2016-11-10
    Really a bit upset with the bait and switch the vendor did on this. First of all, this is a great plugin and when it was free, we used it liberally. But with now making it a paid option, we are pretty much forced to shell out the money.
    Was this review helpful?YesNo
    by Tom Schurman on 2016-11-09
    Due to the slowness of updates, most of its usage is unhelpful. Additionally, we see some field not being set on transition. Where we cannot set directly with the built-in Jira post functions, we workaround by creating a hidden "hack" field that we set first using the built-in post functions, then copy from the "hack" field with the built-in post function. For example, "Component/s" field. We dropped this new add-on like a bad habit and shall not look back. Atlasssian tried hard, but in the end should never have passed QA regressions before releasing it and actually charging us money for it.
    Was this review helpful?YesNo
    by Michelle Melancon on 2016-11-07
    Atlassian removes out of the box functionality as a paid feature. What's next?
    Was this review helpful?YesNo

    Innovalog

    Hi Michelle,

    I understand you might be frustrated by Atlassian's decision, but why give our product, which we spent a full year developing, such a low rating as a result? The alternative would have been to lose the functionality forever, since Atlassian had no choice but to remove all "P2" add-ons from JIRA Cloud.

    Regards,

    David

    by Tomasz Myckow on 2016-11-01
    Useful add, was more useful. However as many people have stated here, going from included in the price to now extra for less features is a raw deal. Given a choice no one would pay more for less. So yes the anger should be with Atlassian for updating their framework not with Innovalog however based on the recent change the value for this is low. $0 for more vs $$ for less
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud add-on pricing work?

    Cloud pricing is subscription based. You are eligible for support and automatic version updates as long as your subscription is active.

    When your subscription renews each month, your pricing tier for host products and add-ons is automatically adjusted (as necessary) based on the number of users in your instance.

    If you've opted for annual billing for your host product, add-ons are also billed annually. Annual subscriptions for this add-on include a discount (12 months for the price of 10).

    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 cloud pricing tier?

    The cloud add-on tier is set automatically based on the maximum tier of the licensed JIRA applications on your instance. For example, if you have JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, your add-on tier is 50 users.

    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 cloud add-ons, you cannot extend your free evaluation period. All cloud add-ons are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the add-on.

    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 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

    Versions

    JIRA Cloud Released 2016-11-14

    Summary

    New features, improvements and bug fixes

    Details

    New features:

    • New field Nunjucks filter to return the value of a field of an object
    • New sprints Nunjucks filter to return the list of sprints for a Board or issue

    Enhancements:

    • In Nunjucks annotations, you can now access fields by real name in addition to field IDs
    • Post-functions that work on linked issues now support the "any" link type

    Bug fixes:

    • Post-functions that set a field value now work on the last transition (they bypass the editable=false workflow step property)
    • Linked issues can now be found even when the current user doesn't have access to them

    Versions

    Version 4.0.5 JIRA Server 6.4 - 7.2.5 Released 2016-09-23

    Summary

    Bug fixes.

    Details

    Bug fixes:

    • [JMWE-439] - Append values option doesn't work when source value is null
    • [JMWE-440] - Parent Status Validator and Previous Status Validator don't display correct error message

    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.

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Find new add-ons screen loads.
    3. Locate JIRA Misc Workflow Extensions.
    4. Click Free trial to download and install your add-on.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar add-ons