Resolve 1-Hour Discrepancy in Jira Data Center Issue Calendar Gadget
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In this article, we will describe a scenario in which the 'Issue Calendar' gadget shows a 1-hour discrepancy when using a custom date-time field, leading to incorrect JQL generation.
On the calendar, the issues will be displayed on the day, with a hyperlinked [more].
![Calendar gadget displays several issues on March 15, with the additional hyperlinked [more]](https://images.ctfassets.net/zsv3d0ugroxu/7sEIX6ttiUGeOLqVc6ta6J/04c47c6333760c74b44f8ccb131541cb/Screenshot_2025-05-30_at_4.58.33â__PM-20250530-112839.png)
Clicking on [more] will open up the Issue Navigator with a JQL derived from the gadget.
Solution
Setting the correct JVM timezone
Ensure that the Jira timezone in the JVM of each node is set correctly. For instructions, see the articles
Jira Issues Dates events' times are offset by an hour in Confluence Team Calendar
Set the timezone for the Java environment for Jira Data Center
Workaround using the Announcement Banner
The steps outlined in this article are provided AS-IS. This means we've had reports of them working for some customers, under certain circumstances, yet they are not officially supported, nor can we guarantee they'll work for your specific scenario.
You may follow through and validate them on your own non-prod environments prior to production, or fall back to supported alternatives if they don't work out.
We also invite you to contact our Community for matters that are outside Atlassian's scope of support!
If the above-mentioned configuration doesn’t help, then add this JavaScript to the announcement banner.
<script>
setTimeout(function() {
AJS.toInit(function() {
if (document.URL.indexOf("/secure/Dashboard.jspa") >= 0) {
var iframes = document.querySelectorAll('iframe[title="JIRA Issues Calendar"]');
if (iframes.length > 0) {
iframes.forEach(function(iframe) {
try {
// Access the content of each iframe
var iframeDocument = iframe.contentDocument || iframe.contentWindow.document;
// Find all div elements with class "issuesHeader" and modify their links
var issuesHeaders = iframeDocument.querySelectorAll('.issuesHeader');
issuesHeaders.forEach(function(header) {
modifyLink(header.querySelector('a'));
});
// Find the div with class "issues" and target the link with class "moreIssues"
var issuesDivs = iframeDocument.querySelectorAll('.issues');
issuesDivs.forEach(function(issuesDiv) {
var moreIssuesLink = issuesDiv.querySelector('.moreIssues');
modifyLink(moreIssuesLink);
});
} catch (error) {
console.error('Error accessing or modifying iframe content:', error);
}
});
}
function modifyLink(link) {
if (link) {
// Get the current href value
var currentHref = link.getAttribute('href');
// Replace '+01%3A00' with an empty string
var newHref = currentHref.replace(/\+01%3A00/g, '');
// Set the modified href back to the link
link.setAttribute('href', newHref);
}
}
}
});
}, 2000);
</script>Was this helpful?