# Bug COMMS-341 - Internal comments can be added without a valid token in some cases

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Module | Modules and project features / Comments and activity, Enterprise edition |
| Target versions | 16.0.1 |
| Observed in versions | 16.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) | 16.0.x |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

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

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Activate an enterprise plan via token that allows internal comments
    
2.  Go to Project settings → Work packages → Internal comments tab and activate the feature
    
3.  Lose/remove your enterprise plan by deleting the token in Administration → Enterprise edition
    
4.  Go to a WP
    
5.  Add an internal comment
    

### What is the buggy behavior?

*   Internal comments can be created
    

### What is the expected behavior?

1.  The option to make a comment internal should not be available if the corresponding enterprise plans are not active
    

###
