Loading

Topics

Linked tasks and approvals

Who can use this feature?
EnterpriseEnterprise+

Visit our pricing page for more information.

Linked tasks and approvals let you hand off work from a ticket and keep the two connected. The ticket tracks their progress, and each one links back to the ticket.

Use them when someone outside the ticket has to decide or do something before you can resolve it. For example:

  • A manager approves a software seat or a hardware purchase.
  • A budget owner signs off on a vendor quote.
  • Another team ships a laptop or sets up an account.

They keep those handoffs inside the ticket instead of inside threads, so you can see what is waiting and on whom.

Which type to use

You can add two types to a ticket today: approvals and tasks.

Type

Use it when

What you set

Blocks the ticket?

Approval

Someone must say yes or no before you can continue

The approver (an Asana user, or invite one) and a due date. The requester is added automatically.

Yes

Task

Someone else has work to do, such as a team that uses Asana but not the service desk

Home project and section, title, description, assignee, due date, and collaborators

No

What blocks the ticket

Approvals block the ticket, and tasks don't. While an approval is pending, the ticket is On hold and its resolution SLA is paused. A task shows on the ticket but doesn't hold it. 

Create a linked task or approval from a ticket

Any agent can create a linked task or approval from the ticket's overflow (⋯) menu. Nothing is created until you review and confirm it.

  1. Open the ticket and choose the overflow menu.
  2. Pick the type: an approval or a task.
  3. Review the name and description. ASM pre-fills both with an AI summary of the ticket, and you can edit them.
  4. Set the details for that type: the approver and due date for an approval, or the project, assignee, and due date for a task.
  5. Create it. The new item links back to the ticket and shows under the ticket's Action items.

What the AI summary includes

The summary is built from the ticket's title, description, and comments. Private, queue-only comments are never included. The new item's description also carries a link to the source ticket, so the person who picks it up can find their way back.

Approvals

An approval pauses your ticket until the named approver decides, then sets the ticket back to Open. If approval is removed and deleted, the ticket is back to in progress, and SLAs unpause.

Set up an approval

Every approval needs one named approver, and that approver must have an Asana account.

  1. Search for the approver by name. If they aren't in Asana yet, invite them from the same field.
  2. Set a due date.
  3. Review the AI summary, edit it if needed, and create the approval.

The requester is not added to the approval automatically but can be added manually if desired. Approving by email, Slack, or Teams without an Asana account is not available yet.

What the approver sees and can do

The approver sees the approval, including the AI summary you reviewed, but not the ticket. They can approve or reject, and comment on the approval. They can also change the approver or due date, add collaborators, add dependencies, and create subtasks. They can't delete the approval.

Nothing the approver does is copied to the ticket. Comments stay on the approval, and only the approval's state affects the ticket.

What happens to the ticket

The ticket status and SLA follow the approval, so you don't have to update them by hand.

What happens

Ticket status

Resolution SLA

You create the approval

On hold

Paused

The approval is pending

Stays On hold

Paused

The approver approves or rejects

Open

Resumes

Service AI also comments on the ticket to tell the requester the request needs a sign-off and who it was sent to, so they know where it stands. The message links to the approval, and they can open it if they have access.

When an approval is rejected

The ticket goes back to Open. It is not closed. You decide what happens next: submit a new approval, close the ticket, or escalate.

The requester is on the approval, so they can see the rejection and reply there with justification.

Tasks

A task hands work to someone in a project of their own, and it doesn't hold the ticket. You set its home project and section, title, description, assignee, due date, and collaborators. The assignee works on it in Asana like any other task. A task doesn't change the ticket's status or SLA.

Who can see what

Approvals are visible to every member of the ticket's queue, and you can make one private. An approver doesn't see the ticket unless they are added to it.

Person

Sees the approval

Sees the ticket

Ticket assignee

Yes

Yes

Approver

Yes

Only if added as a ticket collaborator

Requester

Not added by default but can be added

Conversation history only, not operating details

Other members of the queue

Yes, unless it is private

Yes

Ticket collaborator outside the queue

Must request access

Yes

If an approver needs more context than the summary gives, add them as a ticket collaborator. Tickets can hold personal data, so check what is on the ticket first.

Private approvals

A private approval is hidden from other queue members. They still see it in the ticket's Action items as a private approval, and it still blocks the ticket.

When you move a ticket to another queue

The old and new assignees keep access to both the approval and the ticket, because they are added as collaborators. The approver keeps access to the approval. Members of the old queue lose access to the approval's details but can still see its status from the icon, and they lose ticket access unless they are collaborators. Members of the new queue get access to both.

Questions and current limits

Can an approver approve from email, Slack, or Teams?

Not yet. In this release, the approver acts in Asana, so they need an Asana account. You can invite them from the approver field.

Can an approver see my ticket?

Not unless you add them to it. Comments and activity on the approval aren't copied to the ticket.

Can I link a ticket to another ticket?

Not yet. You can link approvals and tasks.

Does a rejection close the ticket?

No. The ticket goes back to Open, and you decide what happens next.

Which items block the ticket?

Approvals do, and they pause the resolution SLA. Tasks don't.

Do tasks change the ticket's status or SLA?

No. A task is tracked on the ticket but doesn't block it.

Will the requester see the approval? Requesters see a message on the ticket from Service AI that an approval was requested, with a link to the approval task. They can open the task if they have access to it.

Who can create linked tasks and approvals?

Every agent can create linked tasks and approvals from the ticket's overflow menu.

 

Loading
Linked tasks and approvals | Asana Help Center