Cannot add JIRA Agile Sprints or other JIRA related event type in Team Calendars for Confluence

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

Not able to add a JIRA Sprint event or any other JIRA event type in Team Calendars for Confluence, returning "We can't load events in Project Name - Sprints: Check your connection to JIRA"

When making the following actions:

  • Go to Team Calendars for Confluence
  • Create a calendar if there's no calendar yet
  • Click on Add Event
  • In the Event Type field, select JIRA Agile Sprints or any other JIRA related event type
  • Choose the server if there's more than one
  • Choose the Project and any option to Show
  • Finally, click OK

There's no error in the logs, an error displays on screen as shown in the image below:

 

If we set com.atlassian.applinks and confluence.extra.calendar3 to DEBUG level we'll get the following REST calls from Confluence to JIRA:

2015-08-26 19:32:13,142 DEBUG [http-bio-8181-exec-5] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/search/jql/events.ics?_=1440617533138&jql=project+%3D+%22AR%22&dateFieldName=duedate&includeFixVersions=false&start=1435363200000&end=1447030800000&maxIssue=1000
2015-08-26 19:32:13,215 DEBUG [http-bio-8181-exec-5] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/search/events.ics?_=1440617533212&jql=project+%3D+%22AR%22&dateFieldName=duedate&includeFixVersions=false&start=1435363200000&end=1447030800000&maxIssue=1000
2015-08-26 15:32:15,210 DEBUG [http-bio-8181-exec-1] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/config/query/options?_=1440617535208
2015-08-26 15:32:15,284 DEBUG [http-bio-8181-exec-1] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/serverInfo
2015-08-26 15:32:15,349 DEBUG [http-bio-8181-exec-1] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/project?_=1440617535347
2015-08-26 15:32:17,365 DEBUG [http-bio-8181-exec-3] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/config/query/options?_=1440617537362
2015-08-26 15:32:17,431 DEBUG [http-bio-8181-exec-3] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/serverInfo
2015-08-26 15:32:17,493 DEBUG [http-bio-8181-exec-3] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/project?_=1440617537491
2015-08-26 19:32:19,357 DEBUG [http-bio-8181-exec-18] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/config/query/options?_=1440617539355
2015-08-26 19:32:19,430 DEBUG [http-bio-8181-exec-18] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/serverInfo
2015-08-26 19:32:19,493 DEBUG [http-bio-8181-exec-18] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/api/2/project?_=1440617539491
2015-08-26 19:32:19,868 DEBUG [http-bio-8181-exec-5] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/search/jql/events.ics?_=1440617539864&jql=project+%3D+%22AB%22&dateFieldName=sprint&includeFixVersions=false&start=1435363200000&end=1447030800000&maxIssue=1000
2015-08-26 19:32:19,934 DEBUG [http-bio-8181-exec-5] [core.auth.trusted.TrustedRequest] signRequest signRequest - signing request for url:http://jiraurl/rest/ical/1.0/ical/search/events.ics?_=1440617539932&jql=project+%3D+%22AB%22&dateFieldName=sprint&includeFixVersions=false&start=1435363200000&end=1447030800000&maxIssue=1000

Cause

As we can see, the REST calls are made to the ical class, so in this case the problem happens because the JIRA iCalendar Plugin is disabled or not properly working.

Resolution

To verify that the JIRA iCalendar plugin is enabled:

  1. In JIRA, navigate to Administration » Add-ons » Manage Add-ons
  2. Select All add-ons on the select list
  3. Write "calendar" in the filter field
  4. Make sure the JIRA iCalendar Plugin is enabled and up to date

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.