The behavior does make sense, since the date values provided use day-precision. Since the created date uses the time of day as well, following your logic, 2013-06-17 should be translated to different values depending on the comparator (< or >).
So IMHO, the current behavior is better since it provides some degree of consistency. Additionally, you might want to consider using jql functions like startOfDay() and/or endOfDay().
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot