Issue Summary
- The PI on a feature (parent) is updated and this triggers JIRA Align to update the child stories.
- The update to the child stories is setting the Team to the wrong value in Jira Align
- The updated story is synchronized to JIRA. This causes the wrong team to show in Jira.
Notes:
- We've noted that this only happens when the stories are not part of a sprint.
- The correct team will be used when the stories are associated with a sprint
- We also see that this only happens when a custom field is used for the team in Jira.
Steps to Reproduce
- Support has not been able to reproduce this behavior.
Expected Results
- Jira Align and Jira show correct team
Actual Results
- Stories in Jira Align show wrong Team
- Story is synchronized to JIRA. This causes the wrong team to show in Jira.
Workaround
- No workaround has been found other than manually correcting the team for each item. The behavior is being investigated and a workaround will be posted if one is found
- is duplicated by
-
JIRAALIGN-2732 Jira Connector: Synchronizing Stories from Jira that are associated to a team that doesn't exist in Jira Align causes invalid updates (custom team mapping)
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ALIGNSP-5230 Loading...
-
ALIGNSP-6269 Loading...