Issuetrak Release Notes

Magic Sign In

Magic Sign In provides a way for users with Issuetrak-authenticated user accounts to sign into Issuetrak without a password. But the benefits don't end there: Utilizing this feature improves security and allows a seamless login experience to your site.

When this feature is enabled, users are presented with a login screen that prompts them for their user ID. Once they've entered their user ID, they can click on "Send Magic Link", and they will be emailed a link that will sign them into the Issuetrak site. Administrators can configure Magic Links to be valid for between 15 and 120 minutes.

Magic Sign In requires that your Outgoing Email is configured and functioning correctly. Users that need to use this feature will also need a valid email address associated with their user account.

You might notice a "Coming Soon" section on the Password Policy screen for a "Stay Signed In" setting. We're working on making that a reality. We are going to make it possible for you to remain signed-in for as long as 30 days without re-authenticating.

Microsoft Applications Certificate Authentication

We have added the ability for you to create and download a certificate from your Issuetrak instance. You can then upload this certificate to your Microsoft app registration for use with Issuetrak's outgoing email, incoming email, and identity management features.

When you utilize Microsoft for integrations in Issuetrak, we recommend using certificate-based authentication for that purpose as a best practice, rather than using client secrets.

Issue Search Screen

We've added a "Note Entered On" field to the Issue Search screen to make it even easier to get information you want about issues.

Incoming Email

We've reduced the Microsoft Graph permissions that are required for Incoming Email to work. "User.Read.All" permission is no longer required when the Mailbox Identifier Type is set to use "Object ID / Principal Name".

Causes

We've given the Causes administration menus a major facelift, which allows you to maintain Causes with greater ease and speed.

Admin Auditing

Under specific circumstances, attempting to enable Admin Auditing would return the error "The Self-Registration Template must not be blank, and must have 'can change their own password' permission." after a site was upgraded from an older version.

Asset Management

• Error "Add failed!" would appear when trying to add an Asset Value list with CSRF enabled.
• Comments on the View screen of an asset would only show 1 line of comments.
• Asset audits imported via TrakAsset or ScanPC would be missing data once imported into Asset Management even if the audit file itself contained the relevant data.
• Attempting to print an asset barcode would return a 404 error.

Custom Labels

On the Issue Templates List screen, the column for Subject would still appear with the default name rather than the custom label if configured within the site.

Incoming Email

Incoming Email Log would show logged items in the server time zone rather than the viewing user's time zone.

Issue Cloning

Cloning an issue when the previous Submitter was inactive, would allow the issue to be submitted as that inactive user.

We have adjusted issue cloning behavior so that the following fields will not be cloned if they are populated by an inactive user:

• Submitter
• Assigned To
• Next Action

Issue Forms

Custom Headers and Screen Text would be deleted from a form if the fields were from a prior edit of an Issue Form.

Issue Hub

Issue hub indicators for Tasks were missing.

License Screen

After upgrading to 17.3.1, attempting to check for Issuetrak updates from the License screen would return an invalid "17.1.1 is Available!" message.

List UDF

If a Template with a defined list value for a UDF, had that value deleted, then when submitting an issue the list would incorrectly show "No results returned" when expanding the list.

Notifications

Department subscribers defined on an issue would fail to receive a close notification when the issue was closed.

Reports

Custom Reports

• Reports that have a date field grouped would return a 500 error message when ran.
• Reports would return a 500 error message if the site default time format was set to dd-mmm-yyyy.
• Reports would return a 500 error if it contained an Asset UDF, Associated UDF, or Multi-Select UDF.
• Report date fields would not have a space between the time and AM/PM causing
• Excel to see the field as text rather than time.
• Grouping a report by a Date UDF would have each issue grouped separately rather than by date.

Scheduled Reports

• Scheduled report files were being deleted prior to sending to users, if the total file size of the reports exceeded the "Max size of all reports in log" setting within Scheduled Reports.
• A 404 error would appear when clicking on the calendar icon for the beginning date when creating a Scheduled Report.

Summary Reports

Summary reports that would return results based on a user would return no results when clicking on the list of issues, if the UserID of the user was over 25 characters.

Scheduled Issues

Deleting a task from a Scheduled Issue would result in a 500 error.

Security

With CSRF enabled, users would be logged out after an extended time regardless of session time out settings within the site.

Task Groups

Tasks added via a Task-Associated UDF would ignore task dependencies in the task group and set new values.

Users

• A Date type UDF on a User profile would save the incorrect value if a 2 digit year is used rather than a 4 digit year.
• Issue Subtype subscriptions for a user would not appear on the user's profile within the Subscriptions screen.