Validation to ensure that Planned End date/time is different to Planned Start date/time

[Pete Tiddy]

Hi there.

A problem we have encountered is that sometimes our users will create Change Records where the Planned End date/time is same as the Planned Start date/time.

This means that these changes are not then visible on the Change Calendar.

We can educate our users, and the owners of the change function will police this aspect, but is there some simple field validation we could put in place to prevent this issue at source?

Many thanks for your help.

[Marini Marini]

Hi @Pete Tiddy 

Welcome to the Atlassian community!

You can definitely add the Date Compare Validator to the workflow Create issue transition. Here is how we did it:

Cheers,

Marini