OSLC Connector for Codebeamer 2024.07.3
The delegated UI picker marked for default usage is returned to the user if it exists. This handles situations where multiple components of the same project can be part of the used Global Configuration. For DNG delegated UI pickers the user will now see the “Component” dropdown.
Support for cssClass and cssURI for artifacts; this allows developers to apply custom styles when the artifacts are displayed in third party applications.
Working in a Global Configuration context is not mandatory anymore for getting link validity.
IBM Jazz requires a Global Configuration context for link validity
Allow linking to artifacts that do not have a title
Introduced Views - used by developers to build tables of Codebeamer artifacts displayed in third party applications
Improved process to retrieve links
Errors can be displayed for each individual friend
An error encountered from one connection does not block retrieving links from other configured friends
Link can be displayed for temporarily unavailable service providers
Link labels are updated when the link validity changes
Link validity retrieved in bulk now to reduce traffic and waiting times
Delegated UI URLs for each link are retrieved in bulk now to reduce traffic and waiting times
Add support for OSLC Connector for Octane in the UI
Fix issue with favicon.ico being incorrectly a protected resource
Link validity provider URL is now exposed via RDF documents
Change logs are retained for a fixed amount of days and then get moved to the base artifacts
Types of components to be synchronized and advertised is now configurable; available values are “Testcase” and “Requirement”.
Technical changes
Updated the oauth10a library to handle X-Forwarded headers
Setting trs-enabled to false will block the building of the TRS feed now
Removed custom paths
Frontend and backend services are now provided by a single container