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.

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

Cannot use ticket templates since 2.4 anymore #1913

Closed
sthag opened this issue Apr 3, 2018 · 3 comments
Closed

Cannot use ticket templates since 2.4 anymore #1913

sthag opened this issue Apr 3, 2018 · 3 comments

Comments

@sthag
Copy link

sthag commented Apr 3, 2018

Infos:

  • Used Zammad version: 2.4
  • Installation method (source, package, ..): deb package
  • Operating system: Ubuntu 16.04
  • Database + version: MySQL 5.7
  • Elasticsearch version: 5.6.8
  • Browser + version: Firefox & Chrome latest

Expected behavior:

  • I create a new ticket
  • I select a template and hit apply
  • The template is selected and used for the ticket

Actual behavior:

  • The template is not used
  • nothing happens (no log entry on server or client)

Steps to reproduce the behavior:

  • Create a new template

  • Select this template for a new ticket

  • It is possible to create new templates (log looks normal)

  • It is also possible to delete templates

Yes I'm sure this is a bug and no feature request or a general question.

@thorsteneckel
Copy link
Contributor

Hi @sthag - thanks for reporting! A fix is on its way - currently in QA.
JFI: The bug affects every action pre-filling the tickte create view (template, split etc.).

zammad-sync pushed a commit that referenced this issue Apr 3, 2018
zammad-sync pushed a commit that referenced this issue Apr 3, 2018
@thorsteneckel
Copy link
Contributor

This is fixed with the commits above. The new release is ready to install in ~30 minutes from now. Feedback would be great 👍 Closing for now 🚀

@thorsteneckel thorsteneckel added this to the 2.4.1 milestone Apr 3, 2018
@AchuM
Copy link

AchuM commented Apr 4, 2018

I can confirm this update fixed the issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants