Confluence Search API using CQL is returning inconsistent results when comments are deleted.

XMLWordPrintable

    • 2
    • Minor

      Issue Summary

      Confluence Search API using CQL is returning inconsistent results when a comment is deleted.

      Steps to Reproduce

      1.  Create 3 comments in a page, A, B and C in a tree hierarchy(Screenshot 1)
      2. Now copy the URLs of the comments in a notepad.
      https://atlassiantester5.atlassian.net/wiki/spaces/FAVI/pages/3562242049/Testing+pdf?focusedCommentId=3562242049-- comment A
      
      https://atlassiantester5.atlassian.net/wiki/spaces/FAVI/pages/3562242049/Testing+pdf?focusedCommentId=3586850838-- comment B
      
      https://atlassiantester5.atlassian.net/wiki/spaces/FAVI/pages/3562242049/Testing+pdf?focusedCommentId=3586883600-- comment C

      3. Execute  https://api.atlassian.com/ex/confluence/f4c1cbec-b896-4ce3-b4aa-8e5751211556/wiki/rest/api/search?cql=parent=3586850838 - This will return details of comment C. This is expected.

      4.  Now delete comment B from the UI.

      5. Execute  https://api.atlassian.com/ex/confluence/f4c1cbec-b896-4ce3-b4aa-8e5751211556/wiki/rest/api/search?cql=parent=3586850838 again.

      This still returns the result even though the comment B is deleted. The same results are observed after content reindexing also.

      6.  Now execute https://api.atlassian.com/ex/confluence/f4c1cbec-b896-4ce3-b4aa-8e5751211556/wiki/rest/api/search?cql=parent=3562242049/. This gives null results and it is expected.

      Expected Results

      Search API using CQL should return comment details consistently.

      Actual Results

      The comment details are fetched by the Search API even though it is deleted in specific scenarios.

      Workaround

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

            Assignee:
            nmcginley
            Reporter:
            Sajan M (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: