Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-9971

Export Objects using User Friendly format while filtering with a large IQL condition results in 414 error

XMLWordPrintable

      Issue Summary

      Export Objects using User Friendly format while filtering with a large IQL condition results in 414 error

      Steps to Reproduce

      1. Access an Insight Schema that has many assets(2k+ at least)
      2. Creates an IQL filter that has more than 1K conditions like: key in (key-1, key-2, key-3.... key-1500)
      3. Try to export the results in a user-friendly format.

      Expected Results

      • Results are exported successfully.

      Actual Results

      The export fails due to 414 Request-URI Too Long

      Workaround

      Split into batches the IQL conditions like.

      • key IN (key-1 ... key-300)
      • key IN (key-301 ... key 600)

            [JSDCLOUD-9971] Export Objects using User Friendly format while filtering with a large IQL condition results in 414 error

            Nicole made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Nicole made changes -
            Labels New: timeout-bulk-close202205

            Nicole added a comment -
            Atlassian Update - May 10, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com.

            Thank you again for providing valuable feedback to our team!
            Jira Service Management Cloud team

            Nicole added a comment - Atlassian Update - May 10, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com . Thank you again for providing valuable feedback to our team! Jira Service Management Cloud team
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            Radu made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Thiago Behm. created issue -

              Unassigned Unassigned
              tbehm@atlassian.com Thiago Behm.
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: