Skip to content

[HOLD for payment 2024-03-20] Tag - Newly added tags aren't displayed under the "Tags" section in workspace settings #37873

Closed

Description

@izarutskaya

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: v1.4.48-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+alm1018@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal Team

Action Performed:

Precondition:
User is an admin of Collect workspace with no previously added tags (you should add new tags before steps reproduction )

  1. Navigate to staging.new.expensify.com
  2. Go to Workspace settings > Collect workspace
  3. Select the "Tags" tab
  4. Add some tags via classic app
  5. Refresh the page to see the newly added tags

Expected Result:

Newly added tags should be displayed under the "Tags" section in workspace settings.

Actual Result:

Newly added tags aren't displayed under the "Tags" section in workspace settings.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Bug6405013_1709793110758.tags.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. github-actions commented on Mar 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. melvin-bot commented on Mar 7, 2024

    @melvin-bot

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

  5. izarutskaya commented on Mar 7, 2024

    @izarutskaya
    Author

    @MonilBhavsar 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.

    We think that this bug might be related to #wave8-collect-admins
    CC @zanyrenney

  6. MonilBhavsar commented on Mar 7, 2024

    @MonilBhavsar
    Contributor

    @luacmartins @waterim @Abdallah-Ahmed-moh looks like it is coming from this PR #37621
    Given that this is WIP under simplified collect, I think this is not a not a blocker. Let me know what do you think

  7. 21 remaining items

  8. changed the title [-]Tag - Newly added tags aren't displayed under the "Tags" section in workspace settings[/-] [+][HOLD for payment 2024-03-20] Tag - Newly added tags aren't displayed under the "Tags" section in workspace settings[/+] on Mar 13, 2024
  9. melvin-bot commented on Mar 13, 2024

    @melvin-bot

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

  10. melvin-bot commented on Mar 13, 2024

    @melvin-bot

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

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

    • @waterim does not require payment (Contractor)
  11. melvin-bot commented on Mar 13, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@luacmartins / @MonilBhavsar] The PR that introduced the bug has been identified. Link to the PR:
    • [@luacmartins / @MonilBhavsar] 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:
    • [@luacmartins / @MonilBhavsar] A discussion in #expensify-bugs 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:
    • [@waterim] Determine if we should create a regression test for this bug.
    • [@waterim] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@greg-schroeder] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  12. melvin-bot commented on Mar 20, 2024

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  13. greg-schroeder commented on Mar 25, 2024

    @greg-schroeder
    Contributor

    Apologies, I was OOO last week. Taking a look at this now!

  14. greg-schroeder commented on Mar 25, 2024

    @greg-schroeder
    Contributor

    Closing per #37873 (comment)

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

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions