Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Core Workflow: Does show wrong field list if you only have admin permissions and not ticket.agent permissions #4035

Closed
rolfschmidt opened this issue Mar 25, 2022 · 0 comments
Closed

Core Workflow: Does show wrong field list if you only have admin permissions and not ticket.agent permissions #4035

rolfschmidt opened this issue Mar 25, 2022 · 0 comments
Assignees
@rolfschmidt
Labels
admin area bug prioritised by payment verified
Milestone
5.1.1

Comments

@rolfschmidt
Copy link
Collaborator

Infos:

  • Used Zammad version: 5.1
  • Installation method (source, package, ..): all
  • Operating system: all
  • Database + version: all
  • Elasticsearch version: all
  • Browser + version: all
  • Ticket#10103720

Expected behavior:

  • Not sure, if possible then it should work also without ticket.agent permissions

Actual behavior:

  • If you have admin only permissions then the frontend has wrong ticket attributes set and it will not show the proper attributes in core workflow. For example "customer" is available, but this field should never be there

Steps to reproduce the behavior:

  • Create an admin only user
  • Create an workflow for ticket area
  • Try to select Customer field in ticket actions (not allowed)

Yes I'm sure this is a bug and no feature request or a general question.
@rolfschmidt rolfschmidt added this to the 5.1.1 milestone Mar 25, 2022
@rolfschmidt rolfschmidt self-assigned this Mar 25, 2022
zammad-sync pushed a commit that referenced this issue Apr 11, 2022
@rolfschmidt
Fixes #4035 - Core Workflow: Does show wrong field list if you only h…
b85bd1f 
…ave admin permissions and not ticket.agent permissions.
zammad-sync pushed a commit that referenced this issue Apr 22, 2022
@rolfschmidt
Follow up d565590 - Fixes #4035 - Fix naming collision between Search…
7b0dd26 
…ableAjaxSelect and ObjectManagerAttribute attributes.
zammad-sync pushed a commit that referenced this issue Apr 25, 2022
@rolfschmidt
Follow up d565590 - Fixes #4035 - Fix naming collision between Search…
43aa552 
…ableAjaxSelect and ObjectManagerAttribute attributes.
@rolfschmidt rolfschmidt mentioned this issue Apr 27, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rolfschmidt rolfschmidt

Labels
admin area bug prioritised by payment verified
Projects
None yet
Milestone
5.1.1
Development

No branches or pull requests
1 participant
@rolfschmidt