Ticketing 2.0.2

Prerequisites

• DataMiner 10.5.9/10.6.0 or higher must be installed.

• Standard Data Model Registration 2.0.x or higher must be installed.

• The user installing Ticketing needs the following user permissions:

  • General > Elements > Add
  • General > Alarms > Allow to add or update hyperlinks
  • General > Alarms > Properties > Add and General > Alarms > Properties > Edit

• Any users who will use the Ticketing Solution (including the user installing the solution) will need to have write access to the root view and the Ticketing Lock Manager element under the root view (via Permissions > Views; see Configuring a user group).

• 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

Ticket creation from correlation rule now includes affected resources and assets [ID 45110]

When a ticket is created from a correlation rule, the script that takes care of the ticket creation will now include the affected resources and any assets linked to those affected resources.

Ticket fields removed from the "Generic Issue" default Ticket Type [ID 45120]

The "Generic Issue" default ticket type now no longer contains any additional fields.

No longer possible to edit ticket fields for rejected, canceled, or closed tickets [ID 45138]

On the Information page of a ticket, the Save button is now disabled in case the ticket is in the Rejected, Cancelled, or Closed state, so that it is no longer possible to make any changes to the ticket fields of such tickets.

Various UI improvements [ID 45139]

Various improvements have been implemented to the user interface of both the Ticketing app and the automation scripts used in the Ticketing Solution.

Resolved tickets now also included under Open Tickets filter [ID 45140]

When you apply the Open Tickets filter in the upper-right corner of the Tickets page, resolved tickets will now also be displayed.

Fixes

Ticket information displayed incorrect happy path state [ID 45117]

Previously, when a ticket was in the Resolved state, the displayed happy path state was set to In Progress instead of Closed. This issue has been resolved.

The Ticket Information page will now always show the state transition buttons according to the happy path. The first purple button on the left will always show the next expected state of the happy path.

Ticket created using correlation rule did not include triggering alarm [ID 45132]

When a ticket was created using a correlation rule triggered by an alarm, the alarm was not added to the ticket as expected.