Skip to the page

DocsSupport desk

DocsSupport desk

Turn a ticket into a task

Create a task from a support ticket or link an existing one, and hear when the work is done.

Team plan and above

Some tickets need work, not only an answer: a bug to fix, a setting to change. From the ticket you can create a task in a project, or link a task that already exists, so the support side and the delivery side stay joined without copying a customer’s details into the project.

Anyone who can open the ticket can do this, including a member it’s assigned to who isn’t on the support desk.

Create a task from a ticket#

  1. Open the ticket and find the Linked tasks card.
  2. Choose Create dev task.
  3. Check the Project. It defaults to the project chosen under Dev tasks go to in the support portal settings of the ticket’s project, or to the ticket’s own project if none is chosen.
  4. Pick an Outcome if the task belongs to one. It’s optional.
  5. Edit the Title if you want to. It starts as the ticket’s key and subject, such as [SUP-0042] CSV export is greyed out.
  6. Choose Create task.

The task starts in Backlog, unassigned. Invite someone to it from the project as usual. See Tasks.

What carries over#

Only the title, and a description holding the ticket’s key and a link back to the ticket. Nothing the customer wrote is copied, and neither is their name, email or company.

That’s deliberate. Whoever picks up the task may not be able to see support tickets, so add the technical detail they need to the task yourself.

If the project is connected to a GitHub repository, the new task follows that project’s sync and gets an issue there. See GitHub.

  1. On the Linked tasks card, choose Link existing task.
  2. Search by task key for an exact match, or by words in the title or description. Tasks from any project you can see are offered.
  3. Choose the task.

One task can serve several tickets, and a ticket can have several tasks. That suits a bug reported by five customers: five tickets, one task.

How the two stay linked#

  • On the ticket, Linked tasks lists each task with its key, title, assignee, project and current status. Choose one to open it.
  • On the task, Linked tickets lists the ticket keys. Each is a link if you’re able to open that ticket, and plain text if you aren’t.
  • Creating, linking and unlinking each leave an internal note on the ticket saying who did it.

To unlink a task, choose the × beside it on the Linked tasks card. Both sides let go, and the task itself is untouched.

If a linked task is deleted, it comes off the ticket with a note saying so. Restoring the task doesn’t bring the link back, so link it again.

When a linked task is done#

When a linked task moves to Done, by hand or because its GitHub issue was closed or its pull request merged, each ticket it’s linked to gets an internal note:

“BMS-038 is done — let the customer know?”

The ticket’s assignee is told by email, in the bell and on My Work, unless they finished the task themselves.

Nothing else happens. The ticket’s status doesn’t change and nothing is sent to the customer. The note has a Reply to customer button, which switches the reply box to a public reply ready for you to write. Whether to email it is still your choice. See The inbox and tickets.

What the customer sees#

Nothing about tasks. Linked tasks, their status, and the notes about linking and finishing are all internal. The customer hears the work is done when someone on your team tells them.

    Type to search every page. ↑ ↓ to move, Enter to open.