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:
They keep those handoffs inside the ticket instead of inside threads, so you can see what is waiting and on whom.
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 |
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.
Any agent can create a linked task or approval from the ticket's overflow (⋯) menu. Nothing is created until you review and confirm it.
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.
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.
Every approval needs one named approver, and that approver must have an Asana account.
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.
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.
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.
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.
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.
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.
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.
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.
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.

These cookies are strictly necessary to provide you with certain features. For example, these cookies allow you to access secure areas that require registration and set your privacy preferences. Because these cookies are essential to providing services to you, they cannot be disabled. You can set your browser to block or alert you about these cookies, but it may cause some parts of the site to not work.
Third party trackers collect information used for analytics and to personalize your experience with targeted ads. Under the Virginia Consumer Data Protection Act, you have the right to opt-out of the sale of your personal data to third parties. You also have the right to opt out of targeted advertising related processing. You may exercise your right to opt out of the sale of personal data and targeted advertising by using this toggle. If you opt out, we will not be able to offer you personalized ads and we will stop sharing your personal information with third parties. For more information please see our Privacy Statement.
These cookies allow us or our third-party analytics providers to collect information and statistics on use of our services by you and other visitors. This information helps us to improve our services and products for the benefit of you and others.
These cookies, provided by our third-party advertising partners, collect information about your browsing habits, as well as your preferences for various features and services. They also provide us with auditing, research, and reporting to know when advertising content has been displayed and how successful the content has been. This information allows us and our third-party advertising providers to display relevant advertising content.
These cookies provide enhanced functionality, providing chat support, allowing you to more easily complete forms, personalizing content to your preferences, and selecting your communications preferences. If you do not enable these cookies, or choose to disable them in the future, that could impact your ability to use certain features.