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

Violation - Red dot only appears in expense preview after refreshing the page #34809

Closed
6 tasks done
lanitochka17 opened this issue Jan 19, 2024 · 6 comments
Closed
6 tasks done
Assignees

Comments

@lanitochka17
Copy link

lanitochka17 commented Jan 19, 2024

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.28-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:

Issue found when executing PR #31448

Action Performed:

Precondition:

  • Admin and employee are part of Control workspace in Old Dot
  • The Control workspace has set up Max Expense Amount violation
  1. Go to workspace chat
  2. Create a manual request that exceeds the maximum amount
  3. Submit the request
  4. Without opening expense report, refresh the page

Expected Result:

The red dot will appear in the expense preview in the workspace chat as soon as the request with violation is created

Actual Result:

The red dot only appears in the expense preview in the workspace chat after refreshing the page, or visiting the request details page

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6347723_1705676921179.bandicam_2024-01-19_19-27-54-155.mp4

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Jan 19, 2024
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

Copy link

melvin-bot bot commented Jan 19, 2024

Triggered auto assignment to @srikarparsi (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@mountiny mountiny added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Jan 19, 2024
@lanitochka17
Copy link
Author

@mountiny
Copy link
Contributor

@cead22

I dont think this has to be a blocker

@situchan
Copy link
Contributor

yup, not blocker. we already discussed about real time change concerns.

@cead22
Copy link
Contributor

cead22 commented Jan 19, 2024

Agreed. RBR for money request view hasn't been implemented yet, and will be done as part of this issue #32571

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

5 participants