Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16764

Slow /rest/ical/1.0/ical/config/query/options times out for Team Calendar

XMLWordPrintable

    • 7.06
    • 88
    • Severity 2 - Major
    • 216
    • Hide
      Atlassian Update – 21 March 2025

      Dear Customers,

      We appreciate your effort in reporting and providing feedback regarding this issue. We are excited to inform you that the bug has been addressed in the forthcoming Confluence DC 9.4.0 version.

      This fix has been implemented in the Confluence DC and is fully compatible with all supported Jira versions. As a result, we have created a ticket CONFSERVER-99485 within the Confluence Data Center project that correctly tracks the fixed version and effectively resolves this issue.

      At the same time, please be aware that the “Saved filter” query option still depends on the endpoint referenced in this bug, which may render only this option unusable in larger Jira instances. The workaround is presented in the UI - the JQL query option offers a way to search by the filter keyword, which results in exactly the same result. Furthermore, we have initiated JSWSERVER-26345 to monitor this issue, specifically focusing on the affected query option.

      Best regards,

      Krystian M
      Software Engineer, Jira DC

      Show
      Atlassian Update – 21 March 2025 Dear Customers, We appreciate your effort in reporting and providing feedback regarding this issue. We are excited to inform you that the bug has been addressed in the forthcoming Confluence DC 9.4.0 version. This fix has been implemented in the Confluence DC and is fully compatible with all supported Jira versions. As a result, we have created a ticket  CONFSERVER-99485 within the Confluence Data Center project that correctly tracks the fixed version and effectively resolves this issue. At the same time, please be aware that the “ Saved filter ” query option still depends on the endpoint referenced in this bug, which may render only this option unusable in larger Jira instances. The workaround is presented in the UI - the JQL query option offers a way to search by the filter keyword, which results in exactly the same result. Furthermore, we have initiated JSWSERVER-26345 to monitor this issue, specifically focusing on the affected query option. Best regards, Krystian M Software Engineer, Jira DC

      Issue Summary

      REST API request /rest/ical/1.0/ical/config/query/options is taking a long time to return the full set of data that cause the JIRA event creation on Confluence team calendar fails with the timeout error.

      Environment

      Large Jira instance with

      • 2000+ projects, or
      • 30000+ search filters

      Steps to Reproduce

      1. Configure 2000 projects and 30,000 filters in Jira
      2. Go to Confluence, create a Calendar event that pulls in Jira projects

      Expected Results

      Correctly allow the user to choose the Jira project and proceed without error.

      Actual Results

      The below exception is thrown in the atlassian-confluence.log file:

      2019-07-24 04:37:44,960 ERROR [http-nio-8080-exec-1] [calendar3.rest.ExceptionMappers.GeneralExceptionMapper] getResponseError General exception happen on calendar resources
 -- referer: https://confluence/display/ZTEST/calendar/xxxxxxx-9b64-44c5-8a93-810942e14566?calendarName=Release%20Calendar | url: /rest/calendar-services/1.0/calendar/jira/xxxxxxx-cefa-3cdd-9508-4a4945627d9a/query/options.json | userName: admin
com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out

      access_log of Jira show:

      10.0.0.111 252x3288526x4 admin [15/Aug/2019:04:17:18 +0000] http-nio-8080-exec-1 admin "GET /rest/ical/1.0/ical/config/query/options?_=1111111111&xoauth_requestor_id=admin HTTP/1.1" 200 511689 293768 "-" "Apache-HttpClient/4.5.5 (Java/1.8.0)" "xxxxx"

      293768 = 4 minutes 54 seconds

      Notes

      /rest/ical/1.0/ical/config/query/options contains the following data

      • List of projects
      • List of Search filters
      • Names of viewable fields

      Workaround

      Increase the timeout for the calendar connection as mentioned in the KB article JIRA Calendar Read Timed Out.

            [JSWSERVER-16764] Slow /rest/ical/1.0/ical/config/query/options times out for Team Calendar

            Krystian M added a comment -

            A fix for this issue is available in Confluence Data Center 9.4.0 - link to upgrade.

            Krystian M added a comment - A fix for this issue is available in Confluence Data Center 9.4.0 - link to upgrade .

            Lynn McAllister added a comment -

            Hello @Olga Springer,

            Please escalate this bug, as it is a widely used and important integration between Jira and Confluence. The workaround is not a fully functioning mitigation and I'm surprised this is not deemed as a higher-severity. At minimum its a Sev 2, because I do not have a workaround and my day-to-day is impaired, as well as some other people on this thread. This bug was opened in 2018, we're at 5 years, how long is "long-term"? Please escalate this and put it on a roadmap/release. If possible, update the in-active reporter and assign this to someone. I'm sorry but 5 years is far too long, even though there is not an SLA. Thank you for your help on this, I truly appreciate it.

            @end users, please click "Affected customers:" at the top right so that this bug gets a higher UIS score and has more chance of being resolved. Many Thanks.

            Lynn McAllister added a comment - Hello @Olga Springer, Please escalate this bug, as it is a widely used and important integration between Jira and Confluence. The workaround is not a fully functioning mitigation and I'm surprised this is not deemed as a higher-severity. At minimum its a Sev 2, because I do not have a workaround and my day-to-day is impaired, as well as some other people on this thread. This bug was opened in 2018, we're at 5 years, how long is "long-term"? Please escalate this and put it on a roadmap/release. If possible, update the in-active reporter and assign this to someone. I'm sorry but 5 years is far too long, even though there is not an SLA. Thank you for your help on this, I truly appreciate it. @end users, please click "Affected customers:" at the top right so that this bug gets a higher UIS score and has more chance of being resolved. Many Thanks.

            Stasiu added a comment -
            Atlassian Update – 25 April 2023

            Dear Customers,

            Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog.

            The workaround for this bug is as follows:
            Increase the timeout for the calendar connection as mentioned in the KB article JIRA Calendar Read Timed Out.

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Daniel Dudziak
            Senior Software Engineer

            Stasiu added a comment - Atlassian Update – 25 April 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog. The workaround for this bug is as follows: Increase the timeout for the calendar connection as mentioned in the KB article JIRA Calendar Read Timed Out. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daniel Dudziak Senior Software Engineer

            Jason D Smith added a comment -

            We need some good way of cleaning up old public filters to stop this from taking several minutes of users' time every time they want to add an event type.

            Jason D Smith added a comment - We need some good way of cleaning up old public filters to stop this from taking several minutes of users' time every time they want to add an event type.

            Olga Springer added a comment -

            Good morning

            Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs.

            We can see this problem still occurs and impact your organisations. We're moving it to our Long Term roadmap. As of today, we can not prioritise it higher as we are working on other major issues. 

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Olga Springer
            Product Manager, Jira Data Center

            Olga Springer added a comment - Good morning Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. We can see this problem still occurs and impact your organisations. We're moving it to our Long Term roadmap. As of today, we can not prioritise it higher as we are working on other major issues.  Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Olga Springer Product Manager, Jira Data Center

            avigoldyne added a comment -

            we have heavy reliance on and between Confluence and Jira, and trying to increase our dependance on it including with Advanced Roadmaps. This bug is the last hurdle for an entire department to happily migrate from Asana to Jira/Confluence as calendars are crucial and exposed all the way up to the CEO. As an engineer, it seems like this is a very easy fix in adding an additional level of filter as the first step. Force the user to first enter at least the first 2-3 characters of the project name BEFORE trying to query Jira.

            avigoldyne added a comment - we have heavy reliance on and between Confluence and Jira, and trying to increase our dependance on it including with Advanced Roadmaps. This bug is the last hurdle for an entire department to happily migrate from Asana to Jira/Confluence as calendars are crucial and exposed all the way up to the CEO. As an engineer, it seems like this is a very easy fix in adding an additional level of filter as the first step. Force the user to first enter at least the first 2-3 characters of the project name BEFORE trying to query Jira.

            Bryan Guffey added a comment -

            Also affects 8.20.10

            Bryan Guffey added a comment - Also affects 8.20.10

            Crystelle S added a comment -

            @Alex Gay some us are working with 10K+ users, over 2K projects... Data Center instance in our case.

            Hence my suggestion above to limit the API call to the projects that are linked to the Confluence space, not an engineers but it seems like we could avoid it trying to pull everything by narrowing the parameter, and if we narrow is based on a setting users (admins) can access then you don't get into a jira-admin support conundrum/bottleneck.

            Crystelle S added a comment - @Alex Gay some us are working with 10K+ users, over 2K projects... Data Center instance in our case. Hence my suggestion above to limit the API call to the projects that are linked to the Confluence space, not an engineers but it seems like we could avoid it trying to pull everything by narrowing the parameter, and if we narrow is based on a setting users (admins) can access then you don't get into a jira-admin support conundrum/bottleneck.

            Alex Gay added a comment -

            What do you mean with a Large Instance.

             

            We have     

            965 223 issues

            1607 Projects

            7980 Users

             

            And it works as expected with the Workaround.

             

            Alex Gay added a comment - What do you mean with a Large Instance.   We have      965 223 issues 1607 Projects 7980 Users   And it works as expected with the Workaround.  

            Wade Thornton added a comment -

            That workaround does not work for a large Jira instance. 

            Wade Thornton added a comment - That workaround does not work for a large Jira instance. 

              b6cf9181bff6 Krystian M
              yilinmo Yilin (Inactive)
              Affected customers:
              109 This affects my team
              Watchers:
              109 Start watching this issue

                Created:
                Updated:
                Resolved: