Staged Release Notes

AI Note Assistant

We've added another AI feature. Note Assistant allows you to use your existing AI provider to do some very useful transformations to a note that you're editing. When this feature is enabled, and you're adding or editing a note, you'll get a choice of transformations to apply to your note from an "AI Assistant" dropdown:

• Fix grammar & spelling
• Make more professional
• Make friendlier
• Summarize
• Expand & clarify

Note Author

When adding notes, agents with appropriate permissions can now select another user from a dropdown menu to write a note on their behalf.

Why might someone want to be able to do this? We expect this will be pretty useful to folks in the arena of IT support, where the enterer of an issue is very often a different person than the submitter of the issue.

New Rich Text Editor

We've replaced the RTE, and really spruced up the "Add Note" experience with it! Editing and adding notes in an issue is really expedient now, because:

• It no longer requires a page refresh to get into "Edit" mode or save your note
• When you choose to add or edit a note, the RTE instantly appears and allows you to immediately begin working on your note

We took this opportunity to provide a much more rich experience beyond merely being the place where you add notes. The new RTE now also:

• Lets you record Labor hours and notes 
• Allows you to create and work on Billing line items, using dropdowns
• Provides helpful tooltips for Billing functionality
• Very clearly displays when you're adding or editing a Private note, in the form of a red line to the left and a slight red background
• Contains Note Assistant in a dropdown menu

Accessibility? What for?

Going forward, with each major release we've committed to getting Issuetrak into a state where it is easier for disabled folks to use. To that end, we're going through a series of accessibility compliance audits to determine what needs to be fixed. Based on those audits, we'll be combing through the product and making changes wherever we can improve the experience, making it more friendly to the vision-impaired.

You can expect this "Accessibility" section to be present with every major release, describing items we've tweaked or changed, until we are satisfied that we've reached our goal of making Issuetrak generally accessible for our customers. 

Placeholder

...

Placeholder

Placeholder text

Cross-Site Request Forgery

CSRF protection would cause a redirect to the homepage when the user attempted to add a restriction to an Issue Subtype.

Enable Support Access

If the account that activated the support user was deleted, then an error would occur when an admin subsequently attempted to reactivate the support user.

Incoming Email

• IEM would strip Outlook email formatting, such as highlighting and numbered lists.
   
• IEM Exchange did not handle emails with digital signatures. 
   
• Exclude Text would not strip the HTML banner code injected by external mail security systems.
   
• Incoming Email's "Submit new Issue or add Note as this user" setting has had its verbiage changed to be more accurate, because it implied that the designated user would always be used. It now reads as "For unrecognized senders, submit the new Issue or add the Note as this user:".

Issue Hub

• Clearing an issue's substatus via Issue Hub would leave an issue in a broken state, causing a 500 error on Edit or Close.
   
• Adding a note via Issue Hub would not set the SLA first response time.
   
• The Issue Hub "Update Issues" panel's Class dropdown would display inactive Classes.
   
• The first 5 fields of the Custom Records Table were no longer being displayed as Issue Hub columns.
   
• Issue Hub would display "Couldn't load results" sporadically for sites with heavy usage, multiple active users, and many open issues.
   
• Issue Hub views that were filtered by Location would not auto-refresh until they were clicked.

Locations

Attempting to edit a user with an underlying LocationIid above 32767 would throw a 500 error. 

Outgoing Email

Adding a note on the Close Issue screen would not trigger On Note notifications.

Reporting

• Summary Reports would fail and display a date conversion error when site date format was dd-mmm-yyyy.
   
• The Issues/Templates dataset name would not update when the Issues label was renamed.
   
• Issue links in manually exported Custom Report Excel files (formatted and unformatted) had no CSRF token. With CSRF protection on, clicking one of those links would result in landing on the user's Home Page instead of the issue.

Site Performance

Encrypted connection strings would incur a high performance cost.

Surveys

Survey email validation would reject top-level domains longer than 3 characters.

User Interface

The "Edit List UDF" modal would display the Active toggles at incorrect size.

Placeholder

Placeholder text