Jama Connect Interchange™, Version 1.9
Release Date US: 2023/12/15
Release Date AU/EU: 2023/12/16
Logs Page Usability Improvements
The Logs page includes new filters to help you locate specific messages more easily.
- Start Date and End Date
- Locate log messages for a specific date range.
- Locate log messages for a specific date range.
- Log Level
- Specify whether to limit which messages can be viewed; for example, view-only error messages or only info messages.
- Debug messages are hidden by default when you access the Logs page, but can be displayed by selecting the Debug filter.
- Debug messages are hidden by default when you access the Logs page, but can be displayed by selecting the Debug filter.
- Specify whether to limit which messages can be viewed; for example, view-only error messages or only info messages.
Jira Data Center 9.12 LTS Support
This release includes formal support for Jira Data Center 9.12, which is the latest long-term support version for Jira Data Center from Atlassian.
General Maintenance and Library Updates
This release includes updates to several libraries and foundational technology components, such as Java and Spring. These updates align with our continuous improvement objectives to support usability, performance, and security objectives.
Minor Enhancements
- Improved Error Handling
- We've improved error handling for scenarios where the type of a synced Jira issue is changed (for example, from Story to Bug).
- We've improved error handling for scenarios where the type of a synced Jira issue is changed (for example, from Story to Bug).
- Performance Optimizations
- The Jama Connect projects list in the Integration wizard now loads more quickly.
Resolved Issues
ID | Description |
CON-33499 |
If your Jama Connect connector uses Oauth authentication, the Logs page included frequent and unnecessary "token is expired" error messages. Logging has been adjusted to prevent this message from being displayed as often. The Jama Connect Oauth token automatically expires and regenerates periodically. The message might still appear if the Interchange integration attempts to connect to Jama Connect while the token is regenerating, but the issue resolves itself automatically and integrations are not interrupted. |
CON-37746 | Items did not sync properly from Jira to Jama Connect if the Jama Connect Tags field was mapped. This issue has been resolved. |