Filtering in the Ticketing App is not working. No clue how to solve this. Any ideas?
Maybe a Ticketing champion can help?
At development, we are unaware of any filtering issues in the ticketing application. Please add more details to your question so we can help you out.
Edit:
Some quick tips to debug situations like this.
It's important to know what exactly happens when filtering data.
- A filter is composed in the client application and is sent to the web API. This request can be seen by using the developer tools in the browser.
- In the web API this request is translated to a server API call (this can be a request message or a subscription). The web API has a connection towards SLNet for this (this can be seen by using the client test tool).
- SLNet receives the API call and processes it. I believe for a Cassandra system open tickets are stored in memory while closed tickets can only be read out from the database (note this will be different for tickets on Elastic which will be released in the near future).
- When the tickets are found a response traverses back to the client application.
By inspecting the API calls between any of these steps you should be able to determine where it goes wrong.
Is this ‘Severity’ you speak of a drop-down value? Does this also occur with a completely new ticket domain?
If nothing comes to mind, I suggest checking if the request and response to the web API is correct. You can also use the client test tool to verify if the messaging between the web API and SLNet is correct. Lastly, you can inspect if the tickets and their values are correctly saved in the database (this can also be done with the client test tool).
After some investigation it turned out this issue was fixed in 10.0.5 (RN24689), the fix will be merged to 10.0.0 (CU7).
Hello Sebastiaan
Locally on my DataMiner it also works fine, it’s a different system where filtering is not working. Whatever you select, the output is always no tickets. I was just looking for tips on where to check this.
DataMiner version: 10.0.0.0-9449-CU5
Current example, there are two tickets, one with severity low and one undefined. With filter all, both show; with either filter Low or Undefined, nothing is shown.