Skip to content

[No QA] Update help docs for Release 1: Export current view#94945

Merged
flaviadefaria merged 1 commit into
mainfrom
claude-exportCurrentViewHelpDocs
Jul 7, 2026
Merged

[No QA] Update help docs for Release 1: Export current view#94945
flaviadefaria merged 1 commit into
mainfrom
claude-exportCurrentViewHelpDocs

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

Documents the new Current view export option (Release 1 of the "Support exporting users' filtered views" project), which lets users export exactly what they see on the Spend page — active filters, column configuration, and ordering — as a CSV.

Getting-Started-with-the-Spend-Page.md

  • Promoted the filtering sections out of # Report Tables into their own top-level # Filters section (and split # Smart Suggestions into its own section too), since filtering and exporting are Spend-page behaviors, not Report Tables behaviors.
  • Added a ## How to export from the Spend page section directly below ## How filtering works on the Spend page, framed as exporting the current filtered view to CSV, including the file naming convention (Expensify_<current_view>_<unique id>.csv) and the Concierge delivery choice.
  • Updated the FAQ "Can I export reports from the Spend page?" to reference the Current view option.

Search-and-Download-Expenses.md

  • Added an # Export your current filtered view section documenting where to find the option (the Export menu on the Spend page), what it exports (active filters, columns, ordering), the file naming convention, and the wait-or-Concierge delivery choice.
  • Renamed the existing "Export current view" references to Current view, matching the current UI where the option is nested inside the Export menu.

This is a docs-only change. The scope was reviewed and approved by flaviadefaria in the tracking issue.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/633157
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

N/A — documentation-only change.

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

Screenshots/Videos

N/A — documentation-only change.

Co-authored-by: flaviadefaria <flaviadefaria@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team June 30, 2026 09:29
@github-actions github-actions Bot changed the title Update help docs for Release 1: Export current view [No QA] Update help docs for Release 1: Export current view Jun 30, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

@melvin-bot

melvin-bot Bot commented Jul 2, 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 @Kel-Expensify

@melvin-bot melvin-bot Bot requested a review from Kel-Expensify July 2, 2026 10:42
@melvin-bot

melvin-bot Bot commented Jul 2, 2026

Copy link
Copy Markdown

@Kel-Expensify Please 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 July 2, 2026 10:42

---

# Filters

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.

Heading structure violation: Only one # heading (the article title) plus an optional # FAQ is allowed (HELP_AUTHORING_GUIDELINES.md Section 4). This adds an extra # heading. It's also a noun-only/topic label, which is forbidden (Section 2). Demote to a task-based ## heading, e.g. ## How to filter the Spend page, or remove it since ## How to apply filters in New Expensify already covers this.


---

# Smart Suggestions

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.

Heading structure violation: Extra # heading not allowed — only one # title plus optional # FAQ (HELP_AUTHORING_GUIDELINES.md Section 4). Smart Suggestions is also a noun-only/topic label, which is forbidden (Section 2). Remove it; the following ## How to use Smart Suggestions already serves as the task-based section heading.


## Can I export reports from the Spend page?
Yes! You can [export filtered reports to CSV](https://help.expensify.com/articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses) using the export option at the top of the Spend page.
Yes! Choose the **Current view** option within the **Export** menu to download a CSV of exactly what you're seeing—your active filters, columns, and ordering are all preserved. You can also use a template-based export for a standard set of columns. Learn more about [exporting from the Spend page](https://help.expensify.com/articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses).

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.

Link formatting violation: Cross-links must use relative links, not full URLs (HELP_AUTHORING_GUIDELINES.md Section 7 "Link Formatting"). Replace https://help.expensify.com/articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses with the relative path /articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses.


**Note:** Report-level templates only appear when full reports are selected.

# Export your current filtered view

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.

Heading structure violation: This adds another # heading, but only one # article title plus optional # FAQ is allowed (HELP_AUTHORING_GUIDELINES.md Section 4). Headings must also be task-based (Section 2). Convert to a task-based ## heading, e.g. ## How to export your current filtered view.

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR documents the renamed Current view CSV export option (previously "Export current view") on the Spend page. Changes span two articles: a new export subsection plus FAQ update in Getting Started with the Spend Page, and a new "current filtered view" section plus terminology/FAQ updates in Export Expenses and Reports. The content is accurate, uses exact UI labels, and improves consistency of the Current view naming. The main issue is heading hierarchy: the PR introduces new H1 section headings, which the governance forbids.

Scores Summary

  • Readability: 8/10 - New paragraphs are clear, scannable, and benefit-focused; bold UI labels aid comprehension. Minor: the export description sentence is a bit long.
  • AI Readiness: 5/10 - Good task-based ## How to export from the Spend page, but the PR adds noun-only # Filters, # Smart Suggestions, and # Export your current filtered view H1 headings, violating the single-H1 rule (HELP_AUTHORING_GUIDELINES section 4) and the ban on topic-only headings (section 2).
  • Style Compliance: 7/10 - UI terminology (Current view, Export, Concierge, Display) is exact and consistently bolded. Deduction: the modified FAQ answer in the Spend Page article uses a full https://help.expensify.com URL where a relative link is required (section 7 Link Formatting).

Key Findings

  • Single-H1 violation: newly added # Filters, # Smart Suggestions (Spend Page) and # Export your current filtered view (Export article) should be ##, and the first two are noun-only labels rather than task-based.
  • Positive: the "Export current view" to "Current view" rename is applied consistently across the option list, body copy, and FAQ, keeping UI terminology accurate.
  • Positive: new relative cross-link to Search-and-Download-Expenses follows the relative-link standard.
  • Link formatting: the updated FAQ answer under "Can I export reports from the Spend page?" retains a full URL instead of a relative path.

Recommendations

  • Demote the new H1 headings to ## (for example ## How to export your current filtered view). Fold the # Filters / # Smart Suggestions labels under the existing task-based ## headings just below them, or remove the bare labels.
  • Convert the full https://help.expensify.com/... URL in the modified FAQ answer to a relative /articles/... link.
  • Optional: tighten the long export-description sentence for readability.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Getting-Started-with-the-Spend-Page.md - New export subsection and FAQ update; new H1 headings need demotion; full URL in FAQ.
  • docs/articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses.md - Consistent Current view rename and clear new section; new H1 should be ##.

Note: Detailed line-by-line feedback has been provided as inline comments.

@flaviadefaria flaviadefaria merged commit 68df9cd into main Jul 7, 2026
19 checks passed
@flaviadefaria flaviadefaria deleted the claude-exportCurrentViewHelpDocs branch July 7, 2026 10:39
@OSBotify

OSBotify commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/flaviadefaria in version: 9.4.29-0 🚀

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

@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/flaviadefaria in version: 9.4.31-0 🚀

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

@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.4.31-0 🚀

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants