Skip to content

Bring open tickets over

This deployment has no sign-in configured: SP_CONFIG.clientId is empty.

Bring open tickets over

Sign in with your organization's Microsoft account to bring the tickets still open in your old helpdesk into the Ticket Tracker.

← Back to the queue

Bring open tickets over

Your account isn't assigned the Ticket.Editor role, so this page is closed to you. Only Editors create tickets.

Ask your administrator to assign Ticket.Editor to your account on the Ticket Tracker application, then sign out and back in: the role only appears on a new sign-in.

← Back to the queue

Dragonfly Technologies logo mark / Dragonfly Ticket Tracker Lite
← Back to the queue

Bring open tickets over

Moving from another helpdesk? Add the tickets still open there, one row per ticket. Each one gets a ticket number and a response clock worked out from when it was first received. Open tickets are brought over once: nothing here updates a ticket, and a row whose old ticket number is already on a ticket is skipped. Nothing is written until you have read the preview and clicked Import.

Paste an export or a copy of the open tickets from your old helpdesk and the rows below are filled in for you, ready to check and edit; nothing is written until you click Import. What you paste leaves your tenant for the duration of the request, together with the instructions the AI is given, which name this tracker's queue addresses and its severities and statuses, to an AI service Dragonfly runs in Azure. Strip credentials, and anything you would not send by email, before pasting. The Premium data-processing terms say exactly what is sent, kept and by whom.

Download the template, fill in one open ticket per row (the drop-downs hold this tracker's queues, severities and statuses), then choose the file here. Its rows are added to the form below, for you to check before anything is written. The file is read in this browser tab and is not uploaded anywhere.

✨ Filled by AI · check each row before you import

One row per ticket. Received is when the old helpdesk first got it, which sets the response clock. More holds the old ticket number and the description. You take ownership on the queue, as with any ticket.

Subject requiredRequester requiredQueue requiredSeverityStatusReceived requiredMoreRemove
Cancel, back to the queue
Advanced · tickets as JSON (Dragonfly staff)

{ "tickets": [ { "subject", "requester", "queue", "severity", "status", "received", "oldNumber", "description" } ] }. Check writes the form's rows here; Load puts JSON into the form.