Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×When a customer creates a ticket via the portal, they don't appear in the "incidentmanager" queue, even when we refresh the page.
Afer a while, the ticket does appear, but the SLA is allready breached, as if the timer did start directly after creation of the ticket.
Because of this lag / delay, we breache the SLA a lot.
Does somebody know how the delay arises and how we can avoid the SLA breaches?
What type of. request s raised and what is the queue's filter set to.
Could there be a mismatch
Are there any automation rules running on issue created, may they change options so that the issue will appear in the queue?
Do those automations take up a certain amount of time, if so overlook the automation and see how to improve, or split the automations
All issuetypes that we use (change, servicerequest and incident). The queue is the incidentmanager, so where all new tickets will appear before a agent takes it in to progress.
There are no automations up on creating a ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the record: sometimes the ticket appears immediately, but sometimes not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you check the jql for the queue and make sure that the created issue match this jql
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes they do. All new tickets appear in the incidentmanager queue, but sometimes there is a lag and new tickets appear hours after creation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.