Performing bulk actions or single row actions in Ticket Console
Permissions required to perform bulk actions or single row actions
You need the following permissions to perform bulk actions or single row actions. For more information about roles and permissions, see Roles-and-permissions.
Ticket type | Permission | Bulk actions | Single row actions | ||||
---|---|---|---|---|---|---|---|
Flag / Unflag | Change assignment | Update status | Flag / Unflag | Edit | Assign to me | ||
Incident | Incident Master / User | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ |
Change | Change Master / User | ❌️ | ✅️ | ✅️ | ❌️ | ✅️ | ✅️ |
Problem / Known error | Problem Master / User | ❌️ | ✅️ | ✅️ | ❌️ | ✅️ | ✅️ |
Release | Release Master / User | ❌️ | ✅️ | ❌️ | ❌️ | ❌️ | ✅️ |
Work order | Work order Master / User | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ |
Task | Task User / Administrator / Manager | ❌️ | ✅️ | ❌️ | ❌️ | ❌️ | ✅️ |
Task | User with Master or User permission to the associated ticket | ❌️ | ✅️ | ❌️ | ❌️ | ❌️ | ✅️ |
Activity | Release Master, Release User, or Activity User | ❌️ | ✅️ | ❌️ | ❌️ | ❌️ | ✅️ |
To perform bulk actions on tickets
Perform actions on multiple tickets, such as Flag, Unflag, Follow, and Unfollow, at one time. By default, bulk actions can be performed on a maximum of 50 tickets, except for Open in new tab, Relate tickets, and Relate assets, which have a maximum of 10 tickets. To check the permissions you need to do bulk actions, see Permission required to perform bulk actions.
- Open the ticket console.
- Select multiple tickets for bulk action.
Perform one of the following actions on the selected tickets:
Bulk action
Description
Follow
Follow multiple tickets to monitor the activities or updates on them.
Unfollow
Stop following multiple tickets.
Flag
Prioritize multiple tickets by flagging them. You can flag only Incidents or Work orders.
Unflag
Unflag any tickets that are no longer a priority.
Assign
Assign multiple tickets to the assignee.
Update status
Perform bulk status updates for the following ticket types:
- Incident
- Problem Investigation
- Known error
- Change
- Work order
You can update the status of multiple tickets in bulk if the tickets meet the following requirements:
- The tickets must be of the same ticket type. For example, all the tickets are incidents.
- The tickets could have similar status or different status.
- Change request tickets must have similar status and must follow the same process flow.
In the following scenarios, the Update Status link is unavailable, and you cannot update the status of the selected tickets:
- Change requests are undergoing review. For example, the tickets are in the Request for Authorization or Request for Change status.
- All or one of the selected tickets is in the Closed status.
When you select multiple tickets for status update, some of the details of the first ticket are copied to the remaining tickets. For example, if you select multiple incidents, the resolution categorization, and product categorization details of the first incident are prepopulated in the remaining incidents.
Important:
- When you update the status of a problem investigation to Complete and Status reason to Known Error, you need to manually create a known error and relate it to the problem investigation.
- Make sure the assignment details in a problem investigation are updated before you update the status of problem investigations to Assigned.
Relate tickets
Perform bulk relate tickets for the following ticket types:
- Incident
- Problem Investigation
- Known error
- Change
- Work order
- Release
You can create relationships for multiple tickets in bulk. The selected tickets must be of the same ticket type. For example, all the selected tickets are incidents.
You can relate one ticket to many tickets, you can relate multiple tickets to one ticket, or you can relate more than one ticket to multiple tickets by using this bulk action.In the following scenarios, the Relate tickets link is unavailable, and you cannot relate the selected tickets:
- All or one of the selected tickets is either a service request, or Activity, or Task.
- Tickets selected are of more than one ticket type.
In the following scenarios, you get a error message, when you try to bulk relate tickets:
- When you select multiple tickets in the ticket console and in the Relate tickets window, and then select any of the previously selected tickets in the ticket console, you get an error as the relationship cannot be created to the same ticket.
For example, you select CRQ001, CRQ002, and CRQ003 in the ticket console and click Relate tickets link. In the Relate tickets window, you search and select CRQ004, CRQ005, and CRQ002. You select the relationship type and save the ticket. You get the following error, as CRQ002 is selected twice:
Both the instance IDs or both the request IDs can't be same while creating the relationship. (51135) - If one of the selected change tickets is pending for approval, you get the following error:
Error (222375) One or more of the change requests selected is pending for approval. Please deselect such change requests to proceed further.
Important:
- If you have only submitter or viewer permission, you will not be able to relate the ticket.
- If you do not have the relevant permissions to view a ticket in the ticket console, you will not be able to relate the ticket.
Relate assets
Perform bulk relate assets for the following ticket types:
- Incident
- Problem Investigation
- Known error
- Change
- Work order
- Release
- Task
You can create relationships to assets in bulk. The selected tickets must be of the same ticket type. For example, all the selected tickets are incidents.
You can relate one ticket to many assets, you can relate multiple tickets to one asset, or you can relate more than one ticket to multiple assets by using this bulk action. You can search multiple configuration items (CI) at the same time by entering comma-separated CI names in the search box.
While searching for CIs, you must enter at least three characters in the search box to find matching results.Based on the requirement, you can select all CIs listed in all pages of the search result.
In the following scenarios, the Relate assets link is unavailable, and you cannot relate the selected tickets:
- All or one of the selected tickets is either a service request, or Activity.
- Tickets selected are of more than one ticket type.
Important:
- If you have only submitter or viewer permission, you will not be able to relate the ticket.
- If you do not have the relevant permissions to view a ticket in the ticket console, you will not be able to relate the ticket to assets.
Open in new tab
Open multiple tickets in new tabs to view their details.
To perform an action on a single row
You perform actions on a single row of the ticket console. To check the permissions you need to do single row actions, see Permission required to perform bulk actions.
- Open the ticket console.
- Select a record in the grid.
- Click
.
Perform one of the following action on the ticket:
Single row action
Description
Flag
You can prioritize the ticket by flagging it. You can flag only Incidents or Work orders.
Unflag
If you don't need to prioritize the ticket unflag.
Assign to me
Assign the ticket to yourself.
Edit
When you click Edit, the ticket opens in edit mode on a particular PWA screen, such as incident, problem, or change. You can edit the details of the ticket and save it.
Permission to edit a ticket is confirmed by the application when the ticket opens in an edit window.
To assign tickets
You can assign a single ticket or multiple tickets manually, by auto-assignment, or to yourself.
- Select tickets that you want to assign.
Click Assign
.
If you select multiple tickets to be assigned to a support group, the company of the ticket that you select first is always selected as the support company.- Select values from Support Organization, and Support Group.
You can select Auto-assign to the best fit group, which assigns the assignee automatically, based on the configuration, or you can select Assign to me, which assigns the ticket to yourself. - Select assignee and click Assign.
Instructions for classic interfaces