This is running list of issues that have been identified prior to release that have not yet been corrected or addressed. While we strive to only push perfect updates into production, there are times when we want to get features out there and feel that some minor problems shouldn't block a release.
September Release
2024-09-17
- OWASP Filter not working: When viewing a scan results, users can use they query controls to retrieve results that match the selected criteria. Users can refine these results by using the small filter menu control that appears below the query controls, but above the scan results index. We have identified an issue with regard to selecting OWASP as a filter option. The results are not reliable as some Issue records check the OWASP mapping after page load rather than having that mapping stored in the database.
- New Tags & Scheduler System: With out transition to a more robust tag management system, using tags in association with Scheduled Scans will now only work after a scan had been completed. Previous to the September release, users could assign tags to future scans when creating a Scan Schedule. The tags would be automatically applied upon completion of the scan. This functionality does not currently work as expected. However, users can assign tags to scans after the scan has been completed.
June Release
No Known Issues at this time 2024-06-03
March Release
February 2024 Patch 4 Release
- OWASP Mappings are generally most functional with new workspaces and new scans. However, we have deployed some backward compatibility to existing scans. You can use query filters to find Issues by an OWASP vulnerability, however we do see some issues with that value being displayed in the results rows. Also, on initial page load for older issues, the Issue Details template does not show the OWASP finding in the right-hand column. However, by using a browser refresh to reload the template, the mapping will be displayed. We are working on an issue to align backward compatibility with our page performance standards.
Active: 2024-02-20Resolved:2024-06-04 - Workspace Assignments for New Team Members Not Saving Properly
We have received reports of an issue where Workspace Managers who attempt to add another user to the Workspace Team will not see the assignment save with the proper permission/role assignments. Managers attempting to add new users should confirm that there is a valid Role Assignment indicated on the User Card for the Team. The immediate workaround is to simply delete that user from the team and then add the user back with the desired permission/role. On the second attempt, the user is added with the desired permission/role.
Active: 2024-02-26Resolved: 2024-06-04
February 2024 Patch 3 Release
- When exporting from a Scan Issues Index page using the New Filter, only the current page issues are being exported.
Active: 2024-02-09Resolved: 2024-03-12 - Commerce Cloud workspaces do not have the isNew control available.
Active: 2024-02-13Resolved: 2024-03-12
February 2024 Patch Release
- We are investigating reports of the New Tab link for Vulnerability Detail pages not loading properly.
Active: 2024-02-06Resolved: 2024-02-09 - The Additional Results Filter that appear below the Query pulldown & input fields are not fully functional with the New Issues control. Some of these Result Filters require additional work to work with that control and we are working to resolve this.
Active: 2024-02-06
January 2024 Patch Release
- New Issues Feature Not Available for Formatted Reports
The New Findings feature will work properly with reviewing results on platform and with the CSV & JSON Export reports available from the Reports tab. The formatted PDF reports are currently not working with the New Findings feature.
Active: 2024-01-30 - New Issues Feature Only Works with Workspace Settings
There is a New Findings setting that appears in the Global Configuration tab, however at this time it does not work. New Workspaces will be created with the New Findings feature not enabled, even if the Global Configuration setting is enabled. Users must enable this feature on the Workspace→ Advanced Settings tab for it to be successfully enabled.
Active: 2024-01-30Resolved: 2024-03-27 - New Issues Feature not yet available as an option for Scheduled Scans
When creating a Scheduled Scan, users are not able to select "New Issues" as an option for scanning. However, once a scan has been run, users can use the "New Issues" toggle on the Issues Index to see that information.
Active: 2024-02-05Resolved: 2024-02-23 - Refreshed Vulnerability Detail Page potentially leads to blank Findings Index Screen
If a user is visiting a vulnerability detail page and uses the browser's refresh functionality, then uses the browser back button or the <-- Issues button to return to the Findings Index screen, they will possibly be presented with a blank screen. This is a result of a mismatch in certain page loading parameters. To resolve, simply use the browser refresh functionality on the Findings Index to reload your previous query results.
Active: 2024-01-30 Resolved: 2024-02-06 - New Issues Control Not Working with Query Filters
Query Filters do not currently in concert with Scans that have the New Issues enabled or when you are viewing a list of issues with the New Issues toggle enabled.
Active: 2024-02-01Resolved: 2024-02-06
Winter 2023 Release
- Workspace Dashboard Scan Query Pagination Not Fully Functional
When using the Workspace Dashboard query tool to find a specific set of scans, the pagination functionality that appears below the result set is not changed dynamically and does not correspond to the results. However, the query remains active as you step through the different page results. We are working to make this functionality similar to what appears on other query result pages.
Active 2024-01-23 - Refresh on Details Page not working
When you use direct links or try to refresh the page on a vulnerability detail, the browser display will blank out and the information will not be displayed.
Active 2024-01-25 Resolved 2024-01-30 - Vulnerability Index Pagination not working
Users are advised to set the number of vulnerabilities per page to 100 in order to access all the vulnerabilities properly. Lower numbers of per page listings will not display properly after the first page.
Active 2024-01-25 Resolved 2024-01-30 - Non-Admin Environment Users not able to create workspaces
Currently, Environment users who are not Admins are not able to create workspaces.
Active 2024-01-25 Resolved 2024-01-30
