About Ticket Reporting Datasets
Ticket reporting datasets are the ticket fields you can report on in your dashboards; this includes information like status, ticket owner, priority, and so on, but it also includes various ticket data.
Based on your organization’s needs, you can make multiple, separate ticket reporting datasets. This is so you can separate ticket data by the different programs or teams working out of your Qualtrics brand. Limit the number of fields each team has to navigate through, and restrict a user’s access to data based on the program they belong to.
Creating Ticket Reporting Datasets
Before you can set up ticket reporting, you must create a ticket reporting dataset.
Ticketing data starts being recorded the moment the first dataset is created, meaning that when this is mapped to a dashboard, the data starts on the date of dataset creation.
- Go to Tickets.
- Click Tools.
- Select Ticket Reporting Datasets.
- Click Add a dataset.
- By default, all available metadata fields and ticket data will be added. Add and remove fields as needed.
- When you have configured your fields, make sure you add Ticket Data Restrictions. This determines who has access to a given Ticket Reporting Dataset.
Qtip: See the Ticket Data Restrictions section for more detailed steps.
- When you’re finished, click Save.
Mapping Ticket Fields
See a list of all available metadata fields.
- Click on the Add Field button.
- Provide or update a Field Name for your field.
- Select the Field Type.
Qtip: Field types define the type of data mapped into the field and consequently determine which widgets will be available for each field. If you don’t see your desired Field Name when selecting the source of a widget, you may need to change the field type or use a different widget. Be aware that changing Field Types can break widgets on any Dashboard using the affected fields. As such, we often recommend adding a new field that maps to the same question rather than editing the Field Type or Field Mapping of existing Fields (e.g., you may have a Text Set field for a NPS group as well as a separate Number Set field for a NPS value).
- Click on the Not Mapped box, and choose the ticket data that will populate for this field.
- Click on the Save button at the bottom right.
Moving and Removing Fields
Hover over a field. The move icon to the left can be used to drag and drop the field around the mapper. The delete icon ( X ) can be used to remove the field from the ticket reporting dataset.
Recoding Ticket Data
If the values of your ticketing fields don’t look correct – for example, labels being misspelled or wrongly capitalized on the dashboard, or numeric values not aligning as expected – you can recode them. To do so, open a ticket reporting data set, find the field that you want to recode, and click the arrow to open the recode editor. Note that not all fields can be recoded.
In the Recode Editor window that opens, specify the fields and their values. On the left, under Label, include the value as it currently appears in the ticket data (i.e., on the dashboard). On the right, under Recode, enter what you want to correct the value to.
Recoding ticket fields works similarly to recoding fields in the Dashboard Data tab.
Ticket Data Field Types
Field types help you define the format of the data so the dashboard knows what widgets it can be added to. Field types for ticket data are similar to the field types for other dashboard data, but with a few key differences.
- Date Calculation: Create custom fields that allow you to measure the time between different ticket statuses. See Time Between Ticket Statuses for more details. Anything you create here will generally have the same widget compatibilities as regular date fields.
- Drill Down: Nests multiple text set fields to allow you to drill into multiple levels of data. Corresponds to drill down field groups in the dashboard data editor.
- Field Group: A group of numeric values or number sets with the same scale. Corresponds to measure groups in the dashboard data editor.
- No Multi-Answer Text Set option.
You can consult the Field Type & Widget Compatibility Table when deciding what widgets to build with the data available.
Ticket Data Restrictions
By default, all users and roles have access to all ticket reporting data. However, you can create ticket data restrictions to limit access to this data.
- Select Ticket Reporting Datasets.
- Select a dataset.
- Click Ticket Data Restrictions.
- Click Add user or role.
- Type the name of the role or user, and select them.
- Click All Data.
- Click Add Restrictions.
- Select a field to restrict access by. This can be a default ticket field, like status or priority, or custom ticket data.
- Choose between the following:
- Is: Enter a static value the ticket field has to match.
- Matches user attribute: Determine a User Attribute that the ticket field has to match. This is best for values that vary by user.
- Select the value that must be matched.
- Select whether to allow rollup data. See linked page for details.
- Click Done.
- Click Done.
- Click Save.
Using Ticket Reporting Datasets in Dashboards
Once ticket reporting datasets have been assigned to a user, they can go to the Ticket Data section of the dashboard settings to select the dataset they’d like to use in their dashboard. Click Add data to get started.
Swapping Datasets and Editing Datasets
Once you’ve selected a data set, you’ll be able to see the list of fields, but not edit them. To edit fields, use the pencil icon in the upper-right. You’ll be taken to the dataset editor on the Follow Up page.
To switch your dashboard to a different ticketing dataset, use the swap icon to the left of the edit button.