search

microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
183 stars 82 forks source link

Azure DevOps Retrospective: Voting function does not work correctly #244

Open N1str0j opened 3 years ago

N1str0j commented 3 years ago

We’ve had a retrospective with a customer a few weeks ago. When it came to the voting section we were struggling a bit with the system. We have limitated the number of votes per person to 5. Some of the attendees were not able to see the “Votes” section on the top left side. My count showed a negative value once I took my votes back. At some Point it showed that I’ve had -49 votes out of 5 so I would be able to place 54 votes in total. On top of that, our customers reported that the perfomance of the site was very poor (some of them were not able to participate as they were not able to reach the site), is there anything we can do there?

On top of that, two additional questions that are not issues:

  1. We have different customers which are interested in using the retrospectives in DevOps. How can we seperate the retros of different cutomers? At the moment every retro of every different customer would be listed (So our customers would be able to see the retro of an other customer which is not good).
  2. Is there any restriction to prevent participants of the retro to e.g. write new Feedback once the retrospective is already in the Grouping or Voting phase?
  3. Is there something like a status of a retro? Means a completed retro gets kind of an "inactive" status and only "active" retros can be changed?
emom17 commented 3 years ago

We have also hit these issues with voting