Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Mapping Pattern Administration screen allows you to manage Mapping Patterns.

...

Anchor
MappingFields
MappingFields
Mapping Pattern fields

All fields are required, unless specified differently. 

  • Partnership: this is the Partnership name associated to this mapping (Only Local Partnerships are allowed).
  • Source Issue Type: this is the issue type that allows the issue creation and/or linking via button(s).The link will be created from this JIRA issue type
  • Target Issue Type: this is the destination Issue Type. The issues will be created with this type.
  • Issue Link Type: this is the type of association that will be created when the 2 issues are linked to each other.
  • Link Type Versus: this option allow to choose the outward and inward description to be displayed on the source and on the target issue.The allowable options for Link Type Versus are Outward/Inward on Inward/Outward.
  • Link Type: this is a check-box that allows you to define the type of link that Quick Linker will create. The allowable options are 'Quick Link', 'JIRA Link' or 'Both'.
  • Button Label: this is the label shown on the button displayed on the 'Herzum Quick Actions' panel. It cannot be longer than 20 characters.
  • Button actions: This is a check-box that allows you to defines which button action will be enabled.
  • Allow issue creation/linking via partnership credentials: this is the check-box that allows you to provide the ability to create/linking issues to users that do NOT have the “create”/’view’ capability. If this option is selected, on creating and linking an issue, the partnership credentials will be used instead on logged user credentials .
  • Fields Mapping: this section section allows you to configure syncing between one or more fields of the two linked issues.
    1. Comment: this check-box allows sync of issue comments.The sync versus is chosen in a select list. 
      The default versus is from the destination to the source issue type. The allowed versus are =>, <= or <=>.
      The On Create Only allows to synchronize comments when added exclusively (without adding the HQL tag)
      The Synch Comment Author allows to synchronize comments via the credentials of the user who has created the comment (allowed for Local Partnership only)
      The Visibility Restriction allows to synchronize the applied restriction on the visibility of a comment 

      Info
      iconfalse

      Case of Remote Partnership ensure to setup the same Comment visibility main setting on the two JIRA instanceinstances.

    2. Attachment: this check-box allows sync of attachments.The sync versus is chosen in a select list. The default versus is from the source to the destination issue type.The allowed values are =>, <= or <=>.
    3. Other fields Mappings: this section allows to configure syncing between other fields. 
      1. The select list on the left shows all the available fields for the source issue type.The select list on the right shows all the available fields for the destination issue type. 
      2. The sync versus is chosen in a select list. The default versus is from the source to the destination issue type. The allowed versus are =>, <= or <=>.
      • The Setting on Misalignment allows to chose the value to be set on the target field when the value on the source field is not admissible for the target. Available chooses are Null (if allowed) or Leave current value.
      • Synch on Create allows to chose:
        1. for issue created via the quick linker button, if the create screen of the linked issue must be populated based on source issue's data
        2. for issue created via the escalate issue post function, if the created issue must be synced during creation.
    4. Fields Mapping List: shows the list of the fields in sync.

...