During the sprint or Iteration path process, the team might need to adjust the Sprint or Iteration path name; TFS4JIRA will create a new entry in the 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 path value.
\uD83D\uDCD8 What needs to be considered
Avoid modifying the name of the iteration path in Azure DevOps / Sprint after they are initialized / mapped.
If it is still necessary to change the Azure DevOps / Sprint 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 items.
This will avoid manually updating every new ticket or work item that will use the new Sprint / Iteration Path name.