Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to reassign tasks during a retro #9709

Open
kendradixon opened this issue May 3, 2024 · 3 comments
Open

Not able to reassign tasks during a retro #9709

kendradixon opened this issue May 3, 2024 · 3 comments
Labels
bug p3 Should be addressed when able

Comments

@kendradixon
Copy link

kendradixon commented May 3, 2024

This user is unable to assign tasks to other active members in the meeting during a retro.

In the past 3 retros I have facilitated, I have been unable to assign tasks to people who are part of the meeting. Often the application is giving me only one person other than myself to assign a task to. This results in the tasks all being assigned to me when I am not the person who needs to work on them.

  • CS was unable to recreate the issue.
  • User confirmed he is able to see the complete list of members when he attempts to reassign from his task page.
  • CS asked for the dates of these retros and the browser used at the time - waiting on a response

Image

@kendradixon kendradixon added the bug label May 3, 2024
@Dschoordsch
Copy link
Contributor

I looked through some traces. We load the list of team members via the TaskFooterUserAssigneeMenuQuery when opening the menu. I could not see the query with the matching user id, so I assume we served stale data here.

@jordanh
Copy link
Contributor

jordanh commented May 7, 2024

@Dschoordsch thank you for triaging. Fascinating... I wonder how serving stale data happened? What would you recommend here – shall we prioritize this as a p2 or a p3 and try to triage it further or wait to see if it happens again?

For @kendradixon I am going to follow up internally on Slack and recommend we have the user purge app data to clear their cache...

@jordanh jordanh added the p3 Should be addressed when able label May 7, 2024
@Dschoordsch
Copy link
Contributor

I think this should be a p3. I'm pretty sure a refresh would fix it, but we also shouldn't serve stale data from the relay store.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p3 Should be addressed when able
Projects
Status: To Prioritize
Status: To triage
Development

No branches or pull requests

3 participants