Issuetrak Release Notes

Task-Associated UDFs

17.3 brings with it a new type of UDF: Task-Associated UDFs.

Task UDFs are an optional variation of both single-select and multi-select list UDFs, which allows administrators to associate each value on the list with a different task group. This, in turn, launches the appropriate task group(s) when a user selects one or more values. Once the user saves their changes to the issue, any task groups that were selected during issue submission will be added to the issue in the same top-to-bottom order as they were selected.

Note: Task groups selected from Task-Associated UDFs will not be added to the issue until after it has been submitted.

API v1: Multi-Select UDFs

API v1 now supports Multi-Select UDFs, along with selecting multiple values for each UDF in a single API call.

UDF Interface Overhaul

Tying together many of the UDF changes is an entirely new user interface for issue UDFs! This complete overhaul is more intuitive to navigate, easier on the eyes, and more space efficient.

Additionally:

• Tabs separate the various types of issue UDFs
• List UDFs now support importing data via CSV or other character delimiters
• List UDFs have an interface allowing tasks or task groups to be associated with specific list items, thus adding all relevant tasks and task groups upon issue submission

Webform Updates

Multi-Select UDFs

Our work on adding Multi-Select UDFs to the API has made it possible for us to add Webform Multi-Select UDFs available to our customers.

Task-Associated UDFs

Additionally, we've also engineered Task-Associated UDFs to work in conjunction with Webforms. Thus, it is now possible to make multiple selections on a single field, and have multiple tasks and/or task groups be added to the issue once it has been submitted.

Note: Tasks and task groups, if configured to be added on Webform list UDFs, will be added after the issue is submitted.

QR Codes

Lastly, we've added the ability for our webforms to work with QR codes. This allows information to be pre-populated on webforms by encoding it into the QR codes.

Consider the following scenario: 

QR code stickers are placed on the door of each conference room in your building, in case there are adjustments or problems that need to be addressed. If you scan the QR code with your phone, it will launch a webform that is pre-filled with information such as the conference room name, number, and building. You would then fill in the webform with the rest of the information it prompts you for.

Additionally, when you configure your webform to work with QR codes, you can determine whether certain fields are displayed or hidden on the form. Perhaps you want the building name to be hidden. Or maybe you want the conference room number to be prominently displayed. Explore the possibilities with your Account Manager!

Additional Documentation

You can find our documentation on webforms here.

API v2: New Endpoints

• We've added the ability to apply filter constraints to issue searches performed via API v2. 
   
• Additionally, we have also added a bunch of new endpoints to API v2:
   
  • Causes
  • Classes
  • Configuration Items
  • Custom Record Table
  • Issue Types
  • Issue SubTypes 1, 2, 3, and 4
  • Priorities
  • Projects
  • Severities
  • Substatuses
  • Tasks
     
• As a reminder, you can find documentation of API v2 and its endpoints here and here.

Zapier Zaps

The new API v2 endpoints provide the foundation for our new Zapier zaps. This means signficantly-expanded functionality for customers who use (or want to use) Zapier to work with their Issuetrak site!

Active Toggles

Per-value "Active" (and in some cases "Inactive") toggles have been added to the following areas:

• Auto Assignments
• Billing Products & Services
• Classes
• Configuration Items
• Custom Links
• Departments
• IEM Email Tokens
• Issue Forms
• Issue Types
• Project Substatuses
• Software Licenses Search Results
• Software Purchases
• Tasks
• Workflows

Admin Auditing

We've expanded the areas monitored by Admin Auditing, to include:

• Causes
• Classes
• Custom Record Table Settings
• Issue Types
• Issue SubTypes 1, 2, 3, and 4
• Priorities
• Recurring Issues
• Recurring Issues Notes
• Recurring Issues Tasks
• Service Levels
• Service Level Agreements
• Service Level Agreement Notifications
• Service Level Severities
• Service Level Terms
• Service Level Terms Off Dates
• Solutions
• Custom Record Table
• Custom Record Labels
• Substatuses
• Substatus Rules
• Tasks

Embedded HTML

The character limit for Embedded HTML has been expanded from 2,000 characters to 10,000.

Billing

In recognition of the fact that not every country or locality calls "Sales Tax" the same thing, we have made it possible to change the "Sales Tax" field label via the Features screen.

System Requirements

Although already mentioned above, this bears repeating:

• Windows Server 2025 is now officially supported
• We are dropping support for both Windows Server 2016 and SQL Server 2016
• The revised minimum supported versions are Windows Server 2019 and SQL Server 2017
• The minimum supported database compatibility level is now 130

User Interface

We've adjusted the behavior of the right menu. Since its introduction, it has provided menu links that are contextual to the area you are navigating. We wanted to make it easier to see what links are most closely related to your current screen, so we've adjusted it to always sort the name of the section you are working in to the top.

For example, if you are on the Workflow List screen, then "Automation > Workflows" will appear at the top of the right menu, along with links immediately related to the Workflows List screen, with "List" being highlighted. Other sections related to Automation will appear further down the list.

API

The API would generate a 200 (success) response to PUT calls to close an issue, but if the user making the API call did not have proper permissions, the issue was not actually getting closed. Proper validation has been implemented for this scenario.

Asset Management

It wasn't possible to edit inactive assets.

Attachments

If a task was completed during issue submission and Include Attachments was checked, the Add Attachments pop-up would appear a second time.

Automation

Some workflows would fail to process if a large number of workflows would trigger at the same time.

Global Issues

A 500 error would appear if multiple issues were manually added to a Global issue at the same time.

Hours of Operation

• Workflows would fail to trigger properly in situations where Hours of Operation spanned past midnight server time.
   
• "00" was incorrectly available as an option for Hours of Operation on a 12-hour clock (1-12).

Issue Auditing

The Issue Change Log could show an incorrect Submitted Date if the Submitting User has a different time zone than the server time zone.

Issue Cloning

A 500 error message would appear when attempting to clone an issue with subscribers.

Issue Hub

Attempting to print an Issue Hub view would only show the first view on the Print screen.

Issue Notes

Apostrophes in notes were being duplicated if the Rich Text Editor was disabled.

Knowledge Base

Fields for Created By and Created On were changed to Entered By and Entered On for the "Knowledge Base Articles" dataset in Custom Reports

Locale

Unicode characters processed by Incoming Email would appear as a "?" upon processing.

Locations

• Auto-assignments based on location would fail to properly assign issues.
   
• It was possible to submit issues without a Required Location, if the submitter did not have a location on their account.
   
• Locations on a Template would be overridden by the Submitter's Location when submitting issues.
   
• Location based auto-assignments were failing to trigger on issues submitted using the Pre-Submit screen.

Multi-Select UDFs

When tokens for Multi-Select UDFs were configured for Incoming Email, those fields were not being updated on each applicable issue when they should have been.

Notifications

Users with the permission "Will receive an email notification on Submission of ANY/ALL unassigned issues" were receiving notifications for all submitted issues.

Outgoing Email

Incoming emails auto-assigned to Round Robin groups would fail to send assignment notifications.

Projects

Non-SysAdmin users would receive a 500 error when they were attempting to access Projects.

Scheduled Reports

Editing a monthly Scheduled Report within the same month as the next run date, would change the next run date to the next month. We have added an informational message indicating that the "Next Run Date will be updated when changes saved" if a change to the frequency of a scheduled report changed the Next Run Date.

Security Remediations

• SQL Injection: We resolved a vulnerability to SQL injection attacks involving the Knowledge Base search mechanism.
   
• Insecure Direct Object Reference (IDOR): It was possible for an unprivileged user to use URL manipulation to view unapplied asset audit data.

Tasks

Task completed times were not honoring system defined date format and would always display in mm-dd-yyyy format.

User Permissions

Read-Only admins were able to access the Billing module, when they should not have been able to.

Windows Server 2025

Windows Server 2025 will not work for hosting Issuetrak under certain circumstances. We are currently investigating the specifics of this, so please check this article later for updates.

SQL Server 2025 is not affected by this.