Skip to content

[Due for payment 2025-05-22] [Due for payment 2025-05-20] iOS - Report fields - Duplicate introduction sentence when there is at least one report field #61683

Closed

Description

@nlemma

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.1.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+300402kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.4
App Component: Workspace Settings

Action Performed:

Precondition:

  • Workspace has added at least one report field in Report fields settings.
  1. Launch Expensify app.
  2. Go to workspace settings.
  3. Go to Report fields.

Expected Result:

There will be one introduction sentence in Report fields page.

Actual Result:

There are two introduction sentences in Report fields page.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Image

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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.

  3. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  5. github-actions commented on May 8, 2025

    @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. nlemma commented on May 8, 2025

    @nlemma
    Author

    @jliexpensify FYI 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.

  7. pecanoro commented on May 8, 2025

    @pecanoro
    Contributor

    I can reproduce on Android. I am going to find the PR that might have caused it

  8. pecanoro commented on May 8, 2025

    @pecanoro
    Contributor

    Hmm, I think it could have been caused by #60488

  9. 32 remaining items

  10. changed the title [-]iOS - Report fields - Duplicate introduction sentence when there is at least one report field[/-] [+][Due for payment 2025-05-20] iOS - Report fields - Duplicate introduction sentence when there is at least one report field[/+] on May 13, 2025
  11. melvin-bot commented on May 13, 2025

    @melvin-bot

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

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

    • @daledah requires payment (Needs manual offer from BZ)
  12. melvin-bot commented on May 13, 2025

    @melvin-bot

    @pecanoro @jliexpensify @daledah 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]

  13. jliexpensify commented on May 14, 2025

    @jliexpensify
    Contributor

    Payment Summary

    • C+: @daledah $250 (to be paid via ND requests)
  14. pecanoro commented on May 14, 2025

    @pecanoro
    Contributor

    I don't think this needs to be paid since it was a bug with the original PR, right?

  15. pecanoro commented on May 14, 2025

    @pecanoro
    Contributor

    Did we put report fields under a beta? I can't find them anymore in the app

  16. pecanoro commented on May 14, 2025

    @pecanoro
    Contributor

    Hmm, the whole section has been moved:

    Image

  17. pecanoro commented on May 14, 2025

    @pecanoro
    Contributor

    Anyhow, since this does not need to be paid, I am going to close this.

  18. jliexpensify commented on May 14, 2025

    @jliexpensify
    Contributor

    Oh right, thanks for letting me know @pecanoro!

  19. changed the title [-][Due for payment 2025-05-20] iOS - Report fields - Duplicate introduction sentence when there is at least one report field[/-] [+][Due for payment 2025-05-22] [Due for payment 2025-05-20] iOS - Report fields - Duplicate introduction sentence when there is at least one report field[/+] on May 15, 2025
  20. melvin-bot commented on May 15, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.45-21 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 2025-05-22. 🎊

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

    • @daledah requires payment (Needs manual offer from BZ)
  21. melvin-bot commented on May 15, 2025

    @melvin-bot

    @pecanoro @jliexpensify @daledah 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]

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions