Skip to content

[PAID] [$250] Expense - Disabled category when selected is not highlighted #52259

Closed

Description

@IuliiaHerets

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
Email or phone of affected tester (no customers): applausetester+kh271000026@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit an expense with category.
  4. Go to workspace settings > Categories.
  5. Disable all the categories.
  6. Go to workspace chat.
  7. Go to the transaction thread (from Step 3).
  8. Click Category.

Expected Result:

The disabled category when selected should be highlighted (production behavior).

Actual Result:

The disabled category when selected is not highlighted.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6658843_1731071204219.20241108_210046.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021854920252783122362
  • Upwork Job ID: 1854920252783122362
  • Last Price Increase: 2024-11-08
  • Automatic offers:
    • rayane-djouah | Contributor | 104839950
Issue OwnerCurrent Issue Owner: @strepanier03

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 8, 2024
  2. melvin-bot commented on Nov 8, 2024

    @melvin-bot

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

  3. melvin-bot commented on Nov 8, 2024

    @melvin-bot

    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.

  4. melvin-bot commented on Nov 8, 2024

    @melvin-bot

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

  5. github-actions commented on Nov 8, 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.
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 8, 2024
  7. changed the title [-]Expense - Disabled category when selected is not highlighted[/-] [+][$250] Expense - Disabled category when selected is not highlighted[/+] on Nov 8, 2024
  8. melvin-bot commented on Nov 8, 2024

    @melvin-bot
  9. 24 remaining items

  10. melvin-bot commented on Nov 11, 2024

    @melvin-bot

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

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

  11. melvin-bot commented on Nov 11, 2024

    @melvin-bot

    @rayane-djouah @strepanier03 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]

  12. changed the title [-][HOLD for payment 2024-11-18] [$250] Expense - Disabled category when selected is not highlighted[/-] [+][HOLD for payment 2024-11-20] [HOLD for payment 2024-11-18] [$250] Expense - Disabled category when selected is not highlighted[/+] on Nov 13, 2024
  13. 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:

  14. melvin-bot commented on Nov 13, 2024

    @melvin-bot

    @rayane-djouah @strepanier03 @rayane-djouah 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]

  15. rayane-d commented on Nov 15, 2024

    @rayane-d
    Contributor

    BugZero Checklist:

    • 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 a PR
      • 2z. Other:

      Who reported the bug:

      • 3a. Expensify user
      • 3b. Expensify employee
      • 3c. Contributor
      • 3d. QA
      • 3z. Other:
    • 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/51988/files#r1844657870

    • 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

    • 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.

    • @strepanier03 Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/445572

    Regression Test Proposal

    #### Precondition:
    - A workspace has been created.
    
    #### Test:
    
    1. Go to workspace chat.
    2. Submit an expense with a category.
    3. Go to workspace settings > Categories.
    4. Disable all the categories.
    5. Go to workspace chat.
    6. Go to the transaction thread (from Step 3).
    7. Click Category.
    8. Verify that the disabled category when selected is highlighted.
    
    

    Do we agree 👍 or 👎

  16. changed the title [-][HOLD for payment 2024-11-20] [HOLD for payment 2024-11-18] [$250] Expense - Disabled category when selected is not highlighted[/-] [+][Payment 2024-11-18] [$250] Expense - Disabled category when selected is not highlighted[/+] on Nov 18, 2024
  17. strepanier03 commented on Nov 18, 2024

    @strepanier03
    Contributor

    @rayane-djouah - Thanks for the checklist! I've paid and closed the contract for you in Upwork.

    @MuaazArshad - I have sent you an offer, I'll check again later today to see if I can pay it.

  18. strepanier03 commented on Nov 19, 2024

    @strepanier03
    Contributor

    Thanks @MuaazArshad - I've paid and closed your contract. 👋

  19. changed the title [-][Payment 2024-11-18] [$250] Expense - Disabled category when selected is not highlighted[/-] [+][PAID] [$250] Expense - Disabled category when selected is not highlighted[/+] on Nov 19, 2024
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