Skip to main content

Configurable Ticket Table Column Sets

A
Written by Amer Shalan
Updated over 2 months ago

Column sets help users streamline their workflow by ensuring the right ticket table columns are available in the right place. By pre-configuring column sets, users save time when drilling into tickets and conducting support ticket research.

Creating and Managing Column Sets

As a Qvasa admin, you can create and manage column sets on the Tickets Table Configurations page.

Adding a New Column Set

  1. Navigate to the Tickets Table Configurations page.

  2. Enter a name for the new column set.

Click Add New Column Set.

Editing a Column Set

Once a column set is created, it appears in the table. Clicking the edit (pencil) icon opens a lightbox where you can:

  • Rename the column set.

  • Set it as the account default column set.

  • Configure the desired columns.

The account default column set applies to dashboards that do not have a custom column set assigned. When users utilize the Inspect feature, this is the default column set they will see.

Applying Column Sets to Dashboards

In a dynamic dashboard (in edit mode), there is a gear icon in the top bar that allows users to edit dashboard attributes.

Example Screenshot

Setting a Dashboard-Level Column Set

On the Edit Dashboard Attributes page, users can:

  • Select a column set that applies to this dashboard only.

  • Further configure columns at the widget level.

Managing Ticket Attributes

On the Tickets Table Configurations page, there is a button, “Enable ticket static attributes as tickets table columns”, that leads to another page where users can view all ticket attributes that Qvasa receives as part of the default integration when the app is installed from the marketplace.

On this page, a table lists all available ticket attributes. Look for a column titled "Is a Tickets Table Column?", which allows users to enable specific attributes as ticket columns by clicking a button. Once enabled, these attributes become available for column sets and the Inspect feature.

Did this answer your question?