...
TFS4JIRA Self-Hosted Sprint and Iteration Path mapping options:
Map Values
...
Map values: with this mapping option, each Jira Sprint and each Azure DevOps Iteration Path must be manually selected and mapped. A default value can be set with this mapping option.
Copy full TFS tree path
...
2. Copy full TFS tree path: with this mapping option, each Jira Sprint and each Azure DevOps Iteration Path must be have the same exact name. For example, if on Azure DevOps a Iteration Path is named ‘Iteration path 2' and the project is ‘testing’ the full TFS tree path will be 'testing\Iteration path 2’ and this is how the Jira Sprint name should be to be automatically mapped.
Here is an example of the full TFS tree path in Azure DevOps and in Jira:
...
Copy last part of TFS tree path
...
Copy last part of TFS tree path: with this mapping option, each Jira Sprint and each Azure DevOps Iteration Path must be have the same exact name. This mapping is similar to the 'Copy full TFS tree path', the difference is that, if on Azure DevOps a Iteration Path name is ‘Iteration path 2', the Jira Sprint name should be the same as the Azure DevOps Iteration Path, ‘Iteration path 2' for these values to be automatically mapped.
Here is an example of the last TFS tree path in Azure DevOps and in Jira:
...
For more information about mapping, refer to our documentation here: https://appfire.atlassian.net/wiki/spaces/TFS4JIRA/pages/148177448/Synchronizing+Area+Path+and+Iteration+Path+fields?source=tfs4jirasynchronizer
...