Skip to content

[Due for payment 2025-04-17] [Simplified Actions] Implement getReportPreviewAction with tests #57440

Closed

Description

@luacmartins

Implement this section of the #migrate: Simplified actions framework for all reports design doc

cc @jnowakow

Issue OwnerCurrent Issue Owner: @lschurr

Activity

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

    @melvin-bot

    Triggered auto assignment to @lschurr (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. jnowakow commented on Feb 26, 2025

    @jnowakow
    Contributor

    Hello, I'm from Software Mansion, an expert agency, and I'll work on this one

  4. moved this to Second Cohort - CRITICAL in [#whatsnext] #migrateon Mar 4, 2025
  5. melvin-bot commented on Mar 5, 2025

    @melvin-bot

    @jnowakow 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  6. 31 remaining items

  7. melvin-bot commented on Apr 9, 2025

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

  8. melvin-bot commented on Apr 9, 2025

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

  9. luacmartins commented on Apr 9, 2025

    @luacmartins
    ContributorAuthor

    I'm closing this issue in favor of #59960. We'll handle payment via that one

  10. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Apr 9, 2025
  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 10, 2025
  12. changed the title [-][Simplified Actions] Implement getReportPreviewAction with tests[/-] [+][Due for payment 2025-04-17] [Simplified Actions] Implement getReportPreviewAction with tests[/+] on Apr 10, 2025
  13. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-4 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-04-17. 🎊

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

    • @suneox requires payment (Needs manual offer from BZ)
    • @borys3kk does not require payment (Contractor)
    • @jnowakow does not require payment (Contractor)
  14. melvin-bot commented on Apr 10, 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:

    • [@suneox] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [@lschurr] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
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 productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions