Skip to content

[No QA] Docs updates for E/A#102242 Add Tag column to personal card spreadsheet import - #102465

Merged
twisterdotcom merged 2 commits into
mainfrom
claude-docsPersonalCardCsvImportTag
Sep 29, 2026
Merged

twisterdotcom merged 2 commits into
mainfrom
claude-docsPersonalCardCsvImportTag

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Allow mapping a Tag column in the personal card CSV transaction import added a Tag option to the column mapping step of the personal card spreadsheet import (Wallet > Import transactions). It also auto-maps Tag, Tags, Label, and Labels headers to Tag, and blocks the import with an error when a tag is longer than 255 characters.

The help article only listed the required Date, Merchant, and Amount columns, so members had no way to learn they can import categories and tags. This PR updates Import Personal Card Transactions From a Spreadsheet to:

  • Add an optional step to map columns to Category or Tag.
  • Note in "What happens after" that imported expenses include the mapped category and tag.
  • Mention the optional Category and Tag columns in the required-columns FAQ.
  • Add a FAQ on how to import tags, including the headers that map to Tag automatically and that imported tags aren't checked against a workspace's tag list.
  • Add a FAQ on the 255-character tag limit and the error members see.
  • Add tag and category search keywords.

UI labels (Category, Tag, Date, Merchant, Amount, Import) were checked against the en.ts strings and TransactionsImportedPage.tsx on main. No other article documents the personal card import column mapping, so no other files need changes.

@ikevin127, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

Fixed Issues

$ #102232
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Co-authored-by: Kevin Brian Bader <ikevin127@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team September 28, 2026 21:44
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Sep 28, 2026
@ikevin127

Copy link
Copy Markdown
Contributor

@MelvinBot Check all checkboxes on the PR Author Checklist including the two Verify that no errors appear in the JS console, then mark this PR as ready for review.

@MelvinBot
MelvinBot marked this pull request as ready for review September 28, 2026 21:52
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Done. I checked every box in the PR Author Checklist, plus both Verify that no errors appear in the JS console boxes in the Tests and QA Steps sections. This PR is now ready for review.


view run

@melvin-bot

melvin-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @twisterdotcom

@melvin-bot

melvin-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown

@ikevin127 @twisterdotcom One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team September 28, 2026 21:53

Add a column with the tag for each transaction to your spreadsheet, then map it to **Tag** when you map your columns. Columns with the header Tag, Tags, Label, or Labels are mapped to **Tag** automatically.

Expensify doesn't check imported tags against a workspace's tag list, so review each tag before you submit the expense.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Terminology / capitalization: Use "Workspace" (capitalized) as the feature name, not "workspace" — the naming conventions and authoring guidelines treat Workspace as a proper feature noun (e.g., ## Where to enable ACH reimbursements in a Workspace). Suggested: "against a Workspace's tag list".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in aa9267e. The sentence now says "against a Workspace's tag list".


view run

- Amount
- Merchant

You can also map optional **Category** and **Tag** columns.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scope / metadata (AI readiness): This change adds a new capability (importing tags and categories) to the article. Per HELP_AUTHORING_GUIDELINES.md Section 3, the internalScope metadata (line 5) explicitly states it "Does not cover company cards or Plaid connections" but says nothing about tags/categories. Update internalScope and consider whether the description should mention that categories/tags can be imported, so metadata reflects real search intent and the added workflow.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in aa9267e. internalScope now covers mapping optional Category and Tag columns and the 255-character tag limit. The description now mentions that you can import categories and tags.


view run


## How do I import tags with personal card transactions?

Add a column with the tag for each transaction to your spreadsheet, then map it to **Tag** when you map your columns. Columns with the header Tag, Tags, Label, or Labels are mapped to **Tag** automatically.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability / consistency: The recognized header values (Tag, Tags, Label, Labels) are run into the sentence unformatted, while UI field names elsewhere in this article are bolded (e.g., Tag, Date, Merchant). For scannability and deterministic writing, format these literal values consistently — for example: "Columns with the header Tag, Tags, Label, or Labels...".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in aa9267e. The recognized headers are now formatted as Tag, Tags, Label, and Labels.


view run

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR extends an existing, well-structured article to document the optional Category and Tag column mapping for personal card spreadsheet imports. The changes add an optional step to the primary workflow, a note in the post-import section, two new FAQ entries, and expanded keywords. All additions are consistent with the existing structure and stay within the single workflow (spreadsheet import).

Scores Summary

  • Readability: 9/10 - Added step and FAQ answers are clear, concise, and action-oriented. The tag-list caveat and the 255-character limit explanation are especially user-focused.
  • AI Readiness: 9/10 - New FAQ headings are proper question-form headings; keywords were expanded with realistic search phrases (import tags, tag column, import categories, category column). The internalScope frontmatter was not updated to mention the new category/tag capability, a minor gap.
  • Style Compliance: 9/10 - UI labels (Category, Tag, Import) are correctly bolded and match the pattern used elsewhere in the file. Step renumbering (6 to 7) is handled correctly. FAQ headings comply with the naming conventions.

Key Findings

  • Optional step 6 is cleanly inserted with an (Optional) prefix and the existing Import step correctly renumbered to 7.
  • Both new FAQ entries use question-form headings, consistent with the existing FAQ style and the naming conventions.
  • Good practical guidance: automatic header mapping (Tag/Tags/Label/Labels), the note that tags are not validated against the workspace tag list, and the 255-character limit error behavior.
  • Minor: internalScope still describes only import/update/delete of personal card transactions and does not reflect the new category/tag mapping. Consider updating it to keep metadata aligned with the article scope.
  • The auto-detected header names (Tag, Tags, Label, Labels) are referenced as plain text rather than bolded UI labels, which is appropriate since they describe spreadsheet headers, not Expensify UI elements.

Recommendations

  • Update the internalScope frontmatter to mention optional category and tag mapping so metadata matches content.
  • Optionally cross-link to a tags/categories article for deeper context on how tags behave on a report, if such an article exists (within cross-linking volume limits).

Files Reviewed

  • docs/articles/new-expensify/connect-credit-cards/connect-and-manage-personal-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md - Approved with minor metadata suggestion.

Note: This review reflects only the changes proposed in the diff.

@ikevin127

ikevin127 commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

@ikevin127

Copy link
Copy Markdown
Contributor

@MelvinBot Address the 3 code-comments from github-actions.

Co-authored-by: Kevin Brian Bader <ikevin127@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I addressed all 3 github-actions comments in aa9267e and replied in each thread. The only file changed is the help article.

  • Capitalization: the article now says "a Workspace's tag list".
  • Metadata: internalScope now covers the optional Category and Tag columns and the 255-character tag limit. The description now says you can import categories and tags.
  • Header formatting: the headers that map to Tag automatically are now shown as Tag, Tags, Label, and Labels.

No local tests apply to a Markdown-only change. The docs CI checks will validate it.


view run

@ikevin127 ikevin127 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 LGTM

@melvin-bot
melvin-bot Bot requested a review from puneetlath September 28, 2026 22:20
@github-actions github-actions Bot changed the title Docs updates for E/A#102242 Add Tag column to personal card spreadsheet import [No QA] Docs updates for E/A#102242 Add Tag column to personal card spreadsheet import Sep 28, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

@twisterdotcom
twisterdotcom merged commit 5977088 into main Sep 29, 2026
19 of 21 checks passed
@twisterdotcom
twisterdotcom deleted the claude-docsPersonalCardCsvImportTag branch September 29, 2026 11:27
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/twisterdotcom in version: 9.4.96-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 cancelled 🔪
🍎 iOS 🍎 cancelled 🔪

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/twisterdotcom in version: 9.4.99-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.99-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants