This is one of the standard workflows that comes with Jira Service Desk:
I'm trying to figure out why "Escalated" is included. What purpose does it serve? If it were removed, one could still go from "Waiting For Support" to "In Progress" in one hop rather than two.
Could someone provide me a use case where the inclusion of "Escalated" is necessary?
Workflow design often starts from the question "what reports do you need to be able to create?". (And before that, "how will this report improve what your organization does?")
So someone wanted to be able to run a JQL query to see which issues were blocked in some way. Or how many issues were moved into the Escalated status in a certain week (with the "was" or changed" operators)
A custom field could also have been used, as in the Flagged feature of Jira agile boards.
Thanks, Matt. In my company, we're planning on having Tier 1 and Tier 2 support. The general notion is that if the Tier 1 agent can completely resolve the customer's request on their own, then there's no need to disturb anyone at a Tier 2 level.
Might this be an example of why one would:
Curious on your thoughts.
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs