Table of Contents

Ticketing 2.0.4 - Preview

Important

We are still working on this release. Release notes may still be modified, added, or moved to a later release. Check back soon for updates!

Prerequisites

Note

This version requires:

Tip

Installing the following apps alongside the Ticketing Solution will provide access to additional functionality:

  • MediaOps.Plan 1.4.x or higher: Required to be able to assign people to tickets.
  • InfraOps: Required to be able to link assets to tickets.

Enhancements

Text improvements in General Info and Additional Info editing form [ID 45247]

The following text has been adjusted in the General Info and Additional Info editing form:

  • "Edit Ticket" has been changed to "Edit Ticket Fields".
  • "Edit Fields" has been changed to "Edit Ticket Type Fields".
  • The message "This ticket currently has no ticket type fields that can be edited." has been changed to "No fields defined for the selected Ticket Type."

Contacts sorted alphabetically [ID 45248]

In the dropdown that can be used to assign a contact to a ticket, the contacts from the People and Organizations app are now sorted alphabetically. The "No Assignee" option will continue to be shown at the top when applicable (i.e., for a ticket that has not yet been set to "In Progress", because making such a ticket unassigned again is not possible).

Fixes

Large description cannot be fully viewed in expanded view [ID 45245]

If a ticket had a very large description (e.g., over 60 lines), the expanded view of the ticket did not show the complete description even though this should actually be the case. This issue has been resolved, so that you can now scroll down to see the complete description.

Additional info fields could be edited for rejected, canceled, and closed tickets [ID 45246]

If a ticket was rejected, canceled, or closed, it was possible to edit the Additional Info fields on the information page, even though this should not be the case.

Enum default value for ticket type kept reverting to first defined Enum field [ID 45249]

When a ticket type field of data type Enum was defined, the configured default value kept incorrectly reverting to the Enum field that has been defined first.

Improve this page