Skip to content

[$250] Notifications - No push notification when admin change expense amount #83533

Closed

Description

@jponikarchuk

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: v9.3.26-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #83171
Email or phone of affected tester (no customers): gocemate+b215490617@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 10/Chrome
App Component: Other

Action Performed:

  1. Precondition:
    Make sure the browser allows notifications.
    Ensure Account A is a workspace member and Account B is a workspace admin.

Steps:

  1. On the web, sign in as Account A and create an expense.
  2. From Account B, update the expense amount

Expected Result:

There should be a push-notification from Account A, verify you receive a notification like: "Account B changed the amount to $X.XX."

Actual Result:

No push notification when admin change expense amount

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @abzokhattab
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022026886058462315518
  • Upwork Job ID: 2026886058462315518
  • Last Price Increase: 2026-03-12
  • Automatic offers:
    • abzokhattab | Reviewer | 110805348

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 26, 2026
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 26, 2026
  3. melvin-bot commented on Feb 26, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @abzokhattab (External)

  4. melvin-bot commented on Feb 26, 2026

    @melvin-bot

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

  5. changed the title [-]Notifications - No push notification when admin change expense amount[/-] [+][$250] Notifications - No push notification when admin change expense amount[/+] on Feb 26, 2026
  6. melvin-bot commented on Feb 26, 2026

    @melvin-bot
  7. daledah commented on Feb 26, 2026

    @daledah
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    No push notification when admin changes expense amount.

    What is the root cause of that problem?

    When an admin (Account B) modifies an expense amount, the backend creates a MODIFIED_EXPENSE report action on the transaction thread report and sends a Pusher update to Account A.

    On the frontend, triggerNotifications processes the Pusher update and calls shouldShowReportActionNotification, which checks the notification preference of the report:

    // We don't want to send a local notification if the user preference is daily, mute or hidden.
    const notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`]);
    if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS) {
    Log.info(`${tag} No notification because user preference is to be notified: ${notificationPreference}`);
    return false;
    }

    However, transaction thread reports are created with notificationPreference: HIDDEN by default:

    App/src/libs/ReportUtils.ts

    Lines 8634 to 8644 in a152afa

    return buildOptimisticChatReport({
    participantList: participantAccountIDs,
    reportName: getTransactionReportName({reportAction}),
    policyID: moneyRequestReport?.policyID,
    ownerAccountID: CONST.POLICY.OWNER_ACCOUNT_ID_FAKE,
    notificationPreference: CONST.REPORT.NOTIFICATION_PREFERENCE.HIDDEN,
    parentReportActionID: reportAction?.reportActionID,
    parentReportID: moneyRequestReport?.reportID,
    optimisticReportID: optimisticTransactionThreadReportID,
    chatReportID: moneyRequestReport?.reportID,
    });

    Since the check requires notificationPreference === ALWAYS, the MODIFIED_EXPENSE notification on the transaction thread is always suppressed — the function returns false before reaching the notification display code at showReportActionNotification.

    What changes do you think we should make in order to solve the problem?

    In shouldShowReportActionNotification, for MODIFIED_EXPENSE actions on transaction threads, we should fall back to the parent report's notification preference instead of using the transaction thread's (which is always HIDDEN).

    --- a/src/libs/actions/Report/index.ts
    +++ b/src/libs/actions/Report/index.ts
    @@ -3806,7 +3806,13 @@ function shouldShowReportActionNotification(reportID: string, currentUserAccount
         }
     
         // We don't want to send a local notification if the user preference is daily, mute or hidden.
    -    const notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`]);
    +    const report = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`];
    +    let notificationPreference = getReportNotificationPreference(report);
    +
    +    if (action?.actionName === CONST.REPORT.ACTIONS.TYPE.MODIFIED_EXPENSE && report?.parentReportID) {
    +        const parentReport = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${report.parentReportID}`];
    +        notificationPreference = getReportNotificationPreference(parentReport);
    +    }
    +
         if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS) {
             Log.info(`${tag} No notification because user preference is to be notified: ${notificationPreference}`);
             return false;

    Note: we can also add the logic to cover other action names

    What alternative solutions did you explore? (Optional)

    An alternative would be to change the default notificationPreference for transaction threads from HIDDEN to ALWAYS, but that would cause unwanted notifications for every comment on transaction threads, which is not the desired behavior.

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  8. mukhrr commented on Feb 26, 2026

    @mukhrr
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    When a workspace admin (Account B) modifies the amount of an expense created by a workspace member (Account A), Account A does not receive any push or browser notification about the change, which prevents the expense creator from being aware that their expense was modified.

    What is the root cause of that problem?

    Transaction thread reports are created with notificationPreference: HIDDEN by default.

    notificationPreference: CONST.REPORT.NOTIFICATION_PREFERENCE.HIDDEN,

    When an admin modifies an expense amount, the MODIFIED_EXPENSE report action is added to the transaction thread report.

    key: `${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${transactionThreadReport?.reportID}`,

    The shouldShowReportActionNotification function checks the notification preference of the report associated with the action. Since the transaction thread has HIDDEN preference, the check at line 3571 fails and the function returns false, blocking the notification entirely.

    const notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`]);
    if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS) {
    Log.info(`${tag} No notification because user preference is to be notified: ${notificationPreference}`);
    return false;
    }

    This same function is used by both the local notification path (via triggerNotifications in User.ts) and the push notification path (via shouldShowPushNotification.ts), so no notification is shown on any platform.

    shouldShow = Report.shouldShowReportActionNotification(String(data.reportID), currentUserAccountID, reportAction, true);

    What changes do you think we should make in order to solve the problem?

    1. In shouldShowReportActionNotification, when the report is a thread (transaction thread), fall back to checking the parent report's notification preference instead of the thread's own HIDDEN preference. This ensures that if the parent expense report has ALWAYS notification preference, the modified expense notification will be shown.

    const notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`]);
    if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS) {
    Log.info(`${tag} No notification because user preference is to be notified: ${notificationPreference}`);
    return false;
    }

    --- a/src/libs/actions/Report/index.ts
    +++ b/src/libs/actions/Report/index.ts
    @@ -3567,7 +3567,13 @@ function shouldShowReportActionNotification(reportID: string, currentUserAccount
         }
    
         // We don't want to send a local notification if the user preference is daily, mute or hidden.
    -    const notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`]);
    +    const report = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${reportID}`];
    +    let notificationPreference = getReportNotificationPreference(report);
    +
    +    // Transaction threads have HIDDEN notification preference by default, so check the parent report's preference instead
    +    if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS && isChatThreadReportUtils(report) && report?.parentReportID) {
    +        notificationPreference = getReportNotificationPreference(allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${report.parentReportID}`]);
    +    }
         if (notificationPreference !== CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS) {
             Log.info(`${tag} No notification because user preference is to be notified: ${notificationPreference}`);
             return false;
  9. MelvinBot commented on Feb 26, 2026

    @MelvinBot
    Contributor

    🔍 Issue Analysis

    Summary: No push/browser notification is shown to the expense creator (Account A) when an admin (Account B) changes the expense amount. The client-side App code is fully implemented to handle MODIFIEDEXPENSE notifications — the root cause is almost certainly server-side: the backend is not flagging the Onyx update for notification delivery.

    Confidence: High (code evidence is conclusive for the client side; server-side diagnosis is inferred since Web-Expensify is not inspectable here)

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    When a workspace admin modifies an expense amount created by another user, no push notification (mobile) or browser notification (web) is shown to the expense creator. The expected behavior is a notification like "Account B changed the amount to $X.XX."

    What is the root cause of that problem?

    The App's notification pipeline has a server-controlled gate in triggerNotifications():

    function triggerNotifications(onyxUpdates, currentUserAccountIDParam) {
        for (const update of onyxUpdates) {
            if (!update.shouldNotify && !update.shouldShowPushNotification) {
                continue;  // <-- skips the update entirely if server didn't flag it
            }
            // ... triggers showReportActionNotification()
        }
    }

    When the server sends Onyx updates via Pusher containing a MODIFIEDEXPENSE report action, it must set shouldNotify: true or shouldShowPushNotification: true on the update payload. If neither flag is set, triggerNotifications() skips the update at line 691-692, and no notification is ever shown — on any platform.

    The client-side code is fully implemented and correct:

    For mobile specifically: Local notifications are completely no-op on native. Mobile users rely exclusively on server-sent Airship push notifications. If MobilePushNotifications.php in Web-Expensify does not include MODIFIEDEXPENSE in its notifiable action types, mobile users will never see a notification.

    This explains the cross-platform nature of the bug (Android App, iOS App, Windows Chrome all affected) — the server is the single point of failure for all platforms.

    What changes do you think we should make in order to solve the problem?

    The fix needs to happen on the server side (Web-Expensify backend):

    1. For web/browser notifications: Ensure the Onyx update payload containing MODIFIEDEXPENSE report actions (specifically from the UpdateMoneyRequestAmountAndCurrency API command) includes shouldNotify: true when sent to other participants via Pusher.

    2. For mobile push notifications: Ensure MobilePushNotifications.php (or equivalent) sends Airship push notifications for MODIFIEDEXPENSE report actions when an admin modifies another user's expense.

    If there is also an App-side concern, the only potential client-side filter that could block the notification is the notification preference check at Report/index.ts:3810 — it requires notificationPreference === ALWAYS. For policy expense chats, the default should be ALWAYS, but this should be verified for the specific expense report type.

    What alternative solutions did you explore?

    The investigation ruled out several possible client-side causes:

    Detailed Investigation

    Notification Data Flow

    1. Admin changes expense amount → updateMoneyRequestAmountAndCurrency() (IOU/index.ts:8581)
    2. Client creates optimistic MODIFIEDEXPENSE report action via buildOptimisticModifiedExpenseReportAction() (ReportUtils.ts:7528)
    3. API.write(WRITE_COMMANDS.UPDATE_MONEY_REQUEST_AMOUNT_AND_CURRENCY, ...) sends to server
    4. Server creates real report action and sends Onyx updates to other participants via Pusher
    5. Gate 1 (server-side): triggerNotifications() (User.ts:689) checks shouldNotify / shouldShowPushNotification flags — these are set by the server
    6. Gate 2 (client-side): shouldShowReportActionNotification() (Report/index.ts:3792) checks generic filters
    7. showReportActionNotification() routes MODIFIED_EXPENSE to LocalNotification.showModifiedExpenseNotification()
    8. BrowserNotifications.pushModifiedExpenseNotification() formats and displays the notification

    Evidence Chain

    Evidence Location Significance
    triggerNotifications() skips updates without server flags User.ts:691-692 First gate — server must set shouldNotify
    shouldShowReportActionNotification has NO action-type filtering Report/index.ts:3792-3855 Client doesn't exclude MODIFIEDEXPENSE
    MODIFIED_EXPENSE explicitly handled in showReportActionNotification Report/index.ts:3873 Client IS prepared for this notification
    Mobile local notifications are no-ops index.native.ts:4-9 Mobile relies entirely on server push
    shouldNotify/shouldShowPushNotification are server-set OnyxUpdatesFromServer.ts:13-28 Flags come from backend

    Open Questions

    • Does Web-Expensify's MobilePushNotifications.php include MODIFIEDEXPENSE in its notifiable action types?
    • Does the Pusher Onyx update pathway set shouldNotify: true for MODIFIEDEXPENSE report actions from admin edits?
    • Is there a difference in notification behavior between admin-initiated vs. submitter-initiated expense edits?

    Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.

  10. abbasifaizan70 commented on Feb 26, 2026

    @abbasifaizan70
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Notification behavior is inconsistent when the admin changes the expense amount:

    • sometimes no browser push is shown;
    • sometimes only the notification sound is played, but the chat is not marked unread in LHN.
    • when multiple unopened notifications arrive, earlier unread notifications can be auto-marked read after a later one arrives.

    What is the root cause of that problem?

    There are four race-prone points in this flow.

    First, push notification filtering resolves the action from payload by taking the latest action from the first reportActions_* Onyx update it finds, instead of selecting the exact action by reportActionID from the push payload.

    const reportAction = ReportActionUtils.getLatestReportActionFromOnyxData(data.onyxData ?? null);
    shouldShow = Report.shouldShowReportActionNotification(String(data.reportID), currentUserAccountID, reportAction, true);
    }

    function getLatestReportActionFromOnyxData<TKey extends OnyxKey>(onyxData: Array<OnyxUpdate<TKey>> | null): NonNullable<OnyxEntry<ReportAction>> | null {
    const reportActionUpdate = onyxData?.find((onyxUpdate) => onyxUpdate.key.startsWith(ONYXKEYS.COLLECTION.REPORT_ACTIONS));
    if (!reportActionUpdate) {
    return null;
    }
    const reportActions = Object.values((reportActionUpdate.value as ReportActions) ?? {});
    const sortedReportActions = getSortedReportActions(reportActions);
    return sortedReportActions.at(-1) ?? null;

    When multiple report-action updates are present in the same push payload (common for expense edit flows), this can pick an unrelated action. If that unrelated action appears self-authored, notification gating rejects it and no push is shown.

    // If this comment is from the current user we don't want to parrot whatever they wrote back to them.
    if (action && action.actorAccountID === currentUserAccountID) {
    Log.info(`${tag} No notification because comment is from the currently logged in user`);
    return false;
    }

    Second, unread/notification gating treats lastReadTime === action.created as already read. In modified-expense flows, these timestamps can match at millisecond precision, which suppresses unread state even when the action came from another user.

    if (action && report?.lastReadTime && report.lastReadTime >= action.created) {
    Log.info(`${tag} No notification because the comment was already read`, false, {created: action.created, lastReadTime: report.lastReadTime});

    App/src/libs/ReportUtils.ts

    Lines 8902 to 8907 in a152afa

    const lastVisibleActionCreated = getReportLastVisibleActionCreated(report, oneTransactionThreadReport);
    const lastReadTime = report.lastReadTime ?? '';
    const lastMentionedTime = report.lastMentionedTime ?? '';
    // If the user was mentioned and the comment got deleted the lastMentionedTime will be more recent than the lastVisibleActionCreated
    return lastReadTime < (lastVisibleActionCreated ?? '') || lastReadTime < lastMentionedTime;

    Third, preserving unread by setting lastReadTime to newAction.created - 1ms for each incoming notification can move the unread boundary forward. This can auto-mark older unopened actions as read when a newer action arrives.

    Fourth, LHN unread depends on both lastReadTime and lastVisibleActionCreated. Updating only lastReadTime can still leave LHN unread state inconsistent when lastVisibleActionCreated is stale.

    What changes do you think we should make in order to solve the problem?

    diff --git a/src/libs/ReportActionsUtils.ts b/src/libs/ReportActionsUtils.ts
    @@
     function getLatestReportActionFromOnyxData<TKey extends OnyxKey>(onyxData: Array<OnyxUpdate<TKey>> | null): NonNullable<OnyxEntry<ReportAction>> | null {
         const reportActionUpdate = onyxData?.find((onyxUpdate) => onyxUpdate.key.startsWith(ONYXKEYS.COLLECTION.REPORT_ACTIONS));
    @@
         const reportActions = Object.values((reportActionUpdate.value as ReportActions) ?? {});
         const sortedReportActions = getSortedReportActions(reportActions);
         return sortedReportActions.at(-1) ?? null;
     }
    +
    +/**
    + * @returns The exact report action in `onyxData` matching `reportActionID`, or `null` if not found
    + */
    +function getReportActionFromOnyxData<TKey extends OnyxKey>(onyxData: Array<OnyxUpdate<TKey>> | null, reportActionID: string): NonNullable<OnyxEntry<ReportAction>> | null {
    +    if (!reportActionID) {
    +        return null;
    +    }
    +
    +    const reportActionUpdate = onyxData?.find((onyxUpdate) => {
    +        if (!onyxUpdate.key.startsWith(ONYXKEYS.COLLECTION.REPORT_ACTIONS)) {
    +            return false;
    +        }
    +        const reportActions = (onyxUpdate.value as ReportActions) ?? {};
    +        return reportActionID in reportActions;
    +    });
    +
    +    if (!reportActionUpdate) {
    +        return null;
    +    }
    +
    +    const reportActions = (reportActionUpdate.value as ReportActions) ?? {};
    +    return reportActions[reportActionID] ?? null;
    +}
    @@
     export {
    @@
         getLatestReportActionFromOnyxData,
    +    getReportActionFromOnyxData,
    @@
     };
    diff --git a/src/libs/Notification/PushNotification/shouldShowPushNotification.ts b/src/libs/Notification/PushNotification/shouldShowPushNotification.ts
    @@
    -        const reportAction = ReportActionUtils.getLatestReportActionFromOnyxData(data.onyxData ?? null);
    +        const reportAction =
    +            'reportActionID' in data
    +                ? ReportActionUtils.getReportActionFromOnyxData(data.onyxData ?? null, data.reportActionID) ?? ReportActionUtils.getLatestReportActionFromOnyxData(data.onyxData ?? null)
    +                : ReportActionUtils.getLatestReportActionFromOnyxData(data.onyxData ?? null);
             shouldShow = Report.shouldShowReportActionNotification(String(data.reportID), currentUserAccountID, reportAction, true);
         }
    diff --git a/src/libs/actions/Report/index.ts b/src/libs/actions/Report/index.ts
    @@
    -    if (action && report?.lastReadTime && report.lastReadTime >= action.created) {
    +    if (action && report?.lastReadTime && report.lastReadTime > action.created) {
             Log.info(`${tag} No notification because the comment was already read`, false, {created: action.created, lastReadTime: report.lastReadTime});
             return false;
         }
    @@
     function showReportActionNotification(reportID: string, reportAction: ReportAction, currentUserAccountID: number, currentUserLogin: string) {
    @@
         if (!report) {
             Log.hmmm("[LocalNotification] couldn't show report action notification because the report wasn't found", {localReportID, reportActionID: reportAction.reportActionID});
             return;
         }
    +
    +    // Preserve unread state for remote modified-expense actions while keeping
    +    // both the earliest unread boundary and latest visible action time.
    +    if (reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.MODIFIED_EXPENSE && reportAction.actorAccountID !== currentUserAccountID) {
    +        const reportKey = `${ONYXKEYS.COLLECTION.REPORT}${reportID}` as OnyxKey;
    +        const unreadLastReadTime = DateUtils.subtractMillisecondsFromDateTime(reportAction.created, 1);
    +        const preserveUnreadState = () => {
    +            const latestReport = allReports?.[reportKey] ?? report;
    +            const latestLastReadTime = latestReport?.lastReadTime;
    +            const latestLastVisibleActionCreated = latestReport?.lastVisibleActionCreated ?? '';
    +            const stableLastReadTime = latestLastReadTime && latestLastReadTime < unreadLastReadTime ? latestLastReadTime : unreadLastReadTime;
    +            const stableLastVisibleActionCreated = latestLastVisibleActionCreated > reportAction.created ? latestLastVisibleActionCreated : reportAction.created;
    +            Onyx.merge(reportKey, {lastReadTime: stableLastReadTime, lastVisibleActionCreated: stableLastVisibleActionCreated});
    +        };
    +        preserveUnreadState();
    +        setTimeout(preserveUnreadState, 0);
    +    }
    diff --git a/tests/unit/ReportActionsUtilsTest.ts b/tests/unit/ReportActionsUtilsTest.ts
    @@
     import {
    @@
         getLatestReportActionFromOnyxData,
    +    getReportActionFromOnyxData,
    @@
     } from '../../src/libs/ReportActionsUtils';
    @@
    +    describe('getReportActionFromOnyxData', () => {
    +        it('returns the exact report action by reportActionID when multiple reportActions updates exist', () => {
    +            const targetReportActionID = '90002';
    +            const onyxData = [
    +                {
    +                    key: 'reportActions_1',
    +                    onyxMethod: 'merge',
    +                    value: {
    +                        '90001': {reportActionID: '90001', actionName: CONST.REPORT.ACTIONS.TYPE.ADD_COMMENT, actorAccountID: 100, created: '2026-01-01 00:00:00.000'},
    +                    },
    +                },
    +                {
    +                    key: 'reportActions_2',
    +                    onyxMethod: 'merge',
    +                    value: {
    +                        '90002': {reportActionID: '90002', actionName: CONST.REPORT.ACTIONS.TYPE.MODIFIED_EXPENSE, actorAccountID: 200, created: '2026-01-01 00:00:01.000'},
    +                    },
    +                },
    +            ] as never;
    +
    +            const result = getReportActionFromOnyxData(onyxData, targetReportActionID);
    +            expect(result?.reportActionID).toBe(targetReportActionID);
    +            expect(result?.actorAccountID).toBe(200);
    +        });
    +    });

    Demo

    Screen.Recording.2026-02-26.at.1.30.57.PM.mov

    when we already have one existing unread notification

    Screen.Recording.2026-02-26.at.1.31.19.PM.mov
  11. 48 remaining items

  12. abzokhattab commented on Jun 7, 2026

    @abzokhattab
    Contributor
  13. mallenexpensify commented on Jun 8, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @daledah due $125 via NewDot (requested review but tests weren't completed)
    Contributor+: @abzokhattab due $125 via NewDot (reviewed proposals, followed PR, no tests.

    @abzokhattab , @daledah what cha think?

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Jun 8, 2026
  15. melvin-bot commented on Jun 8, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  16. abzokhattab commented on Jun 8, 2026

    @abzokhattab
    Contributor

    looks good to me @mallenexpensify

  17. daledah commented on Jun 9, 2026

    @daledah
    Contributor
  18. mallenexpensify commented on Jun 15, 2026

    @mallenexpensify
    Contributor

    Thanks @abzokhattab and @daledah , leaving payment summary as-is.

  19. quinthar commented on Jun 29, 2026

    @quinthar
    Contributor

    Approved $125 to @abzokhattab

  20. quinthar commented on Sep 25, 2026

    @quinthar
    Contributor

    Approved $125 to @daledah

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 productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions