You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue in the Mantis BT Calendar plugin where the calendar permissions do not respect project-specific access levels. Instead of applying the permissions assigned to a user for a specific project, the system incorrectly uses the global access level, preventing users from managing calendar settings even when they should have the appropriate rights.
Steps to Reproduce:
Assign a user a different access level for a specific project than their global access level.
Ensure that in the "Calendar Permissions" settings, the assigned project-level role should allow managing calendar settings.
Attempt to modify calendar settings within the project.
Expected Behavior:
The user should be able to edit the calendar settings based on the project-specific access level.
Actual Behavior:
The system applies the global access level instead of the project-specific one, preventing the user from editing calendar settings.
Environment:
Mantis BT version: 2.27.0
Mantis BT Calendar plugin version: 2.8.0
PHP: 8.0.30
Additional Notes: The permissions for "Manage Calendar Settings" are set correctly in the UI but are overridden by the global settings rather than the project-specific access level. This issue affects users who need different permissions per project.
The text was updated successfully, but these errors were encountered:
Indeed, there is illogicality in the levels of access to the calendar and its settings if the user has. I'll think about whether it is worth changing the model, but for now I suggest you change the level of minimal access to the calendar mood for all projects:
Description:
There is an issue in the Mantis BT Calendar plugin where the calendar permissions do not respect project-specific access levels. Instead of applying the permissions assigned to a user for a specific project, the system incorrectly uses the global access level, preventing users from managing calendar settings even when they should have the appropriate rights.
Steps to Reproduce:
Expected Behavior:
Actual Behavior:
Environment:
Additional Notes: The permissions for "Manage Calendar Settings" are set correctly in the UI but are overridden by the global settings rather than the project-specific access level. This issue affects users who need different permissions per project.
The text was updated successfully, but these errors were encountered: