During the Sprint or Iteration Path process, the The team might need to adjust the Sprint sprint or Iteration Path name. 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 sprint / Iteration Path mapping section when changing the names of those objects.This additional entry might confuse users and can also leave work items or tickets without their corresponding sprint / Iteration .
📘 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.
\uD83D\
...
uDCD8 Recommendations to deal with object name changes
Avoid modifying the name of the Sprint / Iteration Path after they are initialized or mappedsprint 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 / sprint or Iteration Path path names, then proceed with the change, and right after doing it, manually re-map the new Sprint / Iteration Path entry in TFS4JIRA before starting to create new Issues / Work Itemsissues or workitems.This will avoid manually updating every new ticket or work item using the new Sprint / Iteration Path name
Following these considerations will help ensure that items continue to synchronize, preventing any data inconsistencies.
\uD83D\uDCCE Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|