Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

What does "ESCALATED" and "PENDING" statuses mean in the standard Jira Service Desk Worklow?

JConstantine August 27, 2020

Here's the standard Jira Service Desk Workflow for the Support issue type:

Workflow.pngWhat does the statutes "ESCALATED" and "PENDING" mean in this workflow? In what particular cases we might need them? What does it mean "to escalate the issue" in general?

1 answer

1 accepted

1 vote
Answer accepted
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 27, 2020

Escalating an issue usually means to bring more attention to it.  There are a couple of different ways this could be used.  You could use it to:

  1. If you have a process to quickly address issues you can escalate it so agents know it needs immediate attention.  
  2. The status can be used to also apply a different SLA
  3. If you are using a tiered service desk with different agent levels you can escalate the issue to your tier two support.

Those are just a few examples.  In regards to pending you can use this when:

  1. You are waiting on the customer
  2. Need information from a vendor
  3. Need to pause an SLA

These are just a few examples of what pending can be used for.  It all comes down to your process.

JConstantine August 27, 2020

@Brant Schroeder Crystal clear! Thank you! Where can I divide my Service Desk into tiers btw?

Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 27, 2020

We have created tiers in our own processes.  We run the following:

  • Tier 0 - Self help through knowledge base (Confluence)
  • Tier 1 - Service Desk Team member with Service Desk License.  We do total ownership were the tier 1 support representative is responsible for seeing the issue all the way through to closure.
  • Tier 2 & 3 - Service Desk Team member with Jira License.  This individual can see the issue and comment on the issue but only internally.  This helps protect our tier 2 & 3 resources and allows them to focus on their projects and daily operational work.  This is a application developer, system admin, etc.  They are added as watchers on the issues and tagged in internal comments.

It really depends on how you would like to set it up and how your process works.

Erik Vanderstraeten February 22, 2021

@Brant Schroeder ,
What happens if your tier 2 & 3 needs extra information from the customer?

  • Will they ask it to the tier 1 service desk agent, who will then ask the customer?
  • Or are they added as Request Participant by default and can they contact the customer directly (via the portal)?
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2021

@Erik Vanderstraeten 

Depends on the area and the SLAs in place.  Some of the Tier 2 & 3 we have provided agent access to so they can communicate directly with the customer.  Others go directly through the Tier 1 agent.

Erik Vanderstraeten February 23, 2021

Thanks!
Note: We're working out our set-up here and are struggling with a good set-up that is efficient to work with, but also not paying for agent licenses when it's not needed.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events