Used Zammad version: 3.1.x
Used Zammad installation source: package
Browser + version: Mozilla Firefox
When I define a report-profile to filter based on a certain “particularity” (not sure if this is the proper word, see images) it won’t produce any information. Attaching a label with the same text does.
It does not report anything when checking for the defined “particularities”, however it does show that it can find information.
So it seems to me that it should be working just fine…
Looks like this issue:
opened 04:21PM - 22 Oct 19 UTC
closed 02:34PM - 17 Nov 19 UTC
bug
reporting
verified
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- 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!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
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).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 3.1 and earlier
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any (but verified von 5.6.x)
* Browser + version: any
* Ticket-ID: #1053174
### Expected behavior:
When having e.g. selects or tree selects with several values that contain any legimate character, the Reporting will -when using a Report profile- return all tickets affected by this search.
### Actual behavior:
When having selects or tree selects, the Reporting will not return all affected tickets, when using Reporting profiles that search for values that contain e.g. `_`.
This also affects the 6 tabs below the graph, closed and opened for exmaple will remain empty.
#### Technical background:
Elasticsearch pulls apart strings and uses single words for indexing.
This makes it's search so fast and good, however, if you then search for `my_value`, you won't find what you're looking for.
### Steps to reproduce the behavior:
* Create a custom field with select or tree select
* put some values into it, ensure at least one key has `_` in it
* save the object and restart Zammad
* create a report profile that looks for everything like your custom object with the `_` value
* create several tickets and select the key with `_` to have data for your reporting
* now go to reporting and try to filter for this profile
Yes I'm sure this is a bug and no feature request or a general question.
If so, this should be adressed with Zammad 3.2 coming this week.
If it still doesn’t work, please let us know, I’ll have another look then.
Hello,
Thank you for the reply. I will check back in a week.
Kind regards
1 Like
system
April 1, 2020, 9:45am
4
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
