Severity
No response
Version
2026.3.10627
Latest Version
I could reproduce the problem in the latest build
What happened?
When adding a new feature flag environment in the drawer if the user has edit permissions scoped to any environments, the Save button is disabled for any environment they select (even environments they should be able to edit).
Reproduction
Create a new team with these roles and assign a user to the team:
- Project view role (unscoped)
- Feature toggle edit role (unscoped)
- Feature toggle edit role scoped to some environments
Log in to Octopus as that user, create a feature flag, and select add environment. Regardless of the environment selected the Save button will always be disabled.
More Information
No response
Workaround
Get another user with unscoped feature toggle edit permissions to create the configuration for that environment: Permissions are correctly applied when editing an existing environment. Once the environment has been configured on the flag, users with scoped permission can edit it.
Severity
No response
Version
2026.3.10627
Latest Version
I could reproduce the problem in the latest build
What happened?
When adding a new feature flag environment in the drawer if the user has edit permissions scoped to any environments, the Save button is disabled for any environment they select (even environments they should be able to edit).
Reproduction
Create a new team with these roles and assign a user to the team:
Log in to Octopus as that user, create a feature flag, and select add environment. Regardless of the environment selected the Save button will always be disabled.
More Information
No response
Workaround
Get another user with unscoped feature toggle edit permissions to create the configuration for that environment: Permissions are correctly applied when editing an existing environment. Once the environment has been configured on the flag, users with scoped permission can edit it.