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-08-31] [$250] Update system messages for expenses moved to different reports #70485
Problem: Our exisitng system messages when expenses are moving reports follow different patterns, confusing users, leaving circular breadcrumbs and cluttering our expense threads unnecessarily.
Solution: Update our system messages for moving expenses:
Remove system messages for moving expenses when the action is taken on a Draft report.
[Done] Change the system message to refer to the report it was moved from instead of the report it was moved to so users can track movement back through reports for audit and context purposes.
Remove additional system messages when an expense is rejected or moved due to the expense being held while the rest are approved.
⚠️ 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 ⚠️
@mallenexpensify Note: C+ payment here would be 500, as there were 2 parts in this issue. First part was handled here #70485 (comment) and PR #80444 was for second part.
Clearing Overdue issues. If I'm late on paying, apologies, I have ~100 issues to pay on Mon/Tues and I'm paying oldest issues first. I should be all caught up tomorrow.
If anything is time sensitive, ping Matt in Slack or NewDot.
If there are posts on the PR or issue that reference a regression or deploy blocker, C+ posts on the issue and confirms regression (which will reduce pay by 50%) or provides reasoning why they shouldn’t be considered. If the C+ doesn’t update the issue, the contributor manager making the payment will assume any mention of a regression or deploy blockers reduces the issue amount.
@parasharrajat , please include your tests in the reviewers checklist in the future, thx.
Those issues were not caused by our PR so I didn't mention.
How am I supposed to know? I'm responsible for confirming the amount due and making payment. With paying hundreds of issues a week it's time consuming to have to click through every mention of a regression or deploy blocker, hence the part of the C+ doc that requires C+ to provide details. Speaking of.. i just updated it in the doc and will share in #contributor-plus soon
Post one of these two:
It was a regression. Say so. Pay drops 50% for each regression on the issue.
It was not a regression. Give the reason, and include all three:
Quote the sentence that settles it, as a blockquote. Use a screenshot only when the proof is visual.
Link the exact comment, not the issue,
State who closed the linked blocker and whether a PR closed it. A blocker the CME closed with no fix PR is not a regression. A blocker closed by a fix PR is one.
If the C+ does not post by the payment date, the CM assumes every mention of a regression or a deploy blocker reduces the amount.
📣 @rafaio1! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
📣 @rafaio1! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
melvin-bot commentedon Sep 12, 2025
Triggered auto assignment to @greg-schroeder (
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.melvin-bot commentedon Sep 12, 2025
Current assignee @greg-schroeder is eligible for the NewFeature assigner, not assigning anyone new.
melvin-bot commentedon Sep 12, 2025
176 remaining items
parasharrajat commentedon Aug 31, 2026
@mallenexpensify Note: C+ payment here would be 500, as there were 2 parts in this issue. First part was handled here #70485 (comment) and PR #80444 was for second part.
mallenexpensify commentedon Sep 2, 2026
Claude, on behalf of Matt
Clearing Overdue issues. If I'm late on paying, apologies, I have ~100 issues to pay on Mon/Tues and I'm paying oldest issues first. I should be all caught up tomorrow.
If anything is time sensitive, ping Matt in Slack or NewDot.
mallenexpensify commentedon Sep 2, 2026
@parasharrajat do you have a link to the other PR?
@twilight2294 I'm assuming you're due $250 for #80444, correct?
Anything/anyone else?!??!
parasharrajat commentedon Sep 3, 2026
@mallenexpensify Here #71220.
mallenexpensify commentedon Sep 3, 2026
@parasharrajat from the C+ doc
@parasharrajat , please include your tests in the reviewers checklist in the future, thx.
parasharrajat commentedon Sep 4, 2026
Those issues were not caused by our PR so I didn't mention.
mallenexpensify commentedon Sep 4, 2026
Payment Summary
Contributor: @twilight2294 paid $250 via Upwork
Contributor+: @parasharrajat due $500 via NewDot
How am I supposed to know? I'm responsible for confirming the amount due and making payment. With paying hundreds of issues a week it's time consuming to have to click through every mention of a regression or deploy blocker, hence the part of the C+ doc that requires C+ to provide details. Speaking of.. i just updated it in the doc and will share in #contributor-plus soon
mallenexpensify commentedon Sep 4, 2026
@parasharrajat @twilight2294 payment summary updated above, apologies for not getting correct
parasharrajat commentedon Sep 4, 2026
Thanks.
melvin-bot commentedon Sep 6, 2026
📣 @rafaio1! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
melvin-bot commentedon Sep 6, 2026
📣 @rafaio1! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format: