-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2024-12-16] Card assignment cleanup, multiple members down to one #53469
Comments
Triggered auto assignment to @twisterdotcom ( |
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
The PR is ready for the review! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.72-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-16. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @twisterdotcom @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Payment Summary
BugZero Checklist (@twisterdotcom)
|
NO need payment, no need checklist |
The checklist is covered here |
Follow up of #52820, discussed here in Slack. If a workspace only has one member, we're correctly automatically selecting the one member (rather than forcing you to select them). However, if it previously had multiple members and then goes down to one, we force you to select that member when assigning a card. We shouldn't do this for custom or direct feeds.
2024-12-02_13-18-09.mp4
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: