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
This plugin does weird things to my freshly setup Redmine 4.1.1 instance.
After applying the "hidden" permission and saving the change it is not reflected in the matrix, and the number of issue status dropdown boxes reduces (by the exact number of "hidden" permissions applied).
workflow.mp4
These missing permissions do persist to the database, but are not otherwise reflected when managing issues, or when reviewing the workflow as described above.
Could be a conflict with another plugin, but I am unclear which one, or why.
The text was updated successfully, but these errors were encountered:
Appears to be an issue even without other plugins in the mix, presumably a compatibility issue with Redmine 4.1.1
chrislockwood
changed the title
Hidden permission sends workflow matrix wonky, is not otherwise effective
[Bug] Hidden permission sends workflow matrix wonky, not otherwise effective in Redmine 4.1.1
Jan 9, 2021
I have the same issue with Redmine 4.0.5. I set a field to hidden in all issue statuses and the dropdown disappeared for this field as shown in the video. I had no way to revert it! I had to either delete the role and create it again or manually fix it in the Redmine DB. Please, don't use it with Redmine 4.0.5 otherwise you might get into troubles!
EDIT: It didn't work anyway, the field was still visible to the role.
EDIT2: I used the current master.
This plugin does weird things to my freshly setup Redmine 4.1.1 instance.
After applying the "hidden" permission and saving the change it is not reflected in the matrix, and the number of issue status dropdown boxes reduces (by the exact number of "hidden" permissions applied).
workflow.mp4
These missing permissions do persist to the database, but are not otherwise reflected when managing issues, or when reviewing the workflow as described above.
Could be a conflict with another plugin, but I am unclear which one, or why.
The text was updated successfully, but these errors were encountered: