March Release
Release Date: March 7, 2026
This release addresses 84 tickets across all core platform modules, prioritizing data accuracy, access control integrity, and a more consistent agent experience. Key highlights include Ticketing v2 API pagination for performance gains, expanded Creator Studio bot capabilities, and strengthened menu-level API authorization.
Tickets Management
Tickets Management sees the most activity, with fixes for bulk operations, field preservation during status changes, inbox sorting, and actor/requestor dropdowns during team transfers. Template-driven clone permissions and the ability to clear date fields in the catalog are also introduced. A backend pagination upgrade to the Ticketing v2 API delivers notable performance gains across notes and history sections.
DRI-6539: Clone Permission Now Driven by Ticket Type Configuration (Enhancement)
Ticket clone is now driven from ticket-type permission. This was earlier allowed for every ticket. Administrators can configure specific ticket types to not allow cloning, preventing unauthorized duplication of sensitive or restricted ticket types.
DRI-10196: Requestor and Actor Dropdown Now Shows Complete User List During Team Transfer (Bug Fix)
Resolved an issue where the Requestor and Actor dropdown fields displayed an incomplete user list when moving a ticket between teams. Some users who were valid requestors as per ticket type role settings were previously not appearing in the dropdown during team transfer, restricting agents from being able to reassign correctly.
DRI-10258: Ability to Clear Date Field in Catalog (Bug Fix)
Previously, attempting to remove an already-set date value resulted in an error. This fix allows agents and end users to properly clear incorrect date entries, such as an erroneous resolved date, and save the ticket without encountering validation errors.
DRI-10080: Performance Improvements via Backend API Pagination in Ticketing v2 (Enhancement)
Significant performance improvements have been made to the Ticketing v2 module through backend API pagination. Sections such as Notes and History now load data in paginated batches rather than fetching the entire dataset at once. This reduces initial page load times, improves responsiveness on tickets with large histories, and ensures consistent performance across tenants with high ticket volumes.
DRI-9960: Menu-Level Permissions Now Enforced for Ticketing v2 API Calls (Bug Fix)
Navigation menu-level permissions are now properly enforced for all Ticketing v2 API calls. Previously, users could access or invoke API endpoints beyond their granted menu permissions, creating a security gap. This update ensures that the platform adheres to each user's menu access configuration when evaluating API requests, aligning API-level authorization with the UI-level access controls already in place.
Dashboard & Analytics
Dashboard & Analytics improvements resolve cross-filter inconsistencies on charts with preset filters, fix actor field dropdowns showing only the current user, and enable dependent filters to function independently without requiring a parent filter. Several UI issues are also addressed.
DRI-9398: Dashboard Cross-Filters Now Apply to Charts with Existing Chart-Level Filters (Bug Fix)
Dashboard-level cross-filters now apply to charts that already had chart-level filters configured, such as Open Tickets and Closed Tickets. Clicking a cross-filter on one chart (e.g., the Status pie chart) now correctly overrides and reflects changes on all related charts, ensuring accurate data representation across the full dashboard view.
DRI-9752: Actor Field in Dashboard Filters Now Shows Full User List (Bug Fix)
The Actor field in dashboard filters now correctly displays the full list of available users rather than showing only the currently logged-in user. This issue was affecting the ability of managers and supervisors to filter data by other agents or team members.
DRI-9361: Dependent Filters Now Usable Without a Parent Filter (Enhancement)
Dependent filters are now usable in dashboard and charts without requiring a parent filter applied. This improvement mimics the behaviour of Tickets Management filters and provides greater flexibility in filter applications.
DRI-8386: Fixed Spacing Issue on Dashboard Filter Fields (Bug Fix)
Corrected a UI rendering issue on the Dashboard where filter fields and form elements were displayed without proper spacing, causing them to appear cramped and visually merged.
Creator Studio & Bot
Creator Studio & Bot enhancements expand suggested actions support for Send and Card steps, enable dependent field linking via Adaptive Cards, and restore component history visibility for high-volume tenants.
DRI-8744: Suggested Actions Now Supported for Send and Card Steps (Enhancement)
Expanded support for Suggested Actions within Creator Studio bot flows. Bot authors can now configure suggested actions at the flow level for both Send and Card steps, supporting static options as well as dynamically constructed choices built from array-level or element-level variables.
DRI-9847: Dependent Field Behavior Now Handled via Adaptive Card Linking (Enhancement)
Dependent field behavior in bot flows is now handled through the Adaptive Card linking inputs mechanism. Fields that rely on the value of another field to populate their options now respond dynamically when the parent field value changes. This enables end users to experience responsive form behavior when interacting with multi-field bot flows across Teams and other supported channels. Presently this is supported for two-level hierarchies.
DRI-10396: Component History Now Visible for High-Volume Tenants in Creator Studio (Bug Fix)
Resolved a visibility issue where component history was not loading in Creator Studio for certain tenants, particularly those with large user bases such as the P&G tenant.
Live Chat, Service Portal, Knowledge Management & Admin App
Live Chat, Service Portal, Knowledge Management, and Admin App receive targeted bug fixes covering message formatting, offer filtering, article navigation, sync timestamps, role visibility, and responsive layout corrections.
Support
For questions or issues related to this release, please contact our support team by emailing us at support@rezolve.ai