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

[MM-432] Fix issue of todo getting assigned to last assigned user #253

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

ayusht2810
Copy link
Contributor

Summary

Ticket Link

What to test?

  • Assignee field is cleared and the old user is not assigned to the new todo after creating a todo

Checklist

  • Completed dev testing
  • make test Ran test cases and ensured they are passing
  • make check-style Ran style check and ensured both webapp and server pass the checks

@mickmister mickmister added the 3: QA Review Requires review by a QA tester label Jul 4, 2024
@ayusht2810
Copy link
Contributor Author

@mickmister Fixed the review fixes. Please re-review.

Copy link

@arush-vashishtha arush-vashishtha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The above PR has been tested for the following scenarios:

  • Tested by keeping the Assignee field clear for todo
  • Tested that the old user is not assigned to the new todo after creating a todo

The PR was working fine for both the conditions, LGTM. Approved

@ayusht2810 ayusht2810 merged commit 5e3aa74 into mattermost-community:master Jul 11, 2024
4 checks passed
@ayusht2810 ayusht2810 deleted the MM-432 branch July 11, 2024 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3: QA Review Requires review by a QA tester
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Keeping the assign field empty auto-assigns the ToDo.
3 participants