You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.