2016-12-21 02:46:53 +00:00
<!--
2017-11-15 16:33:14 +00:00
Hi there - thanks for filing an issue. Please ensure the following things before creating an issue - thank you! 🤓
2016-12-19 10:49:19 +00:00
2017-11-15 16:33:14 +00:00
Since november 15th we handle all requests, except real bugs, at our community board.https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board.
If you think you hit a bug, please continue:
2016-12-20 14:59:10 +00:00
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
2016-12-25 11:27:00 +00:00
- Please write the issue in english
2017-10-18 13:29:53 +00:00
- Don't remove the template - otherwise we will close the issue without further comments
2017-10-18 14:13:37 +00:00
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
2016-12-21 02:46:53 +00:00
2017-11-15 16:33:14 +00:00
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
2017-09-25 09:30:12 +00:00
2017-01-11 17:35:46 +00:00
* The upper textblock will be removed automatically when you submit your issue *
2016-12-20 14:59:10 +00:00
-->
2016-12-19 10:49:19 +00:00
2016-12-21 02:49:31 +00:00
### Infos:
2016-12-19 10:49:19 +00:00
2017-12-09 10:04:51 +00:00
* Used Zammad version:
* Installation method (source, package, ..):
* Operating system:
* Database + version:
* Elasticsearch version:
2016-12-20 14:59:10 +00:00
* Browser + version:
2016-12-19 10:49:19 +00:00
2016-12-21 02:49:31 +00:00
### Expected behavior:
2016-12-19 10:49:19 +00:00
2017-12-09 10:04:51 +00:00
*
2016-12-19 10:49:19 +00:00
2016-12-21 02:49:31 +00:00
### Actual behavior:
2016-12-20 14:59:10 +00:00
2017-12-09 10:04:51 +00:00
*
2016-12-20 14:59:10 +00:00
2016-12-21 02:49:31 +00:00
### Steps to reproduce the behavior:
2016-12-20 14:59:10 +00:00
2017-12-09 10:04:51 +00:00
*
2016-12-20 14:59:10 +00:00
2017-12-09 10:04:51 +00:00
Yes I'm sure this is a bug and no feature request or a general question.
