nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Where can I find the explanation/definition of the different Jira Service Desk statuses?

CLAUDIA MARCELA MORENO BUITRAGO

Hello,

Please I would like to know where I can find the explanation/definition of the different Jira Service Desk statuses.

Declined

Waiting for support

Waiting for customer

Pending

Canceled

Escalated

Waiting for approval

Awaiting CAB approval

Planning

Awaiting implementation

Implementing

Peer review / change manager approval

Work in progress

Completed

Under investigation

Thank you!

Accepted answers

Dirk Ronsmans

Hi @CLAUDIA MARCELA MORENO BUITRAGO ,

I could list them for you how I see them but I'm assuming you need a standard explanation.

They are however how you fill them out yourselves and most are somewhat self explanatory.

- Completed: the task is "completed"

-Waiting for approval: well.. waiting to be approved..

On resource I could link you to tho would be the best practice documentation of Atlassian

https://confluence.atlassian.com/servicedeskserver041/best-practices-for-it-teams-using-jira-service-desk-969531331.html

The ones you list tho seem to be mainly from Problem and Change Management? Are you familiar with those ITIL processes?

All comments

Dirk Ronsmans

Hi @CLAUDIA MARCELA MORENO BUITRAGO ,

I could list them for you how I see them but I'm assuming you need a standard explanation.

They are however how you fill them out yourselves and most are somewhat self explanatory.

- Completed: the task is "completed"

-Waiting for approval: well.. waiting to be approved..

On resource I could link you to tho would be the best practice documentation of Atlassian

https://confluence.atlassian.com/servicedeskserver041/best-practices-for-it-teams-using-jira-service-desk-969531331.html

The ones you list tho seem to be mainly from Problem and Change Management? Are you familiar with those ITIL processes?

Guilhem Dupuy

Hello Claudia,

You can view the link between them by Viewing the Workflow :

Select a specific ticket by clicking on its ID or on its summary.
On the screen, clic on "View Workflow"

Capture d’écran 2020-09-16 à 11.47.41.png

This will display the link between the different status and will help you understand how they work.

Let me know if it helped you or not,

Guilhem

Nic Brough -Adaptavist-

You'll need to ask the people who designed the workflows you are using.

Some of these are distributed as part of the default workflows Jira provides (mostly intended as starting points) and they have names that have been designed to be self-explanatory. Your list has some that your admins have added, and they've also tried to use self-explanatory terms.

For example:

Waiting for customer - it means you are waiting for a customer to do something

Work in progress - someone is working on it

Declined - someone has said you won't be doing it

CLAUDIA MARCELA MORENO BUITRAGO

Hi Dirk,

Thanks for your reply.

What is the difference between "Waiting for support" and "Pending" statuses?

BR,

Claudia

CLAUDIA MARCELA MORENO BUITRAGO

Hi Nic,

Thanks for your reply.

What is the difference between "Waiting for support" and "Pending" statuses?

BR,

Claudia

Dirk Ronsmans

Hi @CLAUDIA MARCELA MORENO BUITRAGO ,

"Waiting for support" is normally used when the issue is already worked on and for example went in to "Waiting for Customer".

If the customer then replies the issue goes to "Waiting for support" so they know they have a reply and need to pick up the issue again.

This is different from "Open" which would signal that it was just created. So pretty much an intermediate step when the ticket goes to a customer for additional information and comes back to the "support".

"Pending" is different as it will ask you for a "pending reason" and these reasons could be lot of different things (and also customizable):

- pending supplier/delivery/order/change/...

often there is also a distinction between these 2 in SLA. "Waiting for customer" normally pauses the SLA as you cannot be penalized when the customer waits to answer, while a Pending state it continues to count as the Customer should not be impacted by an internal pending state (those should be calculated in to your SLA goals)

Hope this clarifies it a bit.

CLAUDIA MARCELA MORENO BUITRAGO

Hi Dirk,

Thank you for your support with regards to this topic.

As far as I understand:

Pending: Work has stopped on the issue because more details are needed from a third party.

Waiting for customer: The customer must provide more details about the issue.

In progress: The issue is being actively worked on at the moment by the assignee.

Waiting for support: The issue is already worked on but currently it is not being actively processed.

Is this correct?

BR,

Claudia

Nic Brough -Adaptavist-

That depends on what your admins might be intending them to mean. Probably worth looking at them in the context of the workflow using them.

My guess when I've seen them is that "waiting for support" is waiting for support to do something and move the issue along. Pending often means "pending something neither support nor the customer have control over" and probably should not be counted towards an SLA. "Pending next release of software" or "Pending legal team checks" for example.

Dirk Ronsmans

Hi @Nic Brough -Adaptavist- ,

I find it odd that you would not count a Pending 3rd party towards your SLA..

If support does not have control over what is "pending" or they did not agree on a proper SLA towards that supplier then it's poor SLM imho.

If this is pending something internal (change/release/..) then it might breach and that is also ok.. that way you can at least see why it took longer than you originally anticipated and adjust accordingly. Otherwise your legal team for example could take weeks to check and the customer is left holding the bag and waiting.

Then again there is always the discussion whether you "resolve" an incident when you move in the change or release management process or whether you keep the issue open till it has been implemented/released.

but that's a discussion that we can keep having till the end of days

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server