JIRA Issue dates event types will not display in Team Calendars if JIRA user timezone is set to GMT format

XMLWordPrintable

    • 7.08
    • 7
    • Severity 3 - Minor
    • 0

      Summary

      JIRA Issue dates event types will not display in Team Calendars if JIRA user timezone is set to GMT format.

      Environment

      This was tested with:

      • Confluence 6.7.2, 6.12
      • JIRA 7.8.0, 7.12
      • Team Calendar 6.0.25
      • JIRA iCalendar Plugin 1.4.7

      Problem

      If JIRA is set to use a “GMT-X” user timezone format, then JIRA Issue dates event does not display in Team Calendars on Confluence.

      Expected Results

      JIRA Issue dates should be rendered in Team Calendars with any timezone format.

      Actual Results

      The JIRA event can only be seen if the user.timezone is set to America/Los_Angeles, for example.
      If the timezone is set to GMT -X format, the following error is seen in Confluence application logs:

      ERROR [http-nio-10.80.10.12-8090-exec-8] [confluence.extra.calendar3.DefaultCalendarManager] executeActionOnHierachy Error on sub calendar com.atlassian.confluence.extra.calendar3.calendarstore.generic.JiraIssueDatesSubCalendarDataStore$JiraIssueDatesSubCalendar@62ce03f7
– url: /plugins/servlet/team-calendars/caldav/4f2cc742-ef63-4981-aca2-ecc38fbb9510/ | traceId: 88863c8533e03f98 | userName: user1
java.lang.NullPointerException
at com.atlassian.confluence.extra.calendar3.calendarstore.CalendarDataStoreCachingDecorator.getEvents(CalendarDataStoreCachingDecorator.java:613)
at com.atlassian.confluence.extra.calendar3.calendarstore.DelegatingCalendarDataStore.getEvents(DelegatingCalendarDataStore.java:734)
at com.atlassian.confluence.extra.calendar3.DefaultCalendarManager.lambda$getEvents$3(DefaultCalendarManager.java:636)
at com.atlassian.confluence.extra.calendar3.DefaultCalendarManager.executeActionOnHierachy(DefaultCalendarManager.java:686)
at com.atlassian.confluence.extra.calendar3.DefaultCalendarManager.getEvents(DefaultCalendarManager.java:632)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      And the following error is seen in JIRA application logs:

      2019-01-14 19:05:48,539 http-nio-8080-exec-10 ERROR cwhite 1145x659255x1 1jqvjj7 10.80.10.12,127.0.0.1 /rest/ical/1.0/ical/search/filter/events.ics [c.a.j.extra.icalfeed.IcalendarResource] Unable to export issues to iCalendar
java.lang.NullPointerException
at com.atlassian.jira.extra.icalfeed.IcalendarResource.toIcalendar(IcalendarResource.java:331)
at com.atlassian.jira.extra.icalfeed.IcalendarResource.search(IcalendarResource.java:305)
at com.atlassian.jira.extra.icalfeed.IcalendarResource.getIcalendarByJql(IcalendarResource.java:286)
at sun.reflect.GeneratedMethodAccessor5237.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
... 19 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:154)
... 1 filtered

      Workaround

      Set the following JVM argument in the setenv.sh file (for Linux) or setenv.bat file (for Windows) of JIRA:

      -Duser.timezone=America/Los_Angeles

            Assignee:
            Unassigned
            Reporter:
            Neha Lokhande
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: