Summary
When searching in Customer Portal, modifying/deleting a previous keyword does not auto populate search results.
Environment
- Issue occurs in Firefox, Safari and Chrome, though the replication steps are slightly different. The issue is most obvious in Chrome.
Steps to Reproduce
- Create a JSD project
- Link a Confluence space to the project in project settings and make sure customers can access space/project.
- Visit the customer portal page to your project and type in a search word. Notice that as you type, there is a spinning circle to indicate that the system is searching.
- Once the search results auto populate, backspace to delete the word.
- Begin typing in a new search word. If the search auto populates, complete steps 3-5 again, until you find that nothing populates or happens when you type in search words.
Expected Results
When typing in a search word in the customer portal, articles should auto populate or a message saying “No solutions found.” should appear (if nothing matches the search). The below screenshot shows an example of a search for a keyword that does not exist in the KB:
If I delete the word MacBook, and try typing in a new search term, the portal should begin to auto populate responses to my new search term.
Actual Results
The first search works, however if you delete and try typing in a new word, nothing will populate. An example of this can be seen in the following screenshot:
Depending upon which browser you’re using, you may need to delete and re-add keywords multiple times to replicate. In Chrome it happens typically after one time. In Safari and Firefox it can take up to 4 or 5 times of typing in a keyword, deleting, and adding a new word.
Nothing is apparent in the logs, aside from the following:
Development console does not show anything either:
Workaround
The current workaround is to completely reload the customer portal page and re-initiate a search.
Bug
Low
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center