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

Default answer type and autofill of e-mail address #938

Closed
BigAndini opened this issue Apr 9, 2017 · 3 comments
Closed

Default answer type and autofill of e-mail address #938

BigAndini opened this issue Apr 9, 2017 · 3 comments

Comments

@BigAndini
Copy link

Infos:

  • Used Zammad version: 1.4.0
  • Operating system: CentOS 7
  • Browser + version: Firefox

Expected behavior:

  • When somebody wrote a new e-mail and a new ticket gets opened it would be great to have the e-mail answer as default value. And the e-mail address of the sender should be autofilled into the To: field of the answer.

Actual behavior:

  • At the moment the To: field is simply empty.

Steps to reproduce the behavior:

  • Create an email feed
  • send email to zammad
  • open the anwer block by clicking into the text field
  • you see the default answer type for a simple note
  • when you change to e-mail the To: field is empty.
@hirbod
Copy link

hirbod commented Apr 11, 2017

"To field" will be filled when you push the "answer" button, but yeah, I would also prefer a pre-filled form when manually switching from note to email.

@sthag
Copy link

sthag commented Jun 20, 2017

I also want to suggest a configurable default behavior for an answer in general. Not only for email.
It would be great if I could set public answer to the default. It's always an internal note.
This could be a system setting or a user bound setting. Maybe even a group or organisation setting.

@thorsteneckel
Copy link
Contributor

This is more or less a duplicate of #372 and will be addressed over there. Closing now.

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

5 participants