-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-11-01] [$250] Tag rules - Tag rules are available for multi tags when the rules are not present on Old Dot #49543
Comments
Triggered auto assignment to @strepanier03 ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
We think that this bug might be related to #wave-control |
Triggered auto assignment to @deetergp ( |
This is behind a beta so it's not a blocker. cc @marcaaron |
I'm also slightly confused about why we don't allow approvers on multi-level tags. Maybe there's just not much overlap or it would be strange to potentially have multiple approvers? @JmillsExpensify what do you think about this one? |
I'm not able to reproduce this on |
@marcaaron Policy should be Control, you can enable Rules in More features to upgrade it |
Yes. Tested with a Control policy. The provided steps do not lead to a reproduction. |
Issue is still reproducible, tested just now bandicam.2024-09-20.23-07-06-209.mp4 |
Triggered auto assignment to @bfitzexpensify ( |
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Swapped out @parasharrajat for @situchan. Thanks for stepping up, Situ! |
So this is what we landed! The proposal looks good. I think we can continue PR. |
Current assignee @deetergp is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
@rezkiy37 Proposal looks good. Adding them now. |
I've opened a PR (#50917) for review 🙂 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.53-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-11-01. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
There was no regression. Regression Test ProposalPrecondition:
|
Payment complete, regression steps added. Closing this out, thanks everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.39-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
Tag rules should not be available for multi tags (because the rules are not present on Old Dot).
Actual Result:
Tag rules are available for multi tags when the rules are not present on Old Dot.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6610082_1726848355301!Dependent_-_Multi_Level_tags_NEW.csv
Bug6610082_1726848355336.20240920_235201.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @bfitzexpensifyThe text was updated successfully, but these errors were encountered: