Please note that there may be dependencies between updating the SAP version and the Jira app version. We always recommend that you combine the matching version on SAP and Jira side for one CC4 version.
A helper report is now available determining the Jira User ID for all SAP users to be used for ticket synchronization. This Report can be used to build/update the user value mapping configuration of CC4. https://crossalm2.atlassian.net/wiki/x/AoC7nAE
A new field “Filter” is now available in our field mapping configuration.
New, unified way to send a jump-in URL from SolMan to Jira.
External tool is now allowed to send attachment binary data directly instead of an URL. (not used by Jira side so far).
All ITPPM fields are now supported.
Bug fix (SAP):
Issues synchronizing long texts. (Wrong texts got sent to Jira)
Issue with wrong business partner conversion.
Issue with multiple business partners having the same e-mail address got fixed.
Error in action SAVE_PARTNER. Please implement SAP note 3449736.
Issues with dependent constant attributes got fixed.
Attachment filename can now contain spaces.
Issues with attachment synchronization got fixed. Error handling got improved. Binary data are now read directly instead of using a content server http get call. Wrong configuration got fixed (legacy configuration is still working).
Empty comment was added after each synchronization.
We changed our Release Notes Design.
1.5.7
2.3.0
1.4.20
Bugfix
Fixed an issue with faulty dependency
1.5.6
2.3.0
1.4.18
Minor enhancement Jira side
Support for ‘Sprint’ field
1.5.5
2.3.0
1.4.17
Minor enhancement Jira side
Support for enabling conditions with spaces
1.5.4
2.3.0
1.4.16
Bug fix for middleware support
Bug fix for connection test with middleware
1.5.3
2.3.0
1.4.15
Minor enhancement Jira side
Support multiple values for enabling condition
1.5.2
2.3.0
1.4.13
Further middleware support
Adjusted handling of the connection test. Before, the connection test only worked if the CC4 Jira app received a token back from SolMan. Now, the app also accepts a success status code.
1.5.1
2.3.0
1.4.12
Middleware support
Only relevant for the following use case: If a middleware is used between Jira and SolMan and a fixed URL is configured in the middleware for every end point of the CC4 OData service, it is now possible to maintain fixed URL(s) in the CC4 app configuration for each end point.
1.5.0
2.3.0
1.4.11
Source code stabilization, improvements and fixes.
Bug fixes:
Attachment synchronization can now be deactivated in old solution. All attributes can be activated or deactivated by customizing in old and new solution.
Logging option “Application log” (logging of processing details in SLG1 log) is back (now also available in new solution). Legacy logging configuration is no longer needed. (Prior to this version both configurations were needed for activating the logging completely.)
New sync action /XALM/CC4_SX can now be used for CC4 DC as well. Issues with sending attachments and receiving error messages got fixed. Actions /XALM/CC4_CR and /XALM/CC4_UP are no longer needed but still working with some limitations.
Old and new sync action are now able to send predecessor ticket information to the external tool. CC4 is now able to link tickets bidirectionally. Jira can send parent-child details and Solman can send parent-child details. In the past these details were empty or wrong.
Sync of integer values (like Value Points and Effort Points) got fixed by removing trailing whitespaces (= sign) on sending to external tool.
Multiple issues on dealing with fallback/default values in attribute definition got fixed. (overwrite in child profile, force attribute sending, consider as external value consequently),
Bug fix on execution of status changes via ppf actions with complexe container parameters. Previous solution was causing short dumps sometimes.
Improvements:
Some new attributes like Urgency, Impact, ProdecessorExtId are now supported for inbound and outbound.
ChaRM Release Data, Focused Build ITPPM data and Focused Build IT Requirement data are now supported for direction Solman to external.
Additionally support of URLs jump into (Focused Build) UI5 app instead of SAP CRM Web UI.
Attachment changes on SAP Solution Manager side are now logged in text log, immediately sending a sync to external tool if configured.
Possibility for sending sync to external tool asynchronously (instead of synchronously).
Value mapping is now supporting special control values “*”, “#DELETE#”, #IGNORE#” or ““ (whitespace). From now on attribute values can be removed/deleted if configured (previously attributes could be set or changed but never removed/deleted)
Optimize F1 documentation for some data elements.
1.4.10
2.2.0
1.4.11
Minor Bugfix Jira side
Support for dropdown fields bi-directionally
1.4.9
2.2.0
1.4.10
Feature Enhancement
Support for Multi-Level Categorization with Jira field of type “cascading list” bi-directionally
1.4.8
2.2.0
1.4.9
Improved Error Logging
Additional stack traces added to the Jira log in case there is an issue
1.4.7
2.2.0
1.4.8
Enhanced Error Monitoring
Additional parameters added as well as the possibility to add multiple mail recipients
1.4.6
2.2.0
1.4.7
Prototype of Error Messaging
Including a 5th point in the app set up section that allows to send mails whenever the app throws an error.
The recipient mail can be set in the configuration profile
1.4.5
2.2.0
1.4.4
Attachment
Support Attachments by new solution. Old solution was already supporting it.
1.4.4
2.1.0
1.4.3
1.4.3
2.0.1
1.4.2
Minor Bugfix SAP side
minor bugfix with partner data, date formats, message length, url and ticket creation
Supporting value mapping using special character “*”.
1.4.2
2.0.0
1.4.2
Minor Bugfix Jira side
minor bugfix with empty date fields
1.4.1
2.0.0
1.4.1
Changes in View Cluster Structure and Focused Build Integration Enhancements
keep improving our custom oData service to fully integrate Focused Build process types in SAP
added support for ISO 8601 date format
Changes in View Cluster Structure and Mapping options
Major update for View Cluster on SAP side to support Jira Cloud and additional features. As a CC4 DC user, please allow some extra time for testing and possibly adjusting the view cluster for this update.
1.3.1
Minor Enhancements
minor bugfixes
1.3.0
Compatibility with Jira 9
replaced an API functionality that was retired with the release of Jira 9.0.0
1.2.2
Minor Enhancements and Bug Fixes
Additional possibility to change the status of the Solution Manager Ticket immediately at creation to a customized status
In the previous version the ticket was saved multiple times by the interface, this behavior 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: