Escalate a ticket to development
Turn a service desk ticket into a bug or a story in an agile board, and get notified when the solution is ready.
When a service ticket is actually a product defect or an improvement request, the agent can escalate it to the development team. Elion ITSM creates a bug or a story in the agile board you choose, links the two and, when the item is done or released, notifies the original ticket.
Before you start
The ticket must be in a service desk and can't be resolved, closed or cancelled.
You must be able to work the ticket (handle it, not just see it).
You must be a Lead, Member or QA of at least one agile board. Only those desks are offered as a destination.
Steps
Open the service ticket's page.
Find the Development section and press Escalate to development.
Fill in the form:
Development desk: the agile board that receives the item.
Create as: Bug (defect) or Story (improvement). For an incident Bug (defect) is selected by default; for the rest, Story (improvement).
Title and Description: they are copied from the ticket. Adjust them for the development team; if the requester wrote the description, it stays marked as such in the item.
Attachments: check Copy attachment on each file you want to pass on. Only attachments from public messages are offered, never those from internal notes.
Put this ticket on hold for development (vendor): it comes checked. Uncheck it if the ticket should stay open in the meantime.
Press Escalate.
Before escalating, leave in the ticket the steps to reproduce the problem, screenshots and the version the customer uses. It saves the development team questions.
What happens next
You see the notice Escalated as with the new item's number and its desk.
The item is created in the agile board and an internal note is left on each side with the link to the other.
If you left the checkbox checked, the ticket goes on hold for the vendor (development).
In the ticket's Development section, the item appears with its desk, its status and, once it has them, its sprint and its release.
On the agile board, the item's card has the Escalated badge, and its page shows Escalated from with the ticket number.
Notifications back
The service ticket gets an automatic note at two moments:
When the item reaches Done: Item (number) from desk (key) is done.
When the release that includes it is released: Item (number) was released in version (name).
With the second notice, the agent knows the solution is already in production and can close the loop with the requester.
If the ticket is already closed or cancelled when the notice arrives, nothing is added.