TFS4JIRA Cloud Native | Updating the name of sprint or iteration path objects
The team might need to adjust the sprint or Iteration path name during the sprint (Jira) or iteration path (ADO) process. When changing the names of those objects, TFS4JIRA will create a new entry in the sprint / Iteration Path mapping section.
Steps to reproduce
Map the Sprint and Iteration path fields along with their values.
Synchronize an item so the sprint and Iteration path fields are populated
Go to ADO and update the iteration path name
Go to TFS4JIRA; a new iteration path entry will be available for mapping.
This extra entry may require clarification for users and could result in work items or issues being devoid of their corresponding sprint or iteration path value.
 Recommendations to deal with object name changes
Avoid modifying the sprint or iteration path's name after it is initialized or mapped, especially if items are already assigned to these values.
If it is still necessary to change the sprint or Iteration path names, then proceed with the change, and right after doing it, manually re-map the new entry in TFS4JIRA before starting to create new issues or workitems.
Following these considerations will help ensure that items continue to synchronize, preventing any data inconsistencies.