Hello Atlassian Developer Community,
To ensure consistent flow of communication in threaded comments, we are enhancing our comment visibility validations in APIs. While the core threaded comments functionality remains unchanged, we have introduced additional checks around visibility settings of child comments to maintain the natural hierarchy of conversations.
This will not impact modifying the visibility of the parent comment.
What’s Changing?
As part of this enhancement, child comments will inherit the visibility settings of their parent comments. This ensures that the conversation thread maintains consistent visibility throughout the discussion, with any changes to a parent comment’s visibility automatically flowing to its child comments. These validations help prevent unintended visibility discrepancies between parent and child comments in a thread.
API Changes
For those of you using the REST API, please note that the API will no longer allow changes to the visibility of child comments directly. Attempting to update a child comment’s visibility will now result in a 400 (Bad Request) error.
Impact and Recommendations
API Usage: Please review your API integrations and adjust any processes that attempt to modify child comment visibility.
Examples:
If a parent comment is public and a user attempts to restrict a child comment using the API, the request will return a 400 error.
Changing a parent comment’s visibility to restrict access will automatically apply the same restriction to all child comments.