MSPM Release 4.132.0

MSP Manager: Ticket Tags, Tags Management & Unsaved Input Protection

This release improves how you organize and work tickets in MSP Manager. The updates focus on three areas: tagging tickets so they are easier to find, administering the tag catalogue from Company Settings, and protecting unsaved work in the ticket editor.

Read more: MSPM Release 4.132.0

What’s New

  • Ticket tags on the Ticket List, ticket viewer, and ticket filters
  • Color-coded tags for faster scanning
  • Tags Management in Company Settings (rename, delete, merge, usage)
  • Warning before unsaved ticket notes and replies are lost
  • Fixes for ticket Save hit area, and Outlook calendar invites

Feature Details

Ticket tags — editor, list, and filtering

Tickets can now be tagged and those tags follow the ticket through day-to-day work.

Tags show as chips on the Ticket List and in the ticket viewer. You can filter the ticket list by one or more tags in workspace filters and ticket widgets — a ticket matches if it has any of the selected tags. Clearing the tag filter restores the rest of your filter set.

Tags persist when you create a ticket, including tags created on the fly from the picker. Duplicating a ticket copies its tags onto the new ticket. Clearing all tags on save removes them from the ticket.

Integrators can also read ticket tags through the public OData route GET Tickets({id})/Tags, consistent with Assets.

This makes it easier to classify work in the queue, find related tickets, and keep tags consistent when tickets are created or duplicated.

Tags Management in Company Settings

Administrators with Company Settings access can now manage the company tag catalogue from Company Settings → Tags.

The list shows each tag with usage across tickets, assets, service items, service plans, and knowledge base items. From there you can:

  • Rename a tag
  • Delete a tag (links are removed, then the tag is deleted — you see usage before confirming)
  • Merge two tags (links move to the target tag, duplicates are dropped, the source tag is removed)

Tag pickers elsewhere pick up renamed or removed tags after you change them. Creating tags remains on entity pickers (ticket, asset, and so on), not on this admin screen.

Tags can also be given colors, similar to ticket statuses, so chips are easier to distinguish on busy lists.

Prevent data loss on unsaved ticket inputs

Writing a note, response, or other ticket action and then clicking away used to drop that text with no warning.

MSP Manager now tracks meaningful unsaved input (body text, recipients, staged attachments). Empty editors do not count as unsaved work.

If you have unsaved input, you are prompted when you:

  • Switch to another ticket
  • Navigate to another page in the app
  • Refresh or close the browser tab (native browser leave prompt)

You can stay and keep editing, or discard and continue. Discard does not publish the note or send the reply. After Save or Cancel, navigation is silent again.

Cancelling Ticket Info edits now restores the original values instead of keeping cancelled changes in memory.

Note: This release adds a navigation warning. It does not auto-save drafts or restore work after a crash.

Fixes

  • Ticket editor Save hit area — The Save control no longer overlaps the editor header, which could cancel an unsent reply, note, time entry, expense, or appointment.
  • Recurring appointments — Recurring appointments created from Schedules now send valid Outlook calendar invites (non-recurring appointments were already working).
This entry was posted in N-sight. Bookmark the permalink.