Skip to content

[Due for payment 2025-03-27] [Better Expense Report View] Implement Expense Preview component #57506

Closed

Description

@mountiny

Implement this section of the design doc.

@Guccio163 @Kicu @JakubKorytko

Issue OwnerCurrent Issue Owner: @sakluger

Activity

  1. self-assigned this
    on Feb 26, 2025
  2. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    Triggered auto assignment to @sakluger (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

  3. moved this to Second Cohort - CRITICAL in [#whatsnext] #migrateon Feb 26, 2025
  4. JakubKorytko commented on Feb 27, 2025

    @JakubKorytko
    Member

    Hello, please assign this to me.

  5. sakluger commented on Mar 7, 2025

    @sakluger
    Contributor

    Hey @JakubKorytko @mountiny - any updates on the PR progress?

  6. 11 remaining items

  7. changed the title [-][Better Expense Report View] Implement Expense Preview component[/-] [+][Due for payment 2025-03-27] [Better Expense Report View] Implement Expense Preview component[/+] on Mar 20, 2025
  8. melvin-bot commented on Mar 20, 2025

    @melvin-bot

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

  9. melvin-bot commented on Mar 20, 2025

    @melvin-bot

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

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

  10. melvin-bot commented on Mar 20, 2025

    @melvin-bot

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

    • [@allgandalf / @DylanDylann] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
  11. mountiny commented on Mar 20, 2025

    @mountiny
    ContributorAuthor

    No specific payments to be handled on this one

  12. melvin-bot commented on Mar 27, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @JakubKorytko is from an agency-contributor and not due payment
    • ROLE: @allgandalf paid $(AMOUNT) via Upwork (LINK)
    • ROLE: @DylanDylann paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@sakluger)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. sakluger commented on Mar 27, 2025

    @sakluger
    Contributor

    No payments required.

    @mountiny do we need to add regression tests here, or will they be added as part of the larger project?

  14. mountiny commented on Mar 27, 2025

    @mountiny
    ContributorAuthor

    @sakluger this will be handled at the end of the project, correct! I think we can close this one now

  15. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Mar 27, 2025
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 productionDailyKSv2NewFeatureSomething to build that is a new item.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions