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
Operating system (if you're unsure: cat /etc/os-release ): any
Database + version: any
Elasticsearch version: any
Browser + version: MS Edge, v. 124.0.2478.105 (64-Bit)
Actual behaviour
If certain Core Workflow conditions are met and the action specifies that the title should be set to read-only, the title can still be changed, either by the user or by an agent.
Expected behaviour
If certain Core Workflow conditions are met and the action specifies that the title should be set to read-only, then it should not be possible to change the title. If the title is to remain changeable, then it should not be available as an action (read-only) in the Core Workflow configuration.
Steps to reproduce the behaviour
Create a core workflow that blocks the ticket title change as an action.
Reload the page
Make sure that the conditions are met
See how the title can still be changed
Screen.Recording.mp4
Support Ticket
Ticket#10155111
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered:
Used Zammad Version
6.3.1 develop
Environment
cat /etc/os-release
): anyActual behaviour
If certain Core Workflow conditions are met and the action specifies that the title should be set to read-only, the title can still be changed, either by the user or by an agent.
Expected behaviour
If certain Core Workflow conditions are met and the action specifies that the title should be set to read-only, then it should not be possible to change the title. If the title is to remain changeable, then it should not be available as an action (read-only) in the Core Workflow configuration.
Steps to reproduce the behaviour
Screen.Recording.mp4
Support Ticket
Ticket#10155111
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered: