Skip to main content
Back to Kantata.com Blog Tour Status

Jira Integration: Additional Field Syncing

By Kenna Colton | Updated

 

This feature lets you extend your Jira integration to share additional business-critical information between Jira and Mavenlink, and to override unwanted default mappings.

For each Jira issue, additional fields can be configured to sync from Jira to Mavenlink standard task or custom task fields. This can be configured in the Additional Fields section of the Jira scenario configuration page.m-bridge-jira-additional-fields-mavenlink-standard-task-field-2.png

The syncing of additional fields only goes one direction: from Jira to Mavenlink, even if you are using a two-way scenario. Values that are created or updated in Jira will sync to Mavenlink-designated task fields, but changes to those fields in Mavenlink will not sync back to Jira.

Additional Field Mapping Best Practices

There are several things to keep in mind when setting up additional field syncing:

  • Jira field names are case sensitive, so be sure to reference the exact name and type from your Jira Settings > Issues > Fields > Custom fields list.
  • To preserve values with decimals in a Jira Number Field, you must map it to a Mavenlink currency field.
  • You must map fields of a compatible type:
    • Jira date fields map to Mavenlink date fields.
    • Jira integers map to Mavenlink number or text fields.
    • Jira text fields map to Mavenlink text fields.
    • Jira single choice fields map to Mavenlink single choice fields. The values must match exactly. If the Jira choice value is not a Mavenlink choice option, the sync event will fail.
      • If you want to sync to the Priority standard task field, note that is a standard choice field with preset values. The value in the Jira field that you want to sync must exactly match the Mavenlink values: low, normal, high, and critical.
    • Jira single choice fields may also be mapped to Mavenlink text fields.
  • If the maximum number of characters accepted in a Mavenlink input field is less than in Jira, the value will be truncated in Mavenlink.
  • If you map to the Mavenlink task Start Date or Due Date fields, be aware that Mavenlink enforces the following business logic: the Due Date must be set to a value that comes chronologically after the Start Date value, or else an error will occur.
  • In a two-way scenario, you should not use additional fields to overwrite fields that are part of a standard mapping, as the Mavenlink to Jira part of the sync will likely change the values in an undesirable way. This is because the integration uses the additional field mapping instead of the standard during the Jira to Mavenlink part of the sync. However, it will use the standard mapping during the Mavenlink to Jira part of the sync, therefore overwriting the Jira field in the standard mapping.

Related Articles