Additional possibility to change the status of the Solution Manager Ticket immediately at creation to a customized status
In the pervious version the ticket was saved multiple times by the interface, this behaviour was cleaned up, so that only one save is performed per one call to the interface
1.2.1
Minor Enhancements
Improvement of mapping: The values from Solution Manager to Jira are now also mapped using the Mapping table in Solution Manager CC4 Configuration
Support of more than one Multi-Level Category Scheme within the Solution Manager Ticket
Creation of Solution Manager Ticket based on and linking to a Transaction Template (e.g. Incident Template, Change Request Template) is supported
Predecessor Product CC3 was decommissioned
1.2.0
Added support for multiple SAP scenarios
Increased mapping flexibility
Improved user-experience for the SAP-sided configuration
Missing translations added to the customizing views
Resolution of Issue regarding bug in mapping of empty SAP inbound process type, making it possible to create a ticket without sending a specified process type to SAP
Additional mapping objects SALES, SERVICE_H and SRV_REQ_H to map more fields within the customizing, e.g. incl. Short Description with up to 120 character, urgency or impact
40 More fields are available for the synchronization: 10 partners, 10 texts, 10 dates and 10 custom fields
Customizing guide is available in SPRO
A Sync Log is available also on SAP side as an assignment block for the tickets. Optionally a SLG1 trace can be activated/ used for analyzing interface issues.
Template customizing was enhanced and a template for all standard process types are available
date-field support for direction SAP Solution Manager to Jira
Several technical code improvements and optimizations (remove duplicated methods, remove special logic, allow simple odata calls)
1.1.9
Minor Bug Fixes and Enhancements
Bug fix for user-mapping
1.1.8
Minor Bug fixes
Bug fix for synchronization of attachments
Bug Fix for synchronization of Texts
1.1.7
Bug fixes
Bug fix for synchronization of users
Bug fix for synchronization of attachments
1.1.6
Several minor bug fixes
Due Date can now be used with Jira Custom Fields
Bug fix for synchronization of attachments
Improved mapping of Categories to support long Categories names
One configuration template for Solution Manager
Bug fixing for SolMan Outbound Creation
1.1.5
New configuration fields available for Solution Manager V1 template
Due date and Categories are now supported and can be mapped in Solution Manager V1 template.
Bug fix for synchronization of attachments.
Official support of ITSM scenario (Incidents, ...) and Requirements Management scenario additionally to ChaRM scenario and Focused Build scenario.
One configuration template for Solution Manager
Mapped Jira values incoming to Solution Manager (e.g. categories, …) can now have up to 128 characters instead of only 64 characters
1.1.4
New Template for FB SP08
1.1.3
New Template for FB SP07
1.1.2
New feature of Additional Trigger to synchronize Issues
1.1.1
SAP Solution Manager full ChaRM Integration
1.1.0
SAP Solution Manager full ChaRM Integration
Status synchronization JIRA - SolMan (both directions)
Creation of Jira Tickets from SolMan
Attachment sync
1.0.4
Release for Data Center
1.0.3
New Template for R2D Process - Focused Build Work Packages and Work Items
The Cross Connector for Jira / Solution Manager now can fully support the E2E Requirements to Deploy (R2D) Process.
Now, besides the Focused Build Requirements that were already supported, we enabled, additionally, the synchronization of Focused Build Work Packages and Work Items.
For a short demo of the integration, please check the following video: