Since the beginning of this week, date comparisons appear to be messed up, which is breaking some of the filters and transition validators used by our organization. Here is one such validator. Notice that the include time part is unchecked, which indicates that the time used on the date in question should be midnight.
In practice, however, the time used is 4 hours after the current time, and the entered send time is compared as well (even though the validator shouldn't be on the time at all):
(this screenshot was taken at 10:35am)
I can update this validator and our filters without too much trouble, probably, but I'm worried that this is a larger issue with date comparisons that I shouldn't be going around. Help?
It certainly looks like the use of the "now" expression is forcing a time element to be included in this field. I am not aware if this function perhaps had a different means to only force a date and not time in previous versions of either that plugin or JIRA itself.
I would be interested to learn what has changed here recently that might be a factor here, such as an update to JIRA or perhaps an update to the plugin in question.
Hi Atlassian Community! This is Teresa from the Jira Service Desk team. On June 19th, I’ll be hosting a webinar “Asset Management: The Role of Context in ITSM” with Atlassian Partne...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events