Infos:
Used Zammad version: 3.1.0 (latest version)
Used Zammad installation source: source
Operating system: Ubuntu 18.04
Browser + version: all
We have created a few KB entries and set them to internal for visibility.
From the KB entry, I can link a ticket.
But if i want to link a KB entry from a ticket in the request answer field, the search symbol appears briefly and nothing happens after that.
If I enter only one keyword and press ENTER, at the top “no such object” appears .
I have already set the visibility to public, but that was’nt the trick.
Do we have to start an idexing or anything else?
thx for help
Andreas
Normally the searchindex will be updated automatically.
If this issue appears since updating from 3.0.x to 3.1.x, please rebuild your index with:
rake searchindex:rebuild
If this is a fresh install, you might want to ensure that your background jobs are fine:
rails r 'p Delayed::Job.count < this should be near to 0!
If rebuilding fails, ensure your elasticsearch service is working.
that doesn’t fix the problem. Index rebuild looks like this
if we use ?? in the Ticket, then KB-entry will be displayed.
However, if we try to search for “related answers” on the right side, no result is displayed.
Incidentally, we have updated directly from 2.9.0 to 3.1.0.
Hey Andreas,
thank you very much for clarifying the problem!
I’m afraid, you found a bug!
I already filled a bug report for you.
Let’s hope for a soonish fix
opened 02:24PM - 23 Aug 19 UTC
closed 07:50AM - 30 Oct 19 UTC
duplicate
<!--
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
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: latest Google Chrome, latest Firefox
* This bug has originally found by the user `bendergruppe` on the Community: https://community.zammad.org/t/find-knowledge-base-entry-from-ticket/2973
### Expected behavior:
When linking an KB-Answer to a ticket (from ticket to answer), you can search for your answer and then simply link it.
### Actual behavior:
When linking an KB-Answer to a ticket (from ticket to answer), the UI does not provide a selection for found answers. Logfile and developer console clearly show that there have been results, they "simply" don't show up within the UI.
### Steps to reproduce the behavior:
* create an knowledgebase answer
* ensure your searchindex is up to date
* go to any ticket (if none is available, create one)
* now try to link an answer to the ticket, by searching for a word that appears within the KB-Answer
### Screencast:

Yes I'm sure this is a bug and no feature request or a general question.
1 Like
Hey @bendergruppe ! I just wanted to let you know that we found and fixed the issue via https://github.com/zammad/zammad/commit/d4afb0e8679cff6f343d574527aaeb0c75668627
We won’t do a stable backport but we will release a new stable version soon.
1 Like
system
Closed
February 27, 2020, 7:52am
6
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.