$customHeader
Skip to end of banner
Go to start of banner

TFS4JIRA Cloud Native | Updating the name of an active Sprint / Iteration Path in Jira / AzureDevOps

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

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 Sprint / Iteration Path after they are initialized or mapped.

  • If it is still necessary to change the Sprint / Iteration 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 Items.

  • This will avoid manually updating every new ticket or work item using the new Sprint / Iteration Path name.

  • No labels