[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature #21456

amyevans · 2023-06-23T20:41:52Z

Background

We recently added a configurable setting to all default and user-created policy rooms, available to admins only, that allows admins to define who can post in that room: All members or Admins only. This enables admins to "control the conversation" in rooms that have large membership, or for whatever other reason should be lower-noise.

While the bulk of the work is complete, there's some remaining polish to be done on the FE.

Tasks

Add the "Who can post" setting to the "New Room" form

The default form value should be all
Send the writeCapability value when calling the AddWorkspaceRoom endpoint
Ensure the value is included in the optimisticData (to support offline creation)
Note: BE PRs supporting the writeCapability value in the AddWorkspaceRoom endpoint aren't live yet, but don't need to block work here

Filter out admin-only rooms for members in the "Share somewhere" selector of the "Assign task" action (accessible via the FAB menu) - so that members cannot share a task to the room
Reduce the padding between the last message and the bottom of the page when the composer isn't present (e.g. for the "member" view in an admin-only room)
Update the room description to be Use ${roomName} to hear about important announcements related to ${workspaceName} for admin-only rooms

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012ddadecb1f0a54b9
Upwork Job ID: 1675048364496478208
Last Price Increase: 2023-07-01

The text was updated successfully, but these errors were encountered:

melvin-bot · 2023-06-23T20:41:58Z

Triggered auto assignment to @jliexpensify (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

melvin-bot · 2023-06-23T20:42:03Z

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

amyevans · 2023-06-23T20:48:07Z

Internal issue for reference: https://github.com/Expensify/Expensify/issues/282865

I shared in Slack to see if a Callstack team member has capacity for this.

jliexpensify · 2023-06-24T02:37:02Z

LMK if you need any Upworks stuff sorted!

rezkiy37 · 2023-06-26T13:48:25Z

Hi, I'm Michael (Mykhailo) from Callstack and I would like to work in this issue.

rezkiy37 · 2023-06-26T15:07:50Z

@amyevans Hi!
Is it possible to add my Expensify accounts to the white list of Create Policy Room and tasks?

amyevans · 2023-06-26T15:23:29Z

Done

rezkiy37 · 2023-06-27T15:24:00Z

@amyevans I have a question about the last task.
Do you mean to replace entirely?

Before: Collaboration among ${workspaceName} admins starts here! 🎉 Use ${roomName} to chat about topics such as workspace configurations and more.
After: Use ${roomName} to hear about important announcements related to ${workspaceName}.

amyevans · 2023-06-27T15:34:27Z

Collaboration among ${workspaceName} admins starts here! 🎉 Use ${roomName} to chat about topics such as workspace configurations and more.

This is the copy for the #admins room, and the #admins room is something different - it is one of 2 rooms created by default when you create a new workspace aka policy (#announce being the other default room). The purpose of the #admins room is for collaboration between admins. Users who are members of the policy (but not admins of the policy) are not in the #admins room.

Then we have this feature we're working on here, which is any room that is restricted to only admins posting (but plenty of non-admins are in the room). Check out the screen recordings/code in #19094 for more context. So we'll want to insert a new condition here-ish:

App/src/libs/ReportUtils.js

Line 571 in 5c6b751

} else if (isDomainRoom(report)) {

that checks if it's a room where only admins can post and then spits out Use ${roomName} to hear about important announcements related to ${workspaceName}.

Does that make sense?

rezkiy37 · 2023-06-27T16:37:11Z

@amyevans Thank you for your answer.
Just to clarify:

The #admins room is the policyAdmins chat type.

isAdminRoom verifies it of getRoomWelcomeMessage.

App/src/libs/ReportUtils.js

Lines 574 to 576 in 5c6b751

    
           } else if (isAdminRoom(report)) { 
        
               welcomeMessage.phrase1 = Localize.translateLocal('reportActionsView.beginningOfChatHistoryAdminRoomPartOne', {workspaceName}); 
        
               welcomeMessage.phrase2 = Localize.translateLocal('reportActionsView.beginningOfChatHistoryAdminRoomPartTwo');

phrase1 should be Use . Because ${roomName} should be presseble to navigate.

App/src/components/ReportWelcomeText.js

Lines 83 to 94 in 5c6b751

    
           {isChatRoom && ( 
        
               <> 
        
                   <Text>{roomWelcomeMessage.phrase1}</Text> 
        
                   <Text 
        
                       style={[styles.textStrong]} 
        
                       onPress={() => Navigation.navigate(ROUTES.getReportDetailsRoute(props.report.reportID))} 
        
                   > 
        
                       {ReportUtils.getReportName(props.report)} 
        
                   </Text> 
        
                   <Text>{roomWelcomeMessage.phrase2}</Text> 
        
               </> 
        
           )}

phrase2 should be to hear about important announcements related to ${workspaceName}.

Correct me if I am wrong 🙂

amyevans · 2023-06-27T17:15:15Z

The #admins room is the policyAdmins chat type.

Yep! (But again, that isn't the room we're talking about in this feature at all.)

isAdminRoom verifies it of getRoomWelcomeMessage.

App/src/libs/ReportUtils.js

Lines 574 to 576 in 5c6b751

} else if (isAdminRoom(report)) {

welcomeMessage.phrase1 = Localize.translateLocal('reportActionsView.beginningOfChatHistoryAdminRoomPartOne', {workspaceName});

welcomeMessage.phrase2 = Localize.translateLocal('reportActionsView.beginningOfChatHistoryAdminRoomPartTwo');

This doesn't directly answer your question, but more to point of what to do here, we'll want to create a new helper function:

function isAdminsOnlyPostingRoom(report) {
    const capability = lodashGet(report, 'writeCapability', CONST.REPORT.WRITE_CAPABILITIES.ALL) || CONST.REPORT.WRITE_CAPABILITIES.ALL;
    return capability === CONST.REPORT.WRITE_CAPABILITIES.ADMINS;
}

and use that function in a new condition in this logic:

} else if (isAdminsOnlyPostingRoom(report)) {
...
}

phrase1 should be Use . Because ${roomName} should be presseble to navigate.

App/src/components/ReportWelcomeText.js

Lines 83 to 94 in 5c6b751

{isChatRoom && (

<>

<Text>{roomWelcomeMessage.phrase1}</Text>

<Text

style={[styles.textStrong]}

onPress={() => Navigation.navigate(ROUTES.getReportDetailsRoute(props.report.reportID))}

>

{ReportUtils.getReportName(props.report)}

</Text>

<Text>{roomWelcomeMessage.phrase2}</Text>

</>

)}

phrase2 should be to hear about important announcements related to ${workspaceName}.

Good point about why we separate out the phrases. That looks correct, thanks!

rezkiy37 · 2023-06-27T17:55:59Z

@amyevans Got it. Thank you!

rezkiy37 · 2023-06-29T10:08:39Z

Proposal

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

This is a feature issue. It has 4 tasks. Anyway, it resolves some user problems too:

Provides new functionality - "Who can post" setting during creating a new room.
Restricts to share "Assign task" in admin-only rooms if a current user is not admin itself.
Reduces the spacing between the last message and the bottom of the page when Composer isn't present.
Updates message the welcome message for admin-only rooms.

What is the root cause of that problem?

Add the "Who can post" setting to the "New Room" form.
- The default form value should be all.
- Send the writeCapability value when calling the AddWorkspaceRoom endpoint.
- Ensure the value is included in the optimisticData (to support offline creation).
- Note: BE PRs supporting the writeCapability value in the AddWorkspaceRoom endpoint aren't live yet, but don't need to block work here.
Filter out admin-only rooms for members in the "Share somewhere" selector of the "Assign task" action (accessible via the FAB menu) - so that members cannot share a task to the room.
Reduce the padding between the last message and the bottom of the page when Composer isn't present (e.g. for the "member" view in an admin-only room).
Update the room description to be Use ${roomName} to hear about important announcements related to ${workspaceName} for admin-only rooms.

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

Add the “Who can post” setting to the “New Room” form.
a. WorkspaceNewRoomPage component.
1. Add writeCapabilityOptions of render method. The array is mapped of all write capabilities. The map returns the array of objects: value (capability itself) and label (reuse already existed strings).
```
const writeCapabilityOptions = _.map(CONST.REPORT.WRITE_CAPABILITIES, (value) => ({
    value,
    label: this.props.translate(`writeCapabilityPage.writeCapability.${value}`),
}));
```
1. Add one more Picker after RoomNameInput, because I consider to follow the same order of pickers as in ReportSettingsPage. It should reuse already existed title (Who can post). The default value should be - CONST.REPORT.WRITE_CAPABILITIES.ALL (all). It takes items (values) from writeCapabilityOptions.
2. Change bottom spacing of workspaces Picker Wrapper (View) from mb5 to mb2 to keep consistency between them.
3. Apply destructuring assignment of values of submit method. Because, the method always uses chains to get each value.
4. Take and pass writeCapability to Report.addPolicyReport(…, writeCapability) in the submit method.
b. addPolicyReport function of Report.js.
1. Takes writeCapability as the last argument.
2. Passes the argument after visibility to ReportUtils.buildOptimisticChatReport(…, writeCapability, ...).
3. Passes the argument to API.write(‘AddWorkspaceRoom’, {…, writeCapability}).
c. buildOptimisticChatReport function of ReportUtils.js.
1. Takes writeCapability after visibility with the default value - CONST.REPORT.WRITE_CAPABILITIES.ALL (all).
2. Returns writeCapability inside the returned object.
Filter out admin-only rooms for members in the “Share somewhere” selector of the “Assign task” action (accessible via the FAB menu) - so that members cannot share a task to the room.
a. shouldReportBeInOptionList function of ReportUtils.js.
1. Takes one more argument - isShareDestination (the default value - false). Since, this function is being used across other places and other list of reports, I should apply changes only for the “Share somewhere” selector.
2. Add one more condition before the final return. When isShareDestination is true and writeCapability equals admin-only, the app should verify that a current user can post to a report. Find linkedWorkspace by policy.id and report.policyID. Then, check a role of the current user for this workspace. The role should be equal admin to allow the user to share to this report, otherwise this report is out of the list.
```
if (isShareDestination && report.writeCapability === CONST.REPORT.WRITE_CAPABILITIES.ADMINS) {
    const linkedWorkspace = _.find(policies, (policy) => policy && policy.id === report.policyID);
    const shouldAllowShare = lodashGet(linkedWorkspace, 'role', '') === CONST.POLICY.ROLE.ADMIN;

    return shouldAllowShare;
}
```
b. getOptions function of OptionsListUtils.js.
1. Takes one more value of options object. It is isShareDestination (the default value - false). Since, this function is being used across other places and other list of reports, I should apply changes only for the “Share somewhere” selector.
2. Passes the value to ReportUtils.shouldReportBeInOptionList(…, isShareDestination).
c. getShareDestinationOptions function of OptionsListUtils.js.
1. Passes isShareDestination to getOptions(..., {..., isShareDestination: true}).

Reduce the padding between the last message and the bottom of the page when Composer isn’t present (e.g. for the “member” view in an admin-only room).
a. Add pb0 (paddingBottom: 0) to spacing.js.
b. Apply styles.pb0 to View with styles.p5 of ReportActionItemCreated, when no other messages and Composer is hidden.

To understand that there is no messages yet, I would use lastMessageText of report and compare with an empty string.
To understand that Composer is hidden, I would apply the same conditions as inside ReportFooter.

const errors = lodashGet(props.report, 'errorFields.addWorkspaceRoom') || lodashGet(props.report, 'errorFields.createChat');
const isArchivedRoom = ReportUtils.isArchivedRoom(props.report);
const hideComposer = ReportUtils.shouldHideComposer(props.report, errors);
const shouldOmitBottomSpace = props.report.lastMessageText === '' && (isArchivedRoom || hideComposer);

<View
    accessibilityLabel={props.translate('accessibilityHints.chatWelcomeMessage')}
    // Apply the condition here
    style={[styles.p5, shouldOmitBottomSpace && styles.pb0, StyleUtils.getReportWelcomeTopMarginStyle(props.isSmallScreenWidth)]}
>

Update the room description to be Use ${roomName} to hear about important announcements related to ${workspaceName} for admin-only rooms.
a. reportActionsView of en.js.
1. Add beginningOfChatHistoryAdminOnlyPostingRoomPartOne - "Use ".
2. Add beginningOfChatHistoryAdminOnlyPostingRoomPartTwo like a method to pass workspaceName - " to hear about important announcements related to ${workspaceName}".
  b. ReportUtils.js
3. Create a function - isAdminsOnlyPostingRoom. It takes report and gets writeCapability or use default value - all. It compares writeCapability with admins to verify that only admins can post here.
```
function isAdminsOnlyPostingRoom(report) {
    const writeCapability = lodashGet(report, 'writeCapability', CONST.REPORT.WRITE_CAPABILITIES.ALL);

    return writeCapability === CONST.REPORT.WRITE_CAPABILITIES.ADMINS;
}
```
1. Add one more else if to getRoomWelcomeMessage. It should use the new isAdminsOnlyPostingRoom function. When it returns true, it sets the first string (beginningOfChatHistoryAdminOnlyPostingRoomPartOne) to phrase1 and the second string (beginningOfChatHistoryAdminOnlyPostingRoomPartTwo) to phrase2.

What alternative solutions did you explore?

Reduce the padding between the last message and the bottom of the page when Composer isn’t present (e.g. for the “member” view in an admin-only room).
a. Remove wrapper of OfflineIndicator of ReportFooter. Remove styles.offlineIndicatorRow, because no wrapper anymore. The wrapper has a static height and is being rendered always on large screens. No sense to keep this empty wrapper when users are online.

rezkiy37 · 2023-06-29T10:11:41Z

The 1st task example:

1.mov

rezkiy37 · 2023-06-29T10:15:39Z

The 2nd task example:

2.mp4

rezkiy37 · 2023-06-29T10:16:20Z

The 3rd task example:

rezkiy37 · 2023-06-29T10:16:47Z

The 4th task example:

amyevans · 2023-06-29T23:08:06Z

Thanks for writing that out as a detailed proposal! I haven't had the opportunity to review it yet and will eventually want a C+ to help with the PR review, so going to pull 1 in now for proposal review as well, so that you won't be blocked.

Asked in Slack for a volunteer.

mananjadhav · 2023-06-30T11:12:52Z

Thanks for the detailed proposal @rezkiy37. Took sometime to go through all the points. Your proposal looks good.

cc - @amyevans

🎀 👀 🎀 C+ reviewed.

melvin-bot · 2023-06-30T11:12:59Z

Triggered auto assignment to @NikkiWines, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

rezkiy37 · 2023-06-30T13:06:55Z

@amyevans Hi!
Could you please provide me translations for Use ${roomName} to hear about important announcements related to ${workspaceName} in Spanish.

rezkiy37 · 2023-07-31T13:20:36Z

@amyevans, @mananjadhav, I've opened a PR for review - #23919.

jliexpensify · 2023-08-01T02:25:08Z

Payment summary:

Contributor: @rezkiy37 $500 (due to regression) - Callstack, to invoice serparately
C+: @mananjadhav $125 (due to regression) - New.Dot payment

No Upworks job created

mananjadhav · 2023-08-01T03:43:24Z

@jliexpensify The payout for me will be 125$, as there are two regressions and the payout date will change as the PR for the second regression is still open.

melvin-bot · 2023-08-01T23:46:33Z

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot · 2023-08-01T23:46:38Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.48-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Fix/21456 - Polish admins-only policy room - Pass arguments properly #23815

If no regressions arise, payment will be issued on 2023-08-08. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

@mananjadhav does not require payment (Eligable for Manual Requests)
@rezkiy37 does not require payment (Contractor)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

melvin-bot · 2023-08-07T18:15:13Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.50-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Fix/23818 - Polish admins-only policy room - Clear "Form's" states correctly #23919

If no regressions arise, payment will be issued on 2023-08-14. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

@mananjadhav does not require payment (Eligable for Manual Requests)
@rezkiy37 does not require payment (Contractor)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

mananjadhav · 2023-08-11T18:51:17Z

There won't be any offending PR because this was more of a feature request. About regressions steps, @amyevans Can you confirm if these are added during the feature design?

amyevans · 2023-08-11T22:24:52Z

About regressions steps, @amyevans Can you confirm if these are added during the feature design?

Good reminder, I haven't put in the request for new regression tests yet but I will Monday!

jliexpensify · 2023-08-14T01:47:02Z

Payment summary here (to save me/JMills/Anu scrolling up)

amyevans · 2023-08-14T23:19:33Z

Regression tests GH created: https://github.com/Expensify/Expensify/issues/308182

I think we're set to proceed with payment today!

jliexpensify · 2023-08-15T11:56:12Z

Cool, so there isn't anything to pay in Upworks - @mananjadhav is getting paid in New.Dot and @rezkiy37 is invoicing us.

@amyevans are you happy to close this one, if everything is done?

amyevans · 2023-08-15T13:25:34Z

Sure, I wasn't sure if we had to keep it open until the payment was made in NewDot. Closing now!

JmillsExpensify · 2023-08-15T16:50:56Z

Reviewed the details for @mananjadhav. Approved for payment in NewDot based on BZ summary above.

amyevans added Weekly KSv2 NewFeature Something to build that is a new item. labels Jun 23, 2023

amyevans self-assigned this Jun 23, 2023

melvin-bot bot assigned jliexpensify Jun 23, 2023

melvin-bot bot assigned shawnborton Jun 23, 2023

amyevans assigned rezkiy37 Jun 26, 2023

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Jun 29, 2023

melvin-bot bot assigned NikkiWines Jun 30, 2023

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jul 31, 2023

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Aug 1, 2023

melvin-bot bot changed the title ~~[HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature~~ [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature Aug 1, 2023

melvin-bot bot removed the Reviewing Has a PR in review label Aug 1, 2023

melvin-bot bot added Daily KSv2 Overdue Weekly KSv2 and removed Weekly KSv2 Daily KSv2 labels Aug 3, 2023

melvin-bot bot changed the title ~~[HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature~~ [HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature Aug 7, 2023

melvin-bot bot removed the Overdue label Aug 7, 2023

amyevans added Daily KSv2 and removed Weekly KSv2 Help Wanted Apply this label when an issue is open to proposals by contributors labels Aug 14, 2023

amyevans closed this as completed Aug 15, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature #21456

[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature #21456

amyevans commented Jun 23, 2023 •

edited by melvin-bot bot

Loading

melvin-bot bot commented Jun 23, 2023

melvin-bot bot commented Jun 23, 2023

amyevans commented Jun 23, 2023

jliexpensify commented Jun 24, 2023

rezkiy37 commented Jun 26, 2023

rezkiy37 commented Jun 26, 2023 •

edited

Loading

amyevans commented Jun 26, 2023

rezkiy37 commented Jun 27, 2023 •

edited

Loading

amyevans commented Jun 27, 2023

rezkiy37 commented Jun 27, 2023 •

edited

Loading

amyevans commented Jun 27, 2023

rezkiy37 commented Jun 27, 2023

rezkiy37 commented Jun 29, 2023 •

edited

Loading

rezkiy37 commented Jun 29, 2023

rezkiy37 commented Jun 29, 2023

rezkiy37 commented Jun 29, 2023

rezkiy37 commented Jun 29, 2023

amyevans commented Jun 29, 2023 •

edited

Loading

mananjadhav commented Jun 30, 2023

melvin-bot bot commented Jun 30, 2023

rezkiy37 commented Jun 30, 2023

rezkiy37 commented Jul 31, 2023

jliexpensify commented Aug 1, 2023 •

edited

Loading

mananjadhav commented Aug 1, 2023 •

edited

Loading

melvin-bot bot commented Aug 1, 2023

melvin-bot bot commented Aug 1, 2023

melvin-bot bot commented Aug 7, 2023

mananjadhav commented Aug 11, 2023

amyevans commented Aug 11, 2023

jliexpensify commented Aug 14, 2023 •

edited

Loading

amyevans commented Aug 14, 2023

jliexpensify commented Aug 15, 2023

amyevans commented Aug 15, 2023

JmillsExpensify commented Aug 15, 2023

[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature #21456

[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-03] [$1000] Polish admins-only policy room feature #21456

Comments

amyevans commented Jun 23, 2023 • edited by melvin-bot bot Loading

Background

Tasks

melvin-bot bot commented Jun 23, 2023

melvin-bot bot commented Jun 23, 2023

amyevans commented Jun 23, 2023

jliexpensify commented Jun 24, 2023

rezkiy37 commented Jun 26, 2023

rezkiy37 commented Jun 26, 2023 • edited Loading

amyevans commented Jun 26, 2023

rezkiy37 commented Jun 27, 2023 • edited Loading

amyevans commented Jun 27, 2023

rezkiy37 commented Jun 27, 2023 • edited Loading

amyevans commented Jun 27, 2023

rezkiy37 commented Jun 27, 2023

rezkiy37 commented Jun 29, 2023 • edited Loading

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore?

rezkiy37 commented Jun 29, 2023

The 1st task example:

rezkiy37 commented Jun 29, 2023

The 2nd task example:

rezkiy37 commented Jun 29, 2023

The 3rd task example:

rezkiy37 commented Jun 29, 2023

The 4th task example:

amyevans commented Jun 29, 2023 • edited Loading

mananjadhav commented Jun 30, 2023

melvin-bot bot commented Jun 30, 2023

rezkiy37 commented Jun 30, 2023

rezkiy37 commented Jul 31, 2023

jliexpensify commented Aug 1, 2023 • edited Loading

mananjadhav commented Aug 1, 2023 • edited Loading

melvin-bot bot commented Aug 1, 2023

melvin-bot bot commented Aug 1, 2023

melvin-bot bot commented Aug 7, 2023

mananjadhav commented Aug 11, 2023

amyevans commented Aug 11, 2023

jliexpensify commented Aug 14, 2023 • edited Loading

amyevans commented Aug 14, 2023

jliexpensify commented Aug 15, 2023

amyevans commented Aug 15, 2023

JmillsExpensify commented Aug 15, 2023

amyevans commented Jun 23, 2023 •

edited by melvin-bot bot

Loading

rezkiy37 commented Jun 26, 2023 •

edited

Loading

rezkiy37 commented Jun 27, 2023 •

edited

Loading

rezkiy37 commented Jun 27, 2023 •

edited

Loading

rezkiy37 commented Jun 29, 2023 •

edited

Loading

amyevans commented Jun 29, 2023 •

edited

Loading

jliexpensify commented Aug 1, 2023 •

edited

Loading

mananjadhav commented Aug 1, 2023 •

edited

Loading

jliexpensify commented Aug 14, 2023 •

edited

Loading