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
I have an issue with this plugin with latest Redmine 3.4.13.
The user "Test Extern (PAG)" with the assigned role "parsX PowerUser" is not able to change the status of a ticket assigned to him with the following error message:
The field "Abgabedatum" is hidden by your plugin for the role "parsX PowerUser" so for sure he is not able to set this field:
This only happens for tickets where the field "Abgabedatum" (which is not required in any role or ticket status) is already set.
If "Abgabedatum" is empty, the user can change the ticket status without problems.
The workflow for this tracker and role is defined as follows:
The role has read-only access to this field anyway, so requiring to fill the field is bullocks anyway.
If i make the field visible for the role in your plugin settings, the user can submit the intended issue status change.
Can you please have a look at this issue anytime soon?
This also happens when the user wants to add a comment but doesn't change ANY issue fields. This is even more severe I think... :-/
tofi86
changed the title
Submitting a ticket is blocked, user is required to fill fields hidden by this plugin
Submitting a ticket or adding a comment requires the user to fill fields which are hidden by this plugin
Sep 16, 2020
Hi,
I have an issue with this plugin with latest Redmine 3.4.13.
The user "Test Extern (PAG)" with the assigned role "parsX PowerUser" is not able to change the status of a ticket assigned to him with the following error message:
The field "Abgabedatum" is hidden by your plugin for the role "parsX PowerUser" so for sure he is not able to set this field:
This only happens for tickets where the field "Abgabedatum" (which is not required in any role or ticket status) is already set.
If "Abgabedatum" is empty, the user can change the ticket status without problems.
The workflow for this tracker and role is defined as follows:
The role has read-only access to this field anyway, so requiring to fill the field is bullocks anyway.
If i make the field visible for the role in your plugin settings, the user can submit the intended issue status change.
Can you please have a look at this issue anytime soon?
Thanks for your help!
Best regards,
Tobias
System information
The text was updated successfully, but these errors were encountered: