Skip to content

[Due for payment 2026-06-09] [Card Rules Release #4] [App] Add policy changelog for adding & removing card rules #86527

Closed

Description

@JS00001

Activity

  1. melvin-bot commented on Mar 27, 2026

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

  2. JS00001 commented on Mar 30, 2026

    @JS00001
    ContributorAuthor

    Havent gotten to this yet

  3. JS00001 commented on Apr 2, 2026

    @JS00001
    ContributorAuthor

    This is release #4, so moving to weekly

  4. 54 remaining items

  5. truph01 commented on Jun 18, 2026

    @truph01
    Contributor

    Deploy Blocker #92295 was identified to be related to the PR #89561 that attempted to fix this issue.
    Deploy Blocker #92293 was identified to be related to the PR #89561 that attempted to fix this issue.

    @mallenexpensify They are follow-up issues, and I worked on one of them.

  6. mallenexpensify commented on Jun 18, 2026

    @mallenexpensify
    Contributor

    @JS00001 will test steps be added all at once for the project?

    @truph01 please provide more info on the deploy blockers. ie. if pay should be reduced. If they're followups, link to comments where it's stated that the followup is/was expected vs it being a regression. Thx

  7. JS00001 commented on Jun 18, 2026

    @JS00001
    ContributorAuthor
  8. melvin-bot commented on Jun 23, 2026

    @melvin-bot

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

  9. truph01 commented on Jun 24, 2026

    @truph01
    Contributor

    @truph01 please provide more info on the deploy blockers. ie. if pay should be reduced. If they're followups, link to comments where it's stated that the followup is/was expected vs it being a regression. Thx

    @mallenexpensify The comments in #92295 (comment) and #92293 (comment) indicate that this is a new feature and is currently only available in staging.

    Given that, I think it's reasonable to classify the related issues as follow-ups rather than regressions.

  10. mallenexpensify commented on Jun 25, 2026

    @mallenexpensify
    Contributor

    @JS00001 👀 above. We're generally more forgiving on new features than bugs for regressions but we still want to avoid them cuz they take resources to fix. Sometimes it comes down to "Should the C+ have caught the regression?" If so, pay should be lowered. What cha think?

  11. JS00001 commented on Jun 26, 2026

    @JS00001
    ContributorAuthor

    The regressions here were minor enough that I think we should payout full for this

  12. mallenexpensify commented on Jun 26, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @truph01 due $250 via NewDot

  13. garrettmknight commented on Nov 14, 2026

    @garrettmknight
    Contributor

    $250 approved for @truph01

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions