-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Problem Definition
Confluence allows us to add as many pinned comments to attachments like PDFs as we want.
However, due to a limitation in REST API, it can only load 100 of these, 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:
- Prevent users from adding more than 100 pinned comments to a single version of an attachment.
- Add this limitation to the documentation
- is related to
-
- Gathering Interest
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[CONFCLOUD-43397] Prevent users from adding more than 100 pinned comments and document it
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?
As an Atlassian customer and user of the comments feature (our company relies on it heavily for technical documentation review and collaboration between our doc and developer teams), this issue is a completely unacceptable user experience!!
If there is a hard limit on the number of comments that your API can handle then the Confluence UI should know about and enforce that limit and not allow entry of additional comments when the limit is exceeded!! There is no excuse for allowing users to unknowingly enter data that will no longer be viewable in the UI due to this limitation (and frankly, this should be a report should be a bug in Confluence not a "feature request" or "suggestion").
Because of this issue we are now faced with a doc review that well exceeded the 100 comment "limit" and the best we have been able to get from Atlassian support is a spreadsheet dump of comment text and resolution states but with no context whatsoever in relation to the document that was reviewed (which makes the data dump nearly unusable to us).