search

microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
182 stars 81 forks source link

Retrospective import going to the wrong team #761

Open andradeingrid opened 4 months ago

andradeingrid commented 4 months ago

Describe the bug I exported a retrospective from a project and when importing it into another project (which has 4 teams), even though I selected the correct team, the retrospective is being imported into another team that exists in the project. All teams have a separate area path and the export was done directly by the tool

Are you using the Retrospectives Tool on-prem? [ ] Yes [X] No

To Reproduce Steps to reproduce the behavior:

Go to a project and export a retrospective Then, go to a project that has more than one team, including one with the same name as the original project, and import the retrospective. When importing, see the team name that appears in the sidebar of the team that was imported

Repeat the process, but now export from the project you just imported and test again

Expected behavior When importing a retrospective into a selected team, the retrospective should be created in the correct team

Screenshots bug

What screen type are you seeing this on ? [X ] Desktop [ ] Mobile

polatengin commented 3 months ago

Hi, this is a very less-tested area. If you can share your email address, I'd like to arrange a call to troubleshoot the issue and fix it (hopefully 😄)