Versions Compared

Old Version 5

changes.mady.by.user Former user

Saved on

compared with

New Version 6

changes.mady.by.user spg bot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed SS-macros to images

...

Three modes of synchronization are available, as shown in screenshot below:

Image Added

  • Copy full TFS tree path copies the whole path from TFS / VSTS field to JIRA Jira field. JIRA Jira field should be of "Text" type
  • Copy last part of TFS tree path copies just the last part of the path (after the last "\" character). This can be used to automatically synchronize TFS / VSTS sprints to JIRA Jira versions, provided that JIRA Jira version names are the same as TFS sprint names
  • Map values can be used for versatile mapping of TFS / VSTS tree paths to any of the JIRA Jira "mappable" type. This will typically be used to map TFS / VSTS iteration path to JIRA Jira sprints and TFS / VSTS are apaths to JIRA Jira components, but it can also be used to map TFS / VSTS sprints to JIRA Jira versions or to any other "mappable" field. In case of mapping of sprints, TFS / VSTS workitems with no iteration path will be synchronized to JIRA Jira issues not assigned to any sprint. JIRA Jira issues from the backlog (without a sprint assigned) will be synchronized to TFS / VSTS work items with iteration path set to the root of the tree path.

Image Added