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:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:
- Add account to workspaceFeeds beta
- Sign in with test account
- Select Manage my team’s expenses
- Enter any business name / personal name
- Navigate to the workspace editor of the newly created workspace
- Navigate to More features tab
- Toggle on the feature
- Navigate to the Expensify Card page
- Select Issue new card, give the user a $2 limit
- Follow the steps for an OPEN bank account (option 3) of this SO
- Finish the setup process
- Issue a card
- Navigate back to the Expensify Card page
Expected Result:
Only see one Expensify Card header.
Actual Result:
Two Expensify Card headers are shown.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos

View all open jobs on GitHub
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:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:
Expected Result:
Only see one
Expensify Cardheader.Actual Result:
Two
Expensify Cardheaders are shown.Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
View all open jobs on GitHub