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: Stop after match is not saved #4034

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

Core Workflow: Stop after match is not saved #4034

rolfschmidt opened this issue Mar 25, 2022 · 0 comments
Assignees
@rolfschmidt
Labels
admin area bug core workflows 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:

  • Stop after match should be configureable and saveable.

Actual behavior:

  • You can not set stop after match.

Steps to reproduce the behavior:

  • Create a workflow
  • Save it
  • Reopen it and try to set stop after match true

Yes I'm sure this is a bug and no feature request or a general question.
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 core workflows prioritised by payment verified
Projects
None yet
Milestone
5.1.1
Development

No branches or pull requests
1 participant
@rolfschmidt