Summary

Service Desk reports are showing in the 'month' drilldown for February issues created from March 1st, 2nd and 3rd, for some reason.

We can see these same ticket in March report as well.

As an example, this is a report for February:

Notice the issue TSP-3 is shown. The same ticket is shown in March:

This issue was created on March 3rd, so it should only show on March:

Environment

Version is actually this one: 3.3.0-OD-1000.1111.1, not available in "Affects Version/s"

Steps to Reproduce

1. Go to a Service Desk project on March 1st, 2nd or 3rd
2. Go to any report in the project including those issues
3. Select 'Past year by month' in the dropdown menu
4. Click the 'February' month point in the graph (for a series containing issues from March)

Expected Results

Only issues from February are shown in the details part.

Actual Results

Issues from March 1st, 2nd and 3rd are also shown

Workaround

This workaround may fix some but not all instances affected by this bug.

When the operating system timezone is behind the timezone set in Jira user's profile (which may actually be the Jira default if they haven't changed it). Being behind the system TZ causes the label to be incorrect, which is why they appear to be in the wrong month.

Users can fix this discrepancy by either changing their own timezone (via their JIRA profile) or the operating system timezone, as long as they match. Customers may need to quit and re-open their browser before the changes take effect.