-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Pay 2024-03-06][$500] [CRITICAL] Backwards Compatibility: Disabled tag is not displayed in the list as selected #35909
Comments
Triggered auto assignment to @mallenexpensify ( |
👋 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:
|
Triggered auto assignment to @marcochavezf ( |
We think that it will be under the wave [#wave6-collect-submitters] |
seems like a |
@m-natarajan can you give some more context about why this issue was created and how we deemed it to be a deploy blocker? |
Pinged @m-natarajan in Slack with the link since this is time sensitive. |
If there are steps required to reproduce the bug please list out exactly what actions were taken. Thanks! |
I can't reproduce this on |
@marcaaron Regression step https://expensify.testrail.io/index.php?/cases/view/2761738 is failing. I am adding a new video here. Recording.2701.mp4 |
Thanks for the vid @m-natarajan
I'm unsure of the specifics but, from a common sense level, I would think this would be expected behaviour. If a tag is disabled, the user/submitter should not see that tag as an option. |
There is an inconsistency between the category and tag, can someone review the issue again? Thanks bandicam.2024-02-13.10-41-01-514.mp4 |
Job added to Upwork: https://www.upwork.com/jobs/~01d431d3f18048470e |
Fair enough - I'll check back tomorrow! |
@dukenv0307's proposal looks good to me 🎀 👀 🎀 C+ reviewed |
Current assignee @cead22 is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
@cead22 @mallenexpensify @DylanDylann this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Current assignee @DylanDylann is eligible for the External assigner, not assigning anyone new. |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @dukenv0307 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Waiting for deploy to prod |
Deployed to product 2 days ago 🎉 |
@mallenexpensify Should we add Daily label to move forward this issue |
Contributor: @dukenv0307 paid $500 via Upwork Created a TestRail GH, reckon it'll be an edge case one we'll only check monthly. Thx 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: 1.4.37-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Precondition: Employee made an IOU request with a tag in WS chat. Tag is disabled after that by WS admin in OD.
Expected Result:
The disabled tag is displayed in the list as selected
Actual Result:
The disabled tag is not displayed in the list as selected
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6369435_1707232600528.bandicam_2024-02-06_17-02-45-498.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @DylanDylannThe text was updated successfully, but these errors were encountered: