Skip to content

Tags - State field is not auto populated #51256

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. 52-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Pre-condition: As admin in old dot, upload dependent tags

  1. Go to https://staging.new.expensify.com/home
  2. As employee, login
  3. Open workspace chat
  4. Tap plus icon -- submit expense
  5. Enter an amount and tap next
  6. Note the state field

Expected Result:

State field must be auto populated

Actual Result:

State field is not auto populated

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
Bug6642044_1729602634818.az_recorder_20241022_183628.mp4

Dependent - Multi Level tags NEW (1).csv

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Oct 22, 2024

    @melvin-bot

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

  2. melvin-bot commented on Oct 22, 2024

    @melvin-bot

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

  3. github-actions commented on Oct 22, 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. dangrous commented on Oct 22, 2024

    @dangrous
    Contributor

    Interesting, I see it on staging (and not on production) but not able to reproduce locally. Will investigate further.

  5. dangrous commented on Oct 22, 2024

    @dangrous
    Contributor

    Found a potential cause here - #49412 - but still not able to reproduce, so it's proving hard to figure out.

  6. ishpaul777 commented on Oct 22, 2024

    @ishpaul777
    Contributor

    Hey @dangrous, sorry for noob question but can you tell me whats "dependent tags" meant in issue OP ?

  7. ishpaul777 commented on Oct 22, 2024

    @ishpaul777
    Contributor

    @lanitochka17 Can you please add steps for:

    Pre-condition: As admin in old dot, upload dependent tags

  8. lanitochka17 commented on Oct 22, 2024

    @lanitochka17
    Author
  9. ishpaul777 commented on Oct 22, 2024

    @ishpaul777
    Contributor

    Thank you!

  10. dangrous commented on Oct 22, 2024

    @dangrous
    Contributor

    Should be fixed by @ishpaul777's PR!

  11. m-natarajan commented on Oct 22, 2024

    @m-natarajan

    Not reproducible

    bandicam.2024-10-22.19-34-35-169.mp4
  12. melvin-bot commented on Oct 23, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  13. ishpaul777 commented on Oct 23, 2024

    @ishpaul777
    Contributor

    hey 👋 i found and reverted the offernding PR for this, is this eligible for payment. This was not related to a PR i authored.

    cc @yuwenmemon @dangrous

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions