Contents        

Below you will find support matrix for Jira and TFS / Azure DevOps (formerly VSTS) field types mapping in Copy value mode (i.e. the mode in which TFS4JIRA Synchronizer tries to automatically convert one value to another). Note than additionally all dictionary Jira fields (i.e. such that have allowed options list defined) can be mapped in Map values mode.




TFS / Azure DevOps (formerly VSTS) field type
Jira field typeDirection
String
Integer
Double/ Decimal
Date Time
Plain Text
Html
TreePath
Boolean
Text

TFS / Azure DevOps (formerly VSTS) → Jira(tick)

(tick)

(tick)(tick)(tick)(tick) (4)(tick)(tick)
Jira TFS / Azure DevOps (formerly VSTS)(tick)

(tick) (1)

(tick) (2)(tick) (3)(tick)(tick) (4)(tick)(tick)(12)
Free TextTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick) (4)(tick)(tick)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick) (4)(tick)(tick)(12)
Select ListTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick) (4)(tick)(tick)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick) (4)(tick)(tick)(12)
Multi SelectTFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick) (6)

(tick) (1)(7)

(tick) (2)(7)(tick) (3)(7)(tick) (6)(tick) (4)(6)(tick) (6)(error)
NumberTFS / Azure DevOps (formerly VSTS) → Jira (tick) (2)(tick)(tick)(error)(tick) (2)(tick) (2)(tick) (2)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick)(error)(tick)(tick)(tick)(error)
Radio ButtonsTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick) (4)(tick)(tick)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick) (4)(tick)(tick)
Multi CheckboxesTFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick) (6)(tick) (1)(7)(tick) (2)(7)(tick) (3)(7)(tick) (6)(tick) (4)(6)(tick) (6)(error)
Date PickerTFS / Azure DevOps (formerly VSTS) → Jira (tick) (3)(error)(error)(tick)(tick) (3)(tick) (3)(tick) (3)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(error)(error)(tick)(tick)(tick)(tick)(error)
User picker (9)TFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick)(tick)(error)
Multi User Picker

TFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS)(tick) (6)(tick) (1)(6)(tick) (2)(6)(tick) (3)(6)(tick) (6)(tick) (6)(tick) (6)(error)
Cascading SelectTFS / Azure DevOps (formerly VSTS) → Jira (error)(error)(error)(error)(error)(error)(error)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(error)(error)(error)(tick)(tick)(error)(error)
Group PickerTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
Jira → TFS / Azure DevOps (formerly VSTS)(tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick)(tick)(error)
Multi Group Picker

TFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick) (6)(tick) (1)(6)(tick) (2)(6)(tick) (3)(6)(tick) (6)(tick) (6)(tick) (6)(error)
Date TimeTFS / Azure DevOps (formerly VSTS) → Jira (tick) (3)(error)(error)(tick)(tick) (3)(tick) (3)(tick) (3)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(error)(error)(tick)(tick)(tick)(tick)(error)
LabelsTFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick) (6)(tick) (1)(7)(tick) (2)(7)(tick) (3)(7)(tick) (6)(tick) (4)(6)(tick) (6)(error)
Project PickerTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick)(tick)(error)
Single Version PickerTFS / Azure DevOps (formerly VSTS) → Jira (tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(tick) (1)(tick) (2)(tick) (3)(tick)(tick)(tick)(error)
Version PickerTFS / Azure DevOps (formerly VSTS) → Jira (tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(tick) (5)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick) (6)(tick) (1)(6)(tick) (2)(6)(tick) (3)(6)(tick) (6)(tick) (6)(tick) (6)(error)
URL Field TFS / Azure DevOps (formerly VSTS) → Jira (tick)(error)(error)(error)(tick)(tick)(tick)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(error)(error)(error)(tick)(tick)(tick)(error)
Time Tracking TFS / Azure DevOps (formerly VSTS) → Jira (error)(error)(tick) (8)(error)(error)(error)(error)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (error)(error)(tick) (8)(error)(error)(error)(error)(error)
Epic Link TFS / Azure DevOps (formerly VSTS) → Jira (error)(error)(error)(error)(tick)(error)(error)(error)
Jira → TFS / Azure DevOps (formerly VSTS) (tick)(10)(error)(error)(error)(tick)(10)(error)(error)(error)
ComponentTFS / Azure DevOps (formerly VSTS)Jira(tick)(error)(error)(error)(tick)(tick)(tick) (11)(error)
Jira → TFS / Azure DevOps (formerly VSTS)(tick)(error)(error)(error)(tick)(tick)(tick) (11)(error)
SprintTFS / Azure DevOps (formerly VSTS)Jira(tick)(error)(error)(error)(tick)(tick)(tick) (11)(error)
Jira → TFS / Azure DevOps (formerly VSTS)(tick)(error)(error)(error)(tick)(tick)(tick) (11)(error)


In version 6.0, TFS4JIRA starts supporting Rank field (TFS) synchronization. However, this only allows one-way synchronization from TFS/Azure DevOps (formerly VSTS) → Jira.

  • It needs to be mapped with a custom field (number/text) in Jira.


In TFS4JIRA we added support for Multi Value control add-on for TFS/Azure DevOps (formerly VSTS).

TFS version: https://witcustomcontrols.codeplex.com/

Azure DevOps (formerly VSTS) version: https://marketplace.visualstudio.com/items?itemName=ms-devlabs.Azure DevOps (formerly VSTS)-extensions-multivalue-control

Fields in TFS/Azure DevOps (formerly VSTS) handled by those add-ons can be mapped to array types of fields in Jira.

In order to synchronize them between Jira and TFS, in synchronizer has to be chosen option "Copy value" ->"attempt type conversion" with custom separator chosen:




(1) Source value must be parsable to integer number (e.g. "12345")

(2) Source value must be parsable to floating point number (e.g. "3.14159" or "12345")

(3) Source value must be parsable UTC time string in one of the the following formats:

  • "YYYY-MM-dd HH:mm:ssZ" (e.g. "2013-12-20 16:45:23Z") - time in TFS / Azure DevOps (formerly VSTS) will be converted according to timezone settings
  • "YYYY-MM-dd HH:mm:ss" (e.g. "2013-12-20 16:45:23") - time in TFS/ Azure DevOps (formerly VSTS) will be exactly the same as in Jira
  • "YYYY-MM-dd" (e.g. "2013-12-20") - time in TFS / Azure DevOps (formerly VSTS) will be exactly the same as in Jira and hour will be set to 00:00:00

(4) With partial Jira Markup ↔ HTML support

(5) Source value is treated as values list separated with commas (e.g. "foo, bar, baz" is treated as the following list: "foo", "bar", "baz")

(6) Source values are joined as single comma separated value (e.g. "foo", "bar", "baz" elements are concatenated as "foo, bar, baz")

(7) First source value element is taken

(8) Jira time tracking fields should be mapped to fields of type double / decimal in TFS / Azure DevOps (formerly VSTS). We assume that time in these fields in TFS / Azure DevOps (formerly VSTS) is stored in hours.

(9) User picker fields can be automatically mapped in Jira and TFS / Azure DevOps (formerly VSTS), provided that both Jira and TFS / Azure DevOps (formerly VSTS) server are connected to the same Active Directory instance and therefore share their user account data. Please see page Synchronizing user fields for details.

(10) Epic Link field is synchronized only when creating new Work Item or Issue and any later changes will not be synchronized.

(11)  See Synchronizing Area Path and Iteration Path fields for more information on synchronizing these fields.

(12)  Allowed values are only "true" and "false" (case insensitive).

  • No labels

This page has no comments.