Repository navigation
Report fields - The report field after deleted offline is still clickable #44974
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Found when validating #44493
Version Number: 9.0.5-3
Reproducible in staging?: y
Reproducible in production?: no, this is new feature
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:
- Go to staging.new.expensify.com
- Go to workspace settings > Report fields (Enable on More features if not yet).
- Add any type of report field.
- Go offline.
- Click on the report field.
- Click Delete.
- Delete the field.
- Click on the deleted report field.
Expected Result:
The report field after deleted offline should no longer be clickable.
Actual Result:
The report field after deleted offline is still clickable.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon Jul 8, 2024
Triggered auto assignment to @strepanier03 (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Jul 8, 2024
👋 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:
melvin-bot commentedon Jul 8, 2024
Triggered auto assignment to @marcochavezf (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.m-natarajan commentedon Jul 8, 2024
@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
m-natarajan commentedon Jul 8, 2024
We think that this bug might be related to #wave-collect - Release 1
mountiny commentedon Jul 8, 2024
Taking to over as I work on the project, this is still behind beta so not a blocker
@waterim @rezkiy37 who can take this?
waterim commentedon Jul 8, 2024
Hello, Im Artem from Callstack and this one will addressed here
melvin-bot commentedon Jul 16, 2024
@strepanier03, @rushatgabhane, @mountiny, @waterim Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
rushatgabhane commentedon Jul 17, 2024
PR reviewed and merged