Showing a custom and contextual error message on date comparison validator

[Zeeshan Khan]

I need help with changing the message that is shown to the user on date validation failure within a Jira workflow.

There is no provisioning of showing a custom error message for "compares to another date" validator in company managed space's workflow.

I have attached screenshots of both the validator config and also the currently displayed error message.

[Zeeshan Khan · Accepted solution]

Thanks for the comments folks, however the issue is now resolved. I just needed to tick “Include Time” since both of my fields are date/time picker type.

[Marc -Devoteam-]

Hi @Zeeshan Khan 

On using default validations ootb of Jira there are no options on changing the error message.

[Zeeshan Khan]

Additionally, I also tested by creating Date picker type fields and its actually showing a contextual error message mentioning the field names and the failed validation.

If any of you can help me set the validation for Accommodation Check-In date (Date picker type) to be greater than today's date, that will be helpful. I tried using the Created system field but that is not functioning for some reason.

[Ash H_]

Hi, I'm Ash from Appfire's Expert Services,

You might want to check out JMWE for this, as well. 

To achieve the level of customization you describe, Jira Misc Workflow Extensions (JMWE) does offer a "Build-your-own (scripted) Validator" that is specifically designed for these types of scenarios. This validator allows you to use Jira expressions to compare date fields—such as ensuring a "Start Date" is before an "End Date" or checking a date against the current time—and, most importantly, it includes a dedicated field for a custom error message. Because you can define exactly what the user sees, you can provide clear instructions like "The completion date must be at least 48 hours after the request date" instead of a standard system error. The app also includes an interactive tester, so you can verify your date comparison logic against existing issues before publishing your workflow changes, ensuring the validation behaves exactly as expected.

Hope it helps,
Ash

[Alan Bruce]

Yeah we have run into that as well. We decided to put a description on the field in the portal/form that explains the date needed. (Check out date must be x days later than Check in date). Not perfect but it seems to help mitigate tickets coming in for the 'working as designed' error.