Issues syncing

Overview

This page illustrates what you can expect  when the field synchronization has been configured on a mapping.

Notice that not all fields defined on your Jira instances are available for synchronization.  

Following  you can find the list of field that can be synchronized and the admissible combinations of synchronizations for different field types.

Furthermore, notice that the syncing behavior can differ with respect to the type of field in sync.

E.g. Case of  Component, the synchronization is performed on adding a new component  same way then deleting a component. Case of Attachment, the synchronization is performed on adding a new attachment exclusively.

In particular, you can expect a different behavior with respect to the following groups of  fields:

• Comment

• Attachment

• Summary and Description 

• Component, Affect Version and Fix Version 

• Priority, Assignee and Reporter

• Custom Fields.

Consider that the synchronization is active on issue creation, editing and linking.

Additionally, the Sync on create option allows chosing:

• if the create screen opened via the via Herzum Quick actions button must be pre-populated (Sync on create = True)  when creating an issue via the Herzum Quick actions button

• if the issue created via the Escalate issue post function must be populated based on the value on the source issue.

While on issue editing the sync type both is naturally provisioning, on issue creation and/or linking the app behavior follows some established conventions that are going to be detailed for:

• issue creation and/or linking via Herzum Quick actions

• issue  creation and linking via Escalate Issue post function.

At last, notice that, in general, you can expect the same behavior for a Local Partnerships as for a Remote Partnership.

This guide explain in detail all mentioned  topics so that you can configure suitable fields mappings.

Fields availability and Fields mapping around different field’s type

Fields availability

The set of Jira fields available for a syncing on a Fields mapping configuration include:

• Affected version

• Assignee

• Attachments

• Comment

• Component

• Description

• Due Date

• Fix version

• Priority

• Reporter

• Summary

Custom fields available for a field syncing configuration are:

• Text Field (single and multi line)

• Number field

• third party custom fields (e.g. the Tempo "Customer Account" custom field) recognized to be text type

• Select List (single and multiple choice) -  (for Local Partnership exclusively)

• Radio Buttons -  (for Local Partnership exclusively)

• Checkboxes -  (for Local Partnership exclusively)

• Select List (cascading) -  (for Local Partnership exclusively)

• User and Group Picker.

• Data Picker

• Data Time Picker

Fields mapping around different field types

Exception made for the following fields, you are able to create a field mappings between the same JIRA field types.

Allowable fields  for Sync on create