Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-71425

GET /wiki/rest/api/content/{id}/child/{type} start parameter isn't working with custom types

XMLWordPrintable

      Issue Summary

      Start parameter isn't working when using the GET /wiki/rest/api/content/{id}/child/{type} API with Custom Types.

      Steps to Reproduce

      1. Create a new cloud app that introduces its own custom content type
      1. Create two custom content items as children of a page
      1. Request those custom content items through the content child API. Set the start query parameter to 0 and the limit query parameter to 1: GET /content/<id>/child/<custom-content-type>/?start=0&limit=1
      1. Do the same request again, this time set start to 1: GET /content/<id>/child/<custom-content-type>/?start=1&limit=1
      1. Do the same request again, this time set start to 2: GET /content/<id>/child/<custom-content-type>/?start=2&limit=1

      Expected Results

      Get two different responses from items 4 and 5.

      Actual Results

      The start parameter is ignored and we receive the same response from items 4 and 5.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            [CONFCLOUD-71425] GET /wiki/rest/api/content/{id}/child/{type} start parameter isn't working with custom types

            Anshuman Dash (K15t) added a comment -

            Hi Matthew

            We have some limitations in our app - Scroll Documents for Confluence, because of this bug. It concerns the number of read requests or confirmations that we can support (both in the migration and during normal operation).

            Is there any chance this bug can be fixed, or at least, a workaround can be shared?

             

            Thanks!

            Anshuman Dash (K15t) added a comment - Hi Matthew We have some limitations in our app - Scroll Documents for Confluence , because of this bug. It concerns the number of read requests or confirmations that we can support (both in the migration and during normal operation). Is there any chance this bug can be fixed, or at least, a workaround can be shared?   Thanks!

            Matthew Hunter added a comment -
            Atlassian Update - January 12, 2023

            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 Confluence 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.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - January 12, 2023 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 Confluence 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. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              19f388d9de30 Cassio Pilla (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: