Skip to content

Implement the Decline Money Request flow #58697

Closed

Description

@lakchote

Based on the Decline Expense in NewDot project, develop the new feature based on the context provided here.

Issue OwnerCurrent Issue Owner: @mananjadhav

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 19, 2025
  2. melvin-bot commented on Mar 19, 2025

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (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. lakchote commented on Mar 19, 2025

    @lakchote
    ContributorAuthor

    Not a bug, unassigning.

  4. added
    NewFeatureSomething to build that is a new item.
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 19, 2025
  5. melvin-bot commented on Mar 19, 2025

    @melvin-bot

    Current assignee @dylanexpensify is eligible for the NewFeature assigner, not assigning anyone new.

  6. melvin-bot commented on Mar 19, 2025

    @melvin-bot

    ⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

  7. 30 remaining items

  8. mananjadhav commented on May 7, 2025

    @mananjadhav
    Collaborator

    I am tracking the code with #52049. Will be posting questions/updates there.

  9. melvin-bot commented on May 13, 2025

    @melvin-bot

    @mananjadhav Huh... This is 4 days overdue. Who can take care of this?

  10. garrettmknight commented on May 14, 2025

    @garrettmknight
    Contributor

    Still making progress in the other issue.

  11. melvin-bot commented on May 15, 2025

    @melvin-bot

    @mananjadhav Still overdue 6 days?! Let's take care of this!

  12. mananjadhav commented on May 15, 2025

    @mananjadhav
    Collaborator

    Making progress in the linked issue. @garrettmknight Is there a reason we have two issues to track the same feature?

  13. melvin-bot commented on May 19, 2025

    @melvin-bot

    @mananjadhav Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. garrettmknight commented on May 19, 2025

    @garrettmknight
    Contributor

    @mananjadhav, it's best practice to split out individual components into individual issues so the main tracking issue isn't overwhelmed with comments. Since we've completed all other dev already, working on the tracking issue isn't causing confusion, but in the future, I'd recommend keeping your comments on the specific issue you're working on instead of the broader tracking one.

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

Metadata

Metadata

Labels

DailyKSv2NewFeatureSomething 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