Skip to content

[HOLD for payment 2024-11-20] [$250] mweb - Per diem - View your subscription link opens Subscription page then back to Workspace #52201

Closed

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.0.59-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+zm27@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a new workspace
  3. Go to More features
  4. Enable Per diem
  5. Tap Upgrade
  6. On upgrade success screen, tap View your subscription

Expected Result:

App will open subscription page

Actual Result:

App opens subscription page and then opens workspace editor page quickly.
This issue only happens when upgrading workspace to Control from Per diem feature

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6657766_1730994753153.ScreenRecording_11-07-2024_23-47-45_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021854641998677095618
  • Upwork Job ID: 1854641998677095618
  • Last Price Increase: 2024-11-07
  • Automatic offers:
    • truph01 | Contributor | 104804112
Issue OwnerCurrent Issue Owner: @sakluger

Activity

  1. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    Triggered auto assignment to @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Nov 7, 2024

    @github-actions
    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.
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 7, 2024
  5. changed the title [-]mweb - Per diem - View your subscription link opens Subscription page then back to Workspace[/-] [+][$250] mweb - Per diem - View your subscription link opens Subscription page then back to Workspace[/+] on Nov 7, 2024
  6. melvin-bot commented on Nov 7, 2024

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 7, 2024
  8. 19 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 13, 2024
  10. changed the title [-][$250] mweb - Per diem - View your subscription link opens Subscription page then back to Workspace[/-] [+][HOLD for payment 2024-11-20] [$250] mweb - Per diem - View your subscription link opens Subscription page then back to Workspace[/+] on Nov 13, 2024
  11. melvin-bot commented on Nov 13, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Nov 13, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.60-3 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-20. 🎊

    For reference, here are some details about the assignees on this issue:

  13. melvin-bot commented on Nov 13, 2024

    @melvin-bot

    @ntdiary @sakluger @ntdiary 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]

  14. sakluger commented on Nov 19, 2024

    @sakluger
    Contributor

    @ntdiary payment is due tomorrow, please complete the BZ checklist by tomorrow. Thanks!

  15. ntdiary commented on Nov 20, 2024

    @ntdiary
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other: Reported on staging but not a deploy blocker.

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/51232/files#r1850266676

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. No need
      This is an edge case that was overlooked during feature development. I think it's sufficient to commen on the original PR. :)

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    Do we agree 👍 or 👎

  16. sakluger commented on Nov 20, 2024

    @sakluger
    Contributor

    Thanks everyone!

    Summarizing payment on this issue:

    Contributor: @truph01 $250, paid via Upwork
    Contributor+: @ntdiary $250, please request on Newdot

  17. JmillsExpensify commented on Nov 21, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @ntdiary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions