You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-06-09] [Card Rules Release #4] [App] Add policy changelog for adding & removing card rules #86527
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.
@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
@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
@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?
Activity
melvin-bot commentedon Mar 27, 2026
Triggered auto assignment to Design team member for new feature review - @dannymcclain (
NewFeature)JS00001 commentedon Mar 30, 2026
Havent gotten to this yet
JS00001 commentedon Apr 2, 2026
This is release #4, so moving to weekly
54 remaining items
truph01 commentedon Jun 18, 2026
@mallenexpensify They are follow-up issues, and I worked on one of them.
mallenexpensify commentedon Jun 18, 2026
@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
JS00001 commentedon Jun 18, 2026
Yeah I think we'd use https://docs.google.com/document/d/1qk_aBZCkk932Q_b9suzWIQrl3UjXG2sS8k4bZjIJPdA/edit?tab=t.0#heading=h.xn9a8cwtw4md
melvin-bot commentedon Jun 23, 2026
@truph01 Huh... This is 4 days overdue. Who can take care of this?
truph01 commentedon Jun 24, 2026
@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.
mallenexpensify commentedon Jun 25, 2026
@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?
JS00001 commentedon Jun 26, 2026
The regressions here were minor enough that I think we should payout full for this
mallenexpensify commentedon Jun 26, 2026
Payment Summary
Contributor+: @truph01 due $250 via NewDot
garrettmknight commentedon Nov 14, 2026
$250 approved for @truph01