Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Scriptrunner listener on issue events to control dates

Hello all,


I'm looking for a scripted listener (scriptrunner plugin) to compare a custom date field (Start date) to system field (due date) and prevent an update of Start date if higher than due date.

Can someone help me with the script?

Thanks in advance,

1 answer

0 votes
Ken McClean
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 04, 2023

Hi Natalie:

Okay so as I understand it, you want a listener to check on issue update if the start date comes AFTER the due date?

The listener would only detect this when the issue is actually updated, meaning that the user change has already been committed.  

When the listener detects that the start date has been set after the due date, what would you like it to do?

Is this for Jira server or Cloud?

Thanks Ken for breaking this down to this level. This solution is run on JIRA data center.

It's correct that I want it to be detected. Is there a way to prevent the update? Maybe through behavior or Automation??

Alternatively, what would you recommend should happen after the update?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events