Loading...
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM

Ticket Reporting Datasets

What's on This Page:


Was this helpful?


The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!


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.

This feature is only available to Brand Administrators, CX Administrators, or users with Qualtrics Ticket Admin permission enabled.

Qtip: This feature moved ticket data mapping from the dashboard to the Follow Up page.

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.

Qtip: If you have used ticket reporting before, there will be at least one ticket reporting dataset to start.
  1. On the home page, click View all tickets.
    Ticket bar along top of projects page; there's a "view all tickets" link
  2. Click Tools.
    Once on ticketing page, open the Tools menu. Ticket reporting datasets is the fourth option
  3. Select Ticket Reporting Datasets.
  4. Click Add a dataset.
    Big tile-style button that has a plus sign in the middle and says "Add a dataset"
  5. By default, all available metadata fields and ticket data will be added. Add and remove fields as needed.
    Data mapper has a list of fields inside
  6. 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.
  7. When you’re finished, click Save.

Mapping Ticket Fields

See a list of all available metadata fields.

Qtip: Any edits you make to a field will not be reflected in other datasets where that field occurs. Edits are always dataset-exclusive.
  1. Click on the Add Field button.
    Add button bottom-left; on a field, its a space for a name, the field type, then the gray button for mapping that turns blue once a field is mapped
  2. Provide or update a Field Name for your field.
  3. 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).
  4. Click on the Not Mapped box, and choose the ticket data that will populate for this field.
  5. 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.

Icon like a hamburge for moving, X icon for deleting. Both show to left of a field when hovered over

Qtip: Removing fields from your mapper will affect all widgets using fields from that dataset. You will also affect which users are able to edit, use, or view those fields in that dataset. It will not affect the data saved with tickets themselves.

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.

Qtip: This works similarly to other data restrictions.
  1. Select Ticket Reporting Datasets.
    Inside ticketing page. Tools menu opened and ticket reporting datasets option highlighted
  2. Select a dataset.
    Datasets listed as tiles on the page
  3. Click Ticket Data Restrictions.
    Ticket Data Restrictions upper-right
  4. Click Add user or role.
    New window where you can add users and roles
  5. Type the name of the role or user, and select them.
  6. Click All Data.
  7. Click Add Restrictions.
    Another new window
  8. Select a field to restrict access by. This can be a default ticket field, like status or priority, or custom ticket data.
    Selecting ticket data fields
  9. 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.
  10. Select the value that must be matched.
    Allow rollup data is selected
  11. Select whether to allow rollup data. See linked page for details.
  12. Click Done.
  13. Click Done.
    Green buttons bottom-right corner
  14. 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.

Center of ticket data page, blue add data button

The user can then proceed to create a ticket reporting page and add widgets to it.

Qtip: If a ticketing dataset you were using is deleted, you’ll have the opportunity to choose a new dataset, and will once again see the “Get started” screen shown above. If the previous ticketing dataset is deleted, you will need to manually fix any widgets you added to ticket reporting pages so they match the new dataset.

Swapping Fieldsets and Editing Fieldsets

Buttons in upper-right of ticket data editor

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.

Removing Ticket Reporting Datasets

Warning: Once you delete a dataset, its restrictions and customization cannot be retrieved. Only delete a dataset if you’re absolutely sure that’s what you want to do. You cannot delete the Default dataset.
  1. On the home page, click View all tickets.
    Ticket bar along top of projects page; there's a "view all tickets" link
  2. Click Tools.
    Once on ticketing page, open the Tools menu. Ticket reporting datasets is the fourth option
  3. Select Ticket Reporting Datasets.
  4. Hover over a dataset and click x to delete it.
    X upper-right of a tile representing a ticket reporting dataset

Editing Existing Ticket Reporting Datasets

  1. On the home page, click View all tickets.
    Ticket bar along top of projects page; there's a "view all tickets" link
  2. Click Tools.
    Once on ticketing page, open the Tools menu. Ticket reporting datasets is the fourth option
  3. Select Ticket Reporting Datasets.
  4. Select a dataset. You will be able to edit mappings, restrictions, and other settings discussed on this page.
    Names of datasets