Skip to content

[No QA] Docs updates for E/A#98849 document bulk Download receipts in Search - #98890

Merged
RachCHopkins merged 2 commits into
mainfrom
docs/download-receipts-search-98849
Aug 28, 2026
Merged

RachCHopkins merged 2 commits into
mainfrom
docs/download-receipts-search-98849

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Docs updates for E/A#98849

This help-site PR documents the bulk Download receipts action in Search, which Expensify/App#98849 fixed. That PR gates Download receipts on receipt presence when reports/expenses are selected on the Spend > Reports and Spend > Expenses pages, and excludes deleted expenses from the export. The help site previously documented Download receipts only for the single-report More menu flow, so the bulk-selection behavior this PR changed was undocumented.

Changes

How-to-Export-Reports.md

  • Added How to download the receipts on multiple reports (select reports on Spend > Reports → Selected → Download receipts), with a note that the option only appears when at least one selected report has an expense with a receipt.
  • Updated the FAQ Why don't I see Download receipts on a report? to cover both the single-report More menu and the multi-report Selected flow.
  • Updated keywords / internalScope to reflect bulk receipt download.

How-to-Export-Expenses.md

  • Added How to download the receipts on selected expenses (select expenses on Spend > Expenses → Selected → Download receipts), with a note that the option only appears when at least one selected expense has a receipt and that deleted expenses are excluded.
  • Added two FAQs: Why don't I see Download receipts for my selected expenses? and Are deleted expenses included when I download receipts?
  • Updated description / keywords / internalScope to include receipt download.

Verification notes

  • Label Download receipts and empty-state No receipts to download confirmed against src/languages/en.ts.
  • Left-nav Spend section with Reports and Expenses tabs confirmed against the live web UI. The bulk-selection Selected button and menu could not be exercised live because the test account had no reports/expenses; the Selected wording matches the existing sibling sections in these same two articles and the PR's own test steps.

Fixed Issues

$ #98833
$ #98827

@truph01, 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.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Aug 18, 2026
@MelvinBot

Copy link
Copy Markdown
Contributor Author

The only failing check on this PR is Check independent approval (run), and there's nothing to fix in the code.

That check isn't a build/test failure — it's a process gate that stays red until the PR receives an independent human review approval. It can't be resolved by a commit or a MelvinBot push; it clears once a reviewer approves.

Every actual CI check is green or still running:

  • check, verify, verifySignedCommits, validate, spellcheck, dryRun, CLA → ✅ pass
  • build → still pending (running, not failed)

Next step: this PR just needs a reviewer to approve it — no code change is required from me.

@github-actions github-actions Bot changed the title Docs updates for E/A#98849 document bulk Download receipts in Search [No QA] Docs updates for E/A#98849 document bulk Download receipts in Search Aug 18, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

@truph01

truph01 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@MelvinBot mark this PR as ready

1 similar comment
@truph01

truph01 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@MelvinBot mark this PR as ready

@MelvinBot
MelvinBot marked this pull request as ready for review August 25, 2026 09:49
@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ Marked this PR as ready for review.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ This PR is already marked as ready for review (out of draft).


view run

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR adds bulk receipt-download workflows to two existing export articles: a new "How to download the receipts on selected expenses" section (plus two FAQs) in How-to-Export-Expenses.md, and a new "How to download the receipts on multiple reports" section (plus a clarified FAQ) in How-to-Export-Reports.md. Metadata was updated in both files to reflect the expanded scope. The added content is high quality and closely follows the governance standards.

Scores Summary

  • Readability: 9/10 - Steps are sequential, action-oriented, and scannable. Sentences are clear and concise, and the Note: callouts set expectations well.
  • AI Readiness: 9/10 - New sections use task-based headings starting with How to / Why / Are. internalScope and keywords were updated to match the new workflows and real search phrasing (download receipts, receipt zip). Heading hierarchy stays within one top-level heading plus H2s.
  • Style Compliance: 9/10 - UI labels are bolded and match the product exactly (Spend, Expenses, Reports, Selected, Download receipts, Download file). Navigation uses the approved unified web/mobile phrasing. The reworked Reports FAQ correctly distinguishes the single-report More menu path from the multi-select Selected path.

Key Findings

  • Strong consistency: the new bulk receipt sections mirror the structure of the existing bulk-export/PDF sections, reinforcing the primary workflow rather than expanding scope.
  • Metadata quality: internalScope accurately extends coverage (bulk receipt download) while preserving explicit exclusions and the cross-reference between the two articles.
  • Minor: In How-to-Export-Expenses.md, the FAQ-style questions (including the two new ones) are H2 sections directly under the single title with no dedicated FAQ heading, unlike How-to-Export-Reports.md which uses a FAQ section. This is pre-existing structure, not introduced by this diff, but worth aligning across the two sibling articles.
  • Minor: The two files bold the Spend breadcrumb arrow differently. Not a violation, but consider standardizing.

Recommendations

  • (Optional) Standardize FAQ structure so both sibling articles use the same pattern.
  • (Optional) Standardize the Spend > Reports / Spend > Expenses breadcrumb bolding across both files.
  • No blocking issues; the added content is publish-ready against the governance criteria.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/How-to-Export-Expenses.md - Added bulk receipt-download section + 2 FAQs; metadata updated. Compliant.
  • docs/articles/new-expensify/reports-and-expenses/How-to-Export-Reports.md - Added multi-report receipt-download section; clarified receipts FAQ; metadata updated. Compliant.

Note: This is a top-level summary; the observations above apply to the added/modified lines only.

@stephanieelliott
stephanieelliott requested a review from a team August 27, 2026 05:45
@melvin-bot

melvin-bot Bot commented Aug 27, 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 @RachCHopkins

@melvin-bot

melvin-bot Bot commented Aug 27, 2026

Copy link
Copy Markdown

@truph01 @daledah @RachCHopkins 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 August 27, 2026 05:45

@RachCHopkins RachCHopkins 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

@RachCHopkins
RachCHopkins merged commit 4ce3320 into main Aug 28, 2026
14 of 15 checks passed
@RachCHopkins
RachCHopkins deleted the docs/download-receipts-search-98849 branch August 28, 2026 04:53
@OSBotify OSBotify mentioned this pull request Aug 28, 2026
45 tasks done
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/RachCHopkins in version: 9.4.64-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 9.4.64-3 🚀

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.

5 participants