+ Peacock blue Coyote

The issue: The current 500 character limit on inline comments makes it difficult to leave comprehensive feedback on articles. When reviewers need to communicate detailed, multi-point feedback, the limit often forces us to split it across the main comment and one or more reply comments just to fit everything in.

Who this affects: This isn't limited to one workflow. It affects: - Technical writers performing editorial/edit-pass reviews on release notes and help content - Product managers reviewing content for technical accuracy - QA reviewers leaving functional/behavioral feedback - Internal subject-matter experts (SMEs) reviewing domain-specific content

Any reviewer leaving substantive, multi-point feedback runs into this limit regularly.

Why this is a problem, not just an inconvenience: Splitting feedback across a comment and its replies creates a real risk that feedback gets missed or only partially addressed. Writers often see the top-level comment and act on it, but may not notice or open the reply thread where the rest of the feedback lives. This means valuable feedback effectively goes unseen, even though it was technically left in the system. For workflows where we're trying to track and improve content quality over time, this directly undermines that goal.

What we're requesting: An increased character limit for comments (or an alternative long-form feedback mechanism) so reviewers can leave complete, comprehensive feedback in a single comment, without needing to fragment it across replies. The current 500-character limit translates to roughly 80–100 words, which is not nearly enough for the kind of feedback our reviewers need to leave. Comprehensive editorial or technical feedback on a single release note entry routinely runs to multiple points, each requiring a sentence or two of context and a suggested fix. A limit in the range of 500 to 1,000 words, roughly 2,850 to 5,700 characters at typical technical-writing density, would let reviewers cover this in a single comment without fragmenting feedback across replies.

+ Apricot cream Koi