In this release:
- Standardized Query Parameters for Enterprise User Defined Fields (UDF) Metadata
- Outlook Calendar Integration in Testing Environments
Standardized Query Parameters for Enterprise User Defined Fields (UDF) Metadata ENTERPRISE
Query parameters for filtering by Issue Type and Issue Class have been renamed to match User Defined Field (UDF) metadata field conventions. The parameters previously named "issueType" and "issueClass" are now "Type" and "Class" respectively. For example, queries that previously used issueType=SO&issueClass=C now use Type=SO&Class=C.
This standardization aligns query parameter naming with the field names used throughout UDF metadata, creating consistency across the API. Developers building integrations can now use the same terminology when querying as they do when working with UDF metadata fields directly, reducing context switching and potential errors.
Updated Documentation
The documentation has been updated to reflect the new query parameter naming convention for all endpoints that filter by Issue Type and Issue Class.
Outlook Calendar Integration in Testing Environments ENTERPRISE ELITE
The Outlook Calendar Integration has been deployed to sandbox environments for testing. Teams can now validate synchronization from Elite or Enterprise to Outlook calendar in a non-production environment before the integration goes live.
This sandbox deployment enables comprehensive testing of data synchronization and integration behavior without impacting production users or data. Teams can identify and resolve any issues during the testing phase, ensuring a reliable production deployment.