We're releasing Issuetrak 17.7 today, and with it we are highlighting a significant update to the Issue Hub, as well as smaller updates to functionality throughout the product.
Issue Hub has seen a substantial reworking under the hood, as well as a nice visual refresh. We've included some new functionality to Issue Hub in response to your feedback, including the ability to export views, as well as fine control over column filters.
Keep reading to find out more!
Issue Hub
We've refreshed the user interface and the user experience for Issue Hub. Here's how you can expect the experience to differ after upgrading to 17.7:
- We've added the ability to export your current view to CSV and XLSX formats. Not only that, it exports data with all of your sorts, filters, and custom column names applied to it. When you choose to export a view, you even get a nice new lightbox telling you what's going on.
- Speaking of filters, we give you the ability to quickly set operators on view columns, like "Starts With" or "Contains", etc.
- Clicking on any issue record in Issue Hub will give you a preview of the issue you selected.
- When you click on the "Hub Settings" button, a Hub Settings panel now slides out from the right that allows you to control which views are visible more quickly and easily than before.
- Similarly, when you click on the "View Settings" button, you get a slide-out menu from the right that allows you to control the view you currently have selected. The filtering you get on the "View Settings" menu is powerful, as well. We've given you the ability to set conditions and filter logic similar to Custom Reports.
- There's a new "Today's Reminders" button to show you any issue and / or asset-related deadlines that are coming due.
- The "indicators" column can now be added to / removed from views, which wasn't possible before.
Security
Altcha
We have added support for Altcha to Issuetrak. When activated, this optional feature will prompt a user to complete a quick task before allowing them to complete the action they are attempting. Currently, the only actions this will apply to are Self-Registration, "Email Issue" and "Email KB" functionality.
Cross-Site Request Forgery
CSRF protection has been reworked to become more secure.
Session Rate Limiting
We've built session rate limiting into the product for Self-Registration, "Email Issue", and "Email KB" pages:
- Self Registration - 5 submissions per 15 minutes
- Email Issue - 50 submissions per 5 minutes
- Email KB - 50 submissions per 5 minutes
Office 365 Applications
We now support adding Microsoft's "US Government DoD" tenant to integrate with Issuetrak.
Reporting
Data Sets
There's 4 new data sets you can use for your custom reports:
- Quick Notes
- Issue Templates
- User Assignments (this is related to Asset Management)
- Workflows
Export Summary Reports
Additionally, you can now export summary reports to Excel or CSV format.
Placeholder
...
Placeholder
...
Legacy ScanPC
We have removed the legacy ScanPC executable from the product. It only supported Windows XP and older versions of Windows. If you need it, we can provide it on request!
Admin Auditing
It was not possible to activate Admin Auditing under the following specific circumstances:
- "Update existing users on login" was unchecked
- The logged-in user was authenticated via OAuth / OIDC (Entra, AD Federation Services, or third party OIDC)
- The user's authentication ID was their email address (or SID, if previously authenticated via LDAP)
When attempting to activate Admin Auditing, the following error would appear when attempting to authenticate:
There was a problem authenticating against AD Federation Services.
API v2
When issues were submitted via API v2, the Description field was being treated as plaintext in all situations, and displaying HTML tags when it should not have been.
Deployment Tools
Attempting to upgrade from Issuetrak 15.1 to 17.6 would fail because of a problem with how the upgrade was handling Office 365 applications.
Issue Forms
- A 500 error would appear when attempting to edit an issue form with an extremely large (~500) number of fields. We've capped the maximum number of fields on an issue form to 495, and the 500 error will no longer appear
- Issue forms that contained a section header called "Subtype" would make it impossible to edit issue forms containing issue subtypes.
Issue Hub
When an issue was closed using the Issue Hub's "close as duplicate" without viewing it, it would cause the "Adjusted Time Open" and "Total Time Open" fields in reporting to contain NULL values.
Localization
It was not possible to add Chinese characters as IEM Keywords, as they would be stored as "???".
Performance Improvement
There was higher latency in page loading and response times, as compared between Issuetrak versions 15.1 and 17.5. We believe we have significantly improved performance in that regard for 17.7.
Quick Search
Using the Quick Search bar to search for numbers above 2,147,483,647 would return an error.
Reporting
- Sites that used MSOLEDB19 as the connection provider would experience an error for scheduled reports, when the following conditions were present:
- Web and SQL on separate servers
- MSOLEDB19 installed on the web server
- SQL server configured to NOT require an encrypted connection
- SSL certificate installed properly on the SQL server
- Weekly scheduled reports were being started the week after they were set, rather than the current week, where applicable.
- Exporting reports to CSV would display a 401 error, and viewing admin auditing search results would throw a 502 error.
Security
We've patched a security vulnerability that was responsibly disclosed to us:
Signed in non-admin users were able to view information about other user accounts by visiting an Issuetrak site and adding the following path to the URL: /core/user/search
Timezones
We've added British Columbia's UTC-7 time zone to Issuetrak, since we didn't have it before.
User Administrators
User administrators were unable to clone users under certain circumstances: When the User Admin was a member of multiple Organizations, and their Primary Org had an Org ID that was numerically higher than the other Org they were a member of.
User Defined Fields
Large Text UDFs were not calculating the correct number of characters remaining.
Workflows
Workflows were changing the substatus on issues when they were only configured to close issues that had the substatus set to "Resolved".