[HOLD for payment 2024-11-20] [$125] Add Type column to Expensify Card workspace feeds

[JmillsExpensify]

Problem: We're getting feedback from real customers using workspace feeds, specifically that they get confused what type of card someone has been issued. This is important to solve on NewDot because we've de-coupled the issuance of physical cards from virtual cards; each can be assigned individually, and at separate times.

Solution: Let's add a Type column to the Expensify Cards page in the workspace editor on larger (web) screens. Then given the smaller screen real estate on mobile, let's use the "dot separator" pattern for smaller (mobile) screens.

For the sake of clarity:

• The only acceptable types are Physical or Virtual
• On web, the Type columns appears to the left Last 4 column
• On mobile, the Type appear after the * dot separator behind the card name. If no card name exists (is this possible?), then we only show the type.

The end result looks like this.

Assigning @DylanDylann directly since he's working on this project.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021852303870715636589
• Upwork Job ID: 1852303870715636589
• Last Price Increase: 2024-11-01
• Automatic offers:
• DylanDylann | Reviewer | 104729959
• nkdengineer | Contributor | 104729960

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

Current assignee @JmillsExpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021852303870715636589

[melvin-bot]

Current assignee @DylanDylann is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Upwork job price has been updated to $125

[nkdengineer]

Edited by proposal-police: This proposal was edited at 2024-11-01 11:06:46 UTC.

Proposal

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

What is the root cause of that problem?

new feature

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

1. We should add new props type to WorkspaceCardListRow component

                        isVirtual={item.nameValuePairs?.isVirtual}

2. Add show it in this component

 <View style={[styles.flexRow, styles.gap2, shouldUseNarrowLayout ? styles.flex2 : styles.flex1, styles.alignItemsCenter, styles.justifyContentEnd]}>
                <Text
                    style={[styles.textLabelSupporting, styles.lh16]}
                >
                    {isVirtual ? 'virtual' : 'physical'}
                </Text>
            </View>

3. Add new field in header WorkspaceCardListHeader

                <View style={[styles.flexRow, styles.gap2, shouldUseNarrowLayout ? styles.flex2 : styles.flex1, styles.alignItemsCenter, styles.justifyContentEnd]}>
                    <Text
                        numberOfLines={1}
                        style={[styles.textLabelSupporting, styles.lh16]}
                    >
                        {translate('workspace.expensifyCard.type')}
                    </Text>
                </View>

4. For the mobile screen, we don't show type in row and header and add type in this place

App/src/pages/workspace/expensifyCard/WorkspaceCardListRow.tsx

Line 57 in e597ded

{name}

What alternative solutions did you explore? (Optional)

NA

[nkdengineer]

updated proposal to handle case in small screen and add the result

[JmillsExpensify]

Apologies for the confusion, I removed the Help wanted label since @DylanDylann is working on this project.

[melvin-bot]

📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[melvin-bot]

📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[mountiny]

@DylanDylann will review the PR, @nkdengineer your proposal looks good. Can you please raise the PR?

[nkdengineer]

I'll raise PR soon

[JmillsExpensify]

Thanks @nkdengineer! Sorry for the confusion.

[melvin-bot]

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

[melvin-bot]

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

• fix: Add Type column to workspace feeds #51946

If no regressions arise, payment will be issued on 2024-11-20. 🎊

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

• @DylanDylann requires payment automatic offer (Reviewer)
• @nkdengineer requires payment automatic offer (Contributor)

[melvin-bot]

@DylanDylann @JmillsExpensify @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[DylanDylann]

I will complete the checklist after some style issues are resolved then I can make a regression test completely

[JmillsExpensify]

Payment summary:

• Contributor: @nkdengineer $125 via Upwork
• Reviewer: @DylanDylann $125 via Upwork

[JmillsExpensify]

Upwork offers sent.

[DylanDylann]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production
• 2b. Reported on staging (deploy blocker)
• 2c. Reported on both staging and production
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment: NA. This is a new design

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Test:

1. Go to workspace with Expensify card enabled
2. Create a card
3. Verify that: we have Type column on large screen and a type row on the small screen (below the limit amount)

Do we agree 👍 or 👎

[JmillsExpensify]

@nkdengineer please accept the Upwork offer when you get a chance.

[nkdengineer]

@JmillsExpensify I accepted, thanks.

[JmillsExpensify]

Awesome. All contributors paid out and regression test created.