Skip to content

[Custom feeds] Land on the pending feed page after creating a second feed  #51567

Closed

Description

@mountiny

Reported in Slack here - check for more details

BUG: After adding a second card feed, you're supposed to land on the feed pending screen for the second feed. Instead you land back on the first feed. Shown in 🧵

Issue OwnerCurrent Issue Owner: @allgandalf

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 28, 2024
  2. self-assigned this
    on Oct 28, 2024
  3. melvin-bot commented on Oct 28, 2024

    @melvin-bot

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

  4. koko57 commented on Oct 28, 2024

    @koko57
    Contributor

    I would like to help with this issue 🙂

  5. mountiny commented on Oct 28, 2024

    @mountiny
    ContributorAuthor

    no payments will be needed

  6. koko57 commented on Oct 29, 2024

    @koko57
    Contributor

    Working on this today. I've noticed that we have no loading state like we just applied in the Expensify card when making the call to API - maybe we should add one? And Error handling?

    Screen.Recording.2024-10-29.at.19.05.56.mov
  7. added
    ReviewingHas a PR in review
    and removed on Oct 30, 2024
  8. 8 remaining items

  9. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.58-2 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-11-14. 🎊

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

    • @koko57 does not require payment (Contractor)
    • @allgandalf requires payment (Needs manual offer from BZ)
  10. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    @allgandalf 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]

  11. melvin-bot commented on Nov 14, 2024

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @lschurr you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  12. melvin-bot commented on Nov 14, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

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

    BugZero Checklist (@lschurr)

    • I have verified the correct assignees and roles are listed above and updated the neccesary 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. lschurr commented on Nov 14, 2024

    @lschurr
    Contributor

    Checked with @mountiny on this one - we will handle payments once the custom feeds project is done. @allgandalf could you work on the checklist? #51567 (comment)

  14. mountiny commented on Nov 14, 2024

    @mountiny
    ContributorAuthor

    Yes, thanks! once the checklist is done, we can close

  15. removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Nov 14, 2024
  16. changed the title [-][HOLD for payment 2024-11-14] [Custom feeds] Land on the pending feed page after creating a second feed [/-] [+][Custom feeds] Land on the pending feed page after creating a second feed [/+] on Nov 14, 2024
  17. allgandalf commented on Nov 17, 2024

    @allgandalf
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other: Not a bug per say, we had the API written but never wrote the optimistic, failure and success data for that API.

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: N/A, there is no offending PR, we never updated Onyx data for the API untill this issue.

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    • Company Cards enabled
    • Have an existing feed for the policy

    Test:

    1. Add another new feed

    Verify that : After adding a new feed the pending page is displayed for that newly added feed feed

    Do we agree 👍 or 👎

  18. mountiny commented on Nov 18, 2024

    @mountiny
    ContributorAuthor

    I think these tests will be handled by testing added by @joekaufmanexpensify for the project. I am going to close this as we will handle the payments together later for the project. Thanks for the rest for the checklist

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions