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 Team,
The JIRA issue calendar has stopped displaying due date. It appears that the due date field is being interpreted by JIRA as the created date. Two tickets have due date, but those displaying in created date. Is there any known bug on Jira issue calendars.
Hello, @Lakshmi S
There is no known bug in Jira. Try to to this:
If none of the above solutions work, you may want to try clearing the browser cache or try accessing the calendar in a different browser to see if the issue persists. Additionally, you can reach out to Atlassian support for further assistance with troubleshooting the issue.
Hope it helps!
Hi @Isadora_Nichetti ,
We checked all above mentioned solutions. It didn't work. Thank you for your quick response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you find a solution, it would be great if you could share it here.
We've also had this problem for a few weeks, perhaps related to a Jira update. The standard proposals do not solve this problem. It is noticeable that some of the "Date to display" options in the gadget are reset to "Created" after saving (the first line shows this).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have successfully applied the workaround suggested in the article posted by @gzgenm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.