nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Server Workflow Validator

Richard Ross_sf63zf

Can I ask you why there is such difference between available Validators for workflows in JIRA Cloud (11 options) versus JIRA Server (only 2 options)?

We paid for JIRA Server, thus only two options for Validations are available - its like this feature doesnt even need to be there, its useless.

Thanks,

Richard

Accepted answers

Sreenivasaraju P

HI @Richard Ross ,

Jira cloud version has more features than Jira server version. You can check in marketplace there are many add ons for the validators and post functions.

David Fischer

The reason why there are way more built-in validators (and conditions) in Jira Cloud than Jira Server is actually historical.

It dates back to 2016, when Atlassian decided to remove all Server (P2) add-ons from Jira Cloud. At that time, JMWE for Jira Server (which was just called Jira Misc Workflow Extensions back then) was running inside Jira Cloud as a "bundled" add-on (running inside Jira's Java virtual machine), and provided a number of workflow Validators and Conditions, in addition to workflow Post-functions.

When JMWE for Jira Server was "unbundled" from Jira Cloud and replaced by JMWE for Jira Cloud, which is based on Atlassian's Connect framework (the framework that supports apps in the Cloud), JMWE post-functions were replaced with their equivalent in the Cloud, but Connect didn't support writing Conditions and Validators. Therefore, JMWE Conditions and Validators were simply removed from JMWE for Jira Cloud. However, in order to avoid breaking existing customer workflows, Innovalog and Atlassian decided to integrate JMWE's Conditions and Validators natively into Jira Cloud. Innovalog donated the code to Atlassian under the condition that they would only incorporate it into Jira Cloud, not Jira Server/DC (where JMWE for Jira Server still provides these Conditions and Validators).

So most of the Conditions and Validators you see in Jira Cloud are actually JMWE Conditions and Validators provided for free to Jira Cloud customers.

Earlier this year (2019), Atlassian added support for Conditions and Validators in the Connect framework, which Innovalog took advantage of to implement additional Conditions and Validators in JMWE for Jira Cloud - you'll recognize them from their "(JMWE app)" suffix.

All comments

Sreenivasaraju P

HI @Richard Ross ,

Jira cloud version has more features than Jira server version. You can check in marketplace there are many add ons for the validators and post functions.

Richard Ross_sf63zf

There are add-ons, but they cost additional money. Nothing is free in JIRA world :-)

Okay, anyway thanks for answer!

Cheers,
Richard

John Funk

Hey Richard - Welcome to the Atlassian Community!

Can't explain why there are move Validators in one product version versus the other. And I know that add-ons cost money, but I think you will get a LOT of value from JMWE for additional post functions, validators and conditions. Well worth the money and super support!

Though I don't use Server, just Cloud, so be sure to check out their capabilities for Server support.

David Fischer

The reason why there are way more built-in validators (and conditions) in Jira Cloud than Jira Server is actually historical.

So most of the Conditions and Validators you see in Jira Cloud are actually JMWE Conditions and Validators provided for free to Jira Cloud customers.

John Funk

Wow - thanks for the history lesson, David. Very interesting!!

Richard Ross_sf63zf

Huh, interesting lesson, thanks! :-) I appreciate it!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software