# Feature COMMS-199 - Introduce internal comments

Project: Stream Communicator
Status: closed
URL: https://community.openproject.org/work_packages/COMMS-199

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 16.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| COMMS-246 | Implementation approach - Comments with restricted visibility | decided | Option 1 as it is the simplest path to enable the comments with restricted visibility feature |
| COMMS-257 | How should we assign the default permissions for comments with restricted visibility? | decided | Grant this new permission to all roles also having the "Manage members" permission |
| COMMS-258 | How should we treat attachments for work packages comments with restricted visibility | decided | Change the attachments container from the work package to the journal (comment) so that they are seen as inline |
| COMMS-262 | Should we change the activity tab unread notification comment badge size to small | decided |  |
| COMMS-263 | Primer Colors for Work Package Comments with Restricted Visibility | decided |  |
| COMMS-264 | Acitivity tab comment editor shrinks before restricted visibility checkbox can be clicked | decided |  |
| COMMS-267 | Amend restricted visibility checkbox design so that it is accessible | decided |  |
| COMMS-274 | Revisit implementation approach - extracting comments | resolved |  |
| COMMS-284 | Is it okay to leak "last updated" information on the work package (due to restricted visibility comments)? | decided | Yes, acceptable for 15.5. |

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-200 | Add new permissions for restricted work package comments | Implementation | closed |  |  |  |
| COMMS-201 | Add capability to create work package comments with restricted visibility (UI) | Implementation | closed |  | 16.0.0 |  |
| COMMS-202 | Define and implement work package comments with restricted visibility database model | Implementation | closed |  | 16.0.0 |  |
| COMMS-203 | Define and implement work package comments with restricted visibility backend services | Implementation | closed |  |  |  |
| COMMS-204 | Define Quoting criteria for work package comments with restricted visibility | Implementation | closed |  | 16.0.0 |  |
| COMMS-205 | Ensure notifications work in both restricted and unrestricted state independent of permission changes | Implementation | closed |  | 16.0.0 |  |
| COMMS-206 | Define @mention criterion for work package comments with restricted visibility | Implementation | closed |  | 16.0.0 |  |
| COMMS-207 | Honor work package comment with restricted visibility permissions on the activity tab (in both notification center and wp full view) | Implementation | closed |  | 16.0.0 |  |
| COMMS-208 | Add capability to enable and disable work package comment with restricted visibility at project level | Implementation | closed |  | 16.0.0 |  |
| COMMS-210 | Consider incorporating the community contribution to form the foundation of the feature crediting the contributors | Implementation | rejected |  |  |  |
| COMMS-254 | Exclude work package restricted comments from journal aggregation | Implementation | closed |  |  |  |
| COMMS-266 | Add feature flag | Implementation | closed |  | 16.0.0 |  |
| COMMS-268 | Adjust the behaviour of attachments to allow for restricted visibility | Implementation | rejected |  |  |  |
| COMMS-270 | Adjust Activity tab comment dismiss strategy to include cancel button and Esc keyboard action | Implementation | closed |  | 16.0.0 |  |
| COMMS-271 | Implement redesign of "restricted visibility" checkbox placement in desktop and mobile | Implementation | closed |  | 16.0.0 |  |
| COMMS-286 | Testing GitHub integration | Implementation | closed |  |  |  |
| COMMS-287 | Testing GitLab integration | Implementation | closed |  |  |  |
| COMMS-308 | Rename restricted visibility to internal comments | Implementation | closed |  | 16.0.0 |  |
| COMMS-312 | Rename restricted visibility checkbox to internal comment | Implementation | closed |  | 16.0.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-276 | Documentation | Update "Learn more" link to point to correct documentation once updated | closed | Maya Berdygylyjova | 16.0.0 |  |  |
| COMMS-255 | Code maintenance | POC: Exclude work package journal comments from full model copy | rejected |  |  |  |  |
| COMMS-309 | Code maintenance | Decouple CKEditor mentions from work package resources allowing other types of resources to be mentionable | new |  |  |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

See <mention class="mention" data-id="31163" data-type="work_package" data-text="#31163">\#31163</mention>

<br>

Comments with restricted visibility permissions need to be applied on all activity pages- project activity, global activity.