Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-43397

Prevent users from adding more than 100 pinned comments and document it

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 7
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Problem Definition

      Confluence allows us to add as many pinned comments to attachments like PDFs as we want.

      However, the UI will only load the first 100 of these (as it only ever loads the first page of results from the REST API), so adding more than 100 will cause these to not be loaded the next time the attachment is opened, even though they are present in the database.

      Suggested Solution

      Two changes:

      1. Officially document this limitation here
      2. Update the UI to enable loading the next page(s) of comments when available

          Form Name

            [CONFSERVER-43397] Prevent users from adding more than 100 pinned comments and document it

            Hi All,

            We also had this problem since everyone is using Confluence intensely to review document file and made Confluence as centralize documents.

            Rauzan Fikri added a comment - Hi All, We also had this problem since everyone is using Confluence intensely to review document file and made Confluence as centralize documents.

            I've just been looking for a tool to help with document reviews. Confluence was on the list, but this issue rules it out.

            John Bromell added a comment - I've just been looking for a tool to help with document reviews. Confluence was on the list, but this issue rules it out.

            Or at least have a "load all comments" button - even if it is going to be slow.

            Tom Dickson added a comment - Or at least have a "load all comments" button - even if it is going to be slow.

            David Couillard added a comment - - edited

            The first "suggested" solution is not a solution at all for documents which get put out to a multi-disciplined group for comment.  Imagine more than 10 people reviewing a document of at least 10 pages, which is not uncommon for a product requirements document.  100 comments occur quicker than you think.

            The "second" suggestion makes me question what other limitations exist which were, or were not documented.  Also getting requests from less-than-happy users who are pushing to get our documentation moved to a Sharepoint site.

            I agree with Matt Butalla, fix the REST API.

            David Couillard added a comment - - edited The first "suggested" solution is not a solution at all for documents which get put out to a multi-disciplined group for comment.  Imagine more than 10 people reviewing a document of at least 10 pages, which is not uncommon for a product requirements document.  100 comments occur quicker than you think. The "second" suggestion makes me question what other limitations exist which were, or were not documented.  Also getting requests from less-than-happy users who are pushing to get our documentation moved to a Sharepoint site. I agree with Matt Butalla, fix the REST API.

            Matt Butalla added a comment - - edited

            Why not fix the API to allow more than 100 comments? I mean, what this limiting is doing is making our users shy away from Confluence and revert back to using word docs on file systems. Sure a bit of education on file versions will help, or just moving documents into Confluence entirely will help too, but this friction makes it harder for us to sell the tool to our staff. Is this really desirable?

            Matt Butalla added a comment - - edited Why not fix the API to allow more than 100 comments? I mean, what this limiting is doing is making our users shy away from Confluence and revert back to using word docs on file systems. Sure a bit of education on file versions will help, or just moving documents into Confluence entirely will help too, but this friction makes it harder for us to sell the tool to our staff. Is this really desirable?

              Unassigned Unassigned
              jsilveira Jaime S
              Votes:
              19 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: