This release has an initial version number of 7.3.15.
Listed below are the enhancements included in this release:
List of Enhancements
1. Support for OAUTH2 Authentication for Service Now connections
Service Now connections can now use OAUTH2 instead of basic authentication to connect. The user provides a client id and client secret as well as their authentication. Once the initial connection is made, the OAUTH server provides an access token which is used to make API calls to the server, thus limiting the number of times the username/password is passed over the network.
Further information can be found here:
Configuring a ServiceNow Server Connection
2. Support for Migration of CMDB Relationships into Jira
A new assignment mapping function GENERATE_JSM_OBJECT_ARRAY has been created with the purpose of allowing an array or list of relationships to CMDB objects in the source platform to be migrated to the target.
Further information can be found here:
GENERATE_JSM_OBJECT_ARRAY Function
3. Support for Cherwell to Jira Migrations
Migration of Attachments from Cherwell to Jira is now supported.
Templates have been added to facilitate migrating data from Cherwell to Jira. CMDB, Knowledge and Incident/Problem/Change migrations are all covered.
Further information on migrating knowledge articles can be found here:
Migration Of Knowledge Articles from Cherwell to Jira
Further information relating to migration of CMDB can be found here:
Preparing Jira Asset Schema for Cherwell Configuration Item migration
4. Support for Generation of a JSON File to update migrated Jira Issues
One restriction of the Jira API, which Precision Bridge uses, is that it is not possible to:
- Specify the status when creating/updating an issue. This always defaults to the initial status for the issue (usually New or Open) when the record is created.
- Specify the due date / reported by and on values.
- Specify User and Timestamp for the Created/Last Updated information. These always default to the current date/time and the user that Precision Bridge connects to Jira with. This restriction applies to issues and their comments and worklogs.
To overcome this Jira API restriction, Precision Bridge can now be configured to generate a JSON document containing:
- The correct created/updated information
- The correct due date/resolved by information
- The correct status
- All worklogs and comments to be added to the issue.
This JSON file can be easily imported manually into the Jira Server to complete the migration of issues.
This enhancement makes use of a new assignment mapping function, GENERATE_JSM_NOTES_ARRAY to obtain the comments and worknotes from the source and generate the required JSON for these to be imported.
Further information can be found here:
GENERATE_JSM_NOTES_ARRAY Function
Migrating issue data to Jira Service Management
New or Updated Templates
The following additional templates were added in this release:
| Source->Target Server | Name | Notes |
| Cherwell -> Jira | CMDB | Migrate the structure of the CMDB into a Jira schema. This will create the object types and attributes that mirror those for the source CMDB |
| Cherwell -> Jira | Configuration Items |
A project outlining how to migrate CMDB content into a Jira Asset Schema |
| Cherwell -> Jira |
Incident / Problem / Change |
This migrates incident, problem and change tickets from Cherwell into Jira issues. including related tasks and attachments. It includes the generation of a JSON file that can be manually imported onto the Jira Instance to add comments and worknotes as well as setting the correct issue status. |
| Cherwell -> Jira | Knowledge | This template supports the migration of Cherwell knowledge articles into a Jira Confluence Space |
| Service Now -> Jira | Incident / Problem / Change |
This is an update of an earlier template that now includes generation of a JSON file that can be manually imported onto the Jira Instance to add comments and worknotes as well as setting the correct issue status. |
Notice of Support Termination
With the release of Precision Bridge 7.3, Support has been withdrawn for Precision Bridge 6.3 and below. Customers still using these versions are advised to upgrade to a later release.
Currently, supported versions of Precision Bridge are: 7.3, 7.2, 7.1 and 7.0.
Advice To Users Upgrading from Precision Bridge 7.0 or earlier
The Use Server ID's Key Mapping option was removed from Precision Bridge 7.1. If this Key mapping option has been used in a project built with Precision Bridge 7.0 (or earlier), the Key Mapping option will default to 'No Key Mappings' when opened in Precision Bridge 7.1 or later.
Note that none of the Precision Bridge Templates used this option in earlier or current versions of Precision Bridge. If you have projects that use this option, be sure to select an alternative key mapping option to use (such as by selecting Key Field Mappings) before executing the project with Precision Bridge 7.2. Failure to do this may result in duplicate records being created if the project is run a second time to update existing records.
Other than the above, projects built using Precision Bridge 7.0 and above will still work with Precision Bridge 7.3 with no changes required.
Licences for 7.0 and 7.1 will still work for 7.3.
Comments
0 comments
Please sign in to leave a comment.