MSP Manager Release Notes

Version 3.8.0 was first available for general availability (GA) on April 12, 2018

What's New

    Fixed Issues

    • Fixed

      Deleting a bill from a billing batch no longer returns to the main billing page if there is more than one ticket in the batch.

    • Fixed

      It is once again possible to have multiple Primary Points of Contact.

    • Fixed

      An issue where initial login attempt by a contact to the end user portal could result in login error has been resolved.

    • Fixed

      A change has been implemented that allows for duplicate Ticket Subtype names to be used under different Ticket Issue Types.

    • Fixed

      The behavior of the On Hold status with respect to SLA has been adjusted. As of this release, using the On Hold status will always pause SLA counters.

    • Fixed

      An issue causing ticket requests created using the end user portal to remain as requests despite proper routing configuration has now been resolved.

    Known Issues

    • Known

      The state of a timer may not update on ticket lists when navigating back to the list from within a ticket via the ‘<’ back arrow.

    • Known

      Currently, inline images cannot be pasted into 'Knowledge > Procedures' and Responses or Notes within a ticket. This will be fixed in an upcoming release. Images can be added as attachments as a work-around in the meantime.

    • Known

      The tickets list in the Customer tab is showing the incorrect completed date. To work around this issue, use Classic Mode or view the completed date from within the ticket editor.

    • Known

      When first selecting the 'Queues' menu option in Helpdesk, the ticket list is not updated until you select a specific Queue.

    • Known

      On the Company Dashboard, User Stats information will not show any change after partial billing of a ticket.

    • Known

      The 'My Dashboard' graph may be misaligned when viewing on a Surface Pro 4 or other 4k resolution screen.

    • Known

      Attempting to view the contents of a response using Edge or IE11 browsers may not show the contents of the response. This is a limitation of the ability of those browsers to render iframe contents. As a work-around, we suggest using either Chrome or Firefox.