Body
Who can use this feature?
- Available in Work Management (TDNext) Ticketing applications
- License Requirement: Technician or higher
- Application Access: User must have access to Work Management and the specific Ticketing application
- Application-level Security Role: User's security role in the Ticketing application must include one of the following:
- Edit All Tickets (to assign or unassign any ticket)
- Edit Tickets for Which They Are Primarily Responsible (to reassign tickets you own)
- Users who are the Reviewer on a ticket or are primarily assigned to the ticket may also assign or unassign it without additional permissions.
Ticket assignment determines who is responsible for completing the work on a ticket. A ticket can be assigned to a group, an individual, both a group and an individual, or left unassigned. Responsibility can be changed at any time throughout the ticket lifecycle.
Understanding how assignment works helps ensure the right people are working on the right issues and that tickets don't fall through the cracks.
In this article, we'll cover:
Tickets can be assigned in several ways to ensure the right people are working on the right issues:
Group Assignment: Tickets assigned to a group are visible to all group members. This is useful when:
- Multiple technicians have the expertise to handle the request
- You want to distribute work among team members
- The specific technician isn't yet determined
- You're routing tickets to a specialized team (e.g., Network Team, Dashboard Support)
Individual Assignment: Tickets assigned to a specific person indicate that the individual is the primary responsible party. This is useful when:
- A specific technician has the expertise or context needed
- You're escalating to a subject matter expert
- Accountability needs to be clearly established
Combined Assignment: A ticket can be assigned to both a group and an individual. The individual is the primary responsible party, while the group assignment maintains visibility for the team.
Unassigned: Tickets can remain unassigned in a queue until a technician takes responsibility for them.
Best practice: Tickets should be assigned to the owning group and remain with that group throughout the ticket lifecycle, even when assigned to individuals within that group.
When you view a ticket's details, the Responsibility field shows who is assigned to the ticket. Depending on how the ticket was assigned, this field may show only a person, only a group, or both. For example, if a ticket comes in unassigned and a technician assigns themselves directly, only that person's name will appear. If a ticket is assigned to a group and a group member takes it, both the group and the individual will be listed.
Two related concepts are worth understanding:
- Primary Responsibility refers specifically to the person or group assigned to the ticket record itself. Filtering or reporting by primary responsibility returns only tickets where that resource is the designated owner of the ticket.
- Responsibility (broader) includes anyone who is either primarily responsible for the ticket or assigned to an active task on the ticket. An active ticket task is one that is not blocked by an incomplete predecessor. Filtering by responsibility returns both the ticket owner and anyone assigned to the ticket's active tasks.
The Reviewer is a user who can be notified about ticket activity but is not directly responsible for completing the work. Some ticket types automatically assign a Reviewer. Reviewers also have permission to assign or unassign the ticket.

On any ticket, the Actions menu (located below the navigation tabs on the ticket details page) provides access to the following assignment options. Note that the labels for these actions update dynamically based on the ticket's current classification (for example, "Take Incident" or "Assign Change Request").
- Add to My Work adds the ticket to your My Work list. This option appears only when the ticket is assigned to you or to a group you belong to, and the ticket is not complete or canceled.
- Take [ticket classification] assigns the ticket to you as the primary responsible person. This option appears only when the ticket is assigned to a group you are a member of.
- Assign [ticket classification] / Reassign [ticket classification] allows you to assign or change responsibility for a ticket to any person or group — including yourself if Take is not available. When reassigning, you can add a comment and choose whether to notify the newly responsible party by email.
- Unassign [ticket classification] removes all responsible persons and groups, leaving the ticket unassigned.
Unassigning a ticket can cause it to be overlooked. The best practice is to reassign rather than unassign tickets whenever possible.

To assign or reassign a ticket:
- In Work Management, click View Applications.
- Click the desired Ticketing application.
- Click Search in the left navigation.
- If necessary, modify the search criteria and click Apply.
- Click the ticket title to open the ticket details.
- Click the Actions menu.
- Select Assign [ticket classification] or Reassign [ticket classification].
- In the New Responsibility field, start typing a name or group name, or click the magnifying glass to search.
- By default, the newly assigned resource will receive an email notification. Uncheck the Notify the new resource of the assignment box if you do not want to send a notification.
- Enter any comments about the assignment. These will be included in the notification email and saved to the ticket Feed.
- Click Save.
If the ticket is assigned to your group but not to you individually, “Taking” the ticket will assign it to you specifically, and the group will remain in the Responsibility field.
To take ownership of a ticket:
- In Work Management, open the ticket details in the appropriate Ticketing application.
- Click Actions > Take [ticket classification].
- Confirm that you want to take responsibility.
The ticket will now appear in the "Assigned to Me" ticket search.
To mark a ticket as unassigned:
⚠️ Leaving a ticket unassigned increases the risk of it being overlooked. Reassigning is strongly preferred.
- In Work Management, open the ticket details in the appropriate Ticketing application.
- Click Actions > Unassign [ticket classification].
- Confirm that you want to remove the responsible resource(s) from the ticket.
The Add to My Work action appears only when the ticket is assigned to you or to a group you belong to, and the ticket is not complete or canceled.
When you add a ticket to My Work, it appears in your My Work list alongside other assignments. If the ticket is assigned to your group but not to you individually, adding it to My Work will assign it to you specifically — the group will remain in the Responsibility field as well.
To add a ticket to My Work:
- In Work Management, open the ticket details in the appropriate Ticketing application.
- Click Actions > Add to My Work
The ticket will now appear in your My Work list.
See Getting Started with My Work for more details.
If you are a workspace member, you can add a ticket directly from the Action menu to help manage your work with your team.
- In Work Management, open the ticket you want to add to the workspace.
- In the Actions menu, select Add to Workspace.
- Choose the appropriate workspace and click Save.
See the Workspaces Overview for more details.
When a ticket is assigned to a group (or to a group and a person), and you reassign it to a new individual, the system checks whether that person is a member of the ticket's current group before updating the assignment:
- If the new person is a member of the current group, the group assignment remains on the ticket.
- If they are not a member of the current group, the ticket will be assigned to that person's Primary Group along with the individual.
- If they are not a member of the current group and have no Primary Group, the ticket will be assigned directly to them, and the previous group assignment will be removed.
Note: Deactivated groups are not considered in this process. If an individual's Primary Group has been deactivated, the system treats them as having no Primary Group.