[No QA] Update Getting-Started-with-the-Reports-Page.md#72372
Conversation
Concierge reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member? |
|
@clarajones-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] |
HelpDot Documentation ReviewOverall AssessmentThis PR updates the "Getting Started with the Reports Page" documentation with targeted improvements that address user confusion around filtering functionality and comparison with Expensify Classic. The changes focus on clarifying filter availability, improving section organization, and adding practical guidance for users transitioning from Classic to New Expensify. Scores Summary
Key FindingsPositive Aspects:
Areas for Improvement:
RecommendationsHigh Priority:
Medium Priority:
Files Reviewed
Note: This is a strategic documentation improvement that addresses real user confusion points while maintaining good overall quality. |
|
A preview of your ExpensifyHelp changes have been deployed to https://678a6ce2.helpdot.pages.dev ⚡️ Updated articles: |
HelpDot Documentation ReviewOverall AssessmentThis PR makes focused improvements to the "Getting Started with the Reports Page" documentation, addressing user confusion around filtering functionality and transitions from Expensify Classic. The changes demonstrate a clear understanding of user pain points while maintaining overall documentation quality. Scores Summary
Key FindingsMajor Strengths:
Areas Needing Attention:
RecommendationsCritical Actions:
Enhancement Opportunities:
Files Reviewed
Overall Quality Score: 8/10 - This is a well-targeted update that meaningfully improves user experience while maintaining documentation standards. The enhanced keywords alone significantly improve discoverability for users struggling with common filtering issues. Detailed formatting feedback provided as inline comments for specific implementation guidance. |
| title: Getting Started with the Reports Page | ||
| description: Learn how to use the Reports page in New Expensify to view, filter, and manage your expense data using report previews, tables, filters, and smart suggestions. | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions] | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions, date range, search, expenses missing] |
There was a problem hiding this comment.
Keywords improvement: Good addition of "date range, search, expenses missing" keywords to improve SEO and searchability. These terms align well with the content covered in the article.
|
|
||
| ## Can someone comment on a report? | ||
| Yes, if someone comments on a report, a **Comments** section appears and the layout adjusts to make space for the discussion. | ||
| ## Why don’t I see the same filters as in Expensify Classic? |
There was a problem hiding this comment.
Readability violation: The FAQ question "Why don't I see the same filters as in Expensify Classic?" could be more specific. Consider: "What happened to filters from Expensify Classic?" or "Where are the Classic filters in New Expensify?"
| Get familiar with the Reports page in New Expensify. This guide walks you through using report previews, tables, filters, and smart suggestions to streamline your expense-tracking workflow. | ||
|
|
||
| The **Reports page** shows a full list of your reports and related expenses. While the Inbox highlights what needs attention, this page helps you explore, filter, and export your expense data. | ||
| The Reports page in New Expensify gives you a complete view of your submitted, approved, and reimbursed expenses—all in one place. This guide shows you how to use report previews, tables, filters, and smart suggestions to track, manage, and take action on your expenses more efficiently. |
There was a problem hiding this comment.
Style improvement: The opening sentence is clear and benefit-focused, which follows HelpDot best practices. However, consider adding a breadcrumb path below the H1 to help with AI readiness (e.g., "Settings > Workspaces > Reports").
|
|
||
| New Expensify simplifies filtering compared to Classic. Some filters like “All Time” or “All Workspaces” aren’t available in the same way. Instead: | ||
|
|
||
| - Use the **Date Range** picker to simulate “All Time” |
There was a problem hiding this comment.
Expensify Style violation: Use "workspace" consistently instead of "Workspace" when referring to the workspace switcher feature. Should be "workspace switcher" to match Expensify's standard terminology.
|
|
||
| - **Add unreported expenses to a report**: Use filters to find unreported expenses, and then add them to a report with just a few clicks. | ||
| - **Quickly search reports** | ||
| - **Quickly search and locate specific reports using filters.** |
There was a problem hiding this comment.
Formatting issue: The bullet point ends with a period followed by another bullet point. This creates inconsistent formatting. Either remove the period or restructure as separate bullets for better readability.
HelpDot Documentation ReviewOverall AssessmentThis PR contains focused improvements to the "Getting Started with the Reports Page" documentation. The changes streamline content, enhance user guidance, and better address the transition from Expensify Classic to New Expensify. The updates demonstrate good editorial judgment in simplifying complex information while maintaining completeness. Scores Summary
Key FindingsStrengths:
Areas for consideration:
RecommendationsImmediate actions:
Future enhancements:
Files Reviewed
This review assessed content accuracy, user experience, formatting consistency, and overall documentation quality. The changes represent a net positive improvement to user guidance. |
| - Search bars | ||
| - Chips (selectable tags) | ||
| - Radio buttons or checkboxes | ||
| - **Expenses:** can be filtered by `Date`, `Merchant`, `Category`, `Tag`, `Amount`, `Reimbursable`, `Billable`, `Status` (e.g. Unreported) |
There was a problem hiding this comment.
Formatting inconsistency: The list uses backticks around filter names inconsistently. Either use backticks for all filter names or remove them entirely for consistency. Also, consider using bullet points instead of inline listing for better scannability.
| - Use the **Workspace Switcher** to move between workspaces | ||
| - Use **Unreported** or **Open** status filters to find expenses without reports | ||
|
|
||
| ## How do comments work on a report? |
There was a problem hiding this comment.
FAQ structure violation: The FAQ question "How do comments work on a report?" should be more specific and actionable. Consider: "How do I comment on a report?" or "What happens when someone comments on a report?"
| - **Workspace** | ||
| - **Tags** (if enabled) | ||
| - **Status** (e.g., pending, reimbursed) | ||
| - **Reports:** can be filtered by `Submitter`, `Workspace`, `Report Status` (e.g. Open, Approved, Paid), `Date` |
There was a problem hiding this comment.
Formatting inconsistency: Same issue as line 90 - inconsistent use of backticks around filter names. Also, the parenthetical examples should be formatted consistently (either all with "e.g." or standardized abbreviations).
| - **Status** (e.g., pending, reimbursed) | ||
| - **Reports:** can be filtered by `Submitter`, `Workspace`, `Report Status` (e.g. Open, Approved, Paid), `Date` | ||
|
|
||
| To view other available filters, click into the **search box** on the Reports or Expenses page. |
There was a problem hiding this comment.
Formatting consistency: The instruction "To view other available filters, click into the search box..." should maintain consistent formatting. Consider using consistent formatting for UI elements throughout the document.
|
|
||
| ## Can someone comment on a report? | ||
| Yes, if someone comments on a report, a **Comments** section appears and the layout adjusts to make space for the discussion. | ||
| ## Why don’t I see the same filters as in Expensify Classic? |
There was a problem hiding this comment.
FAQ structure violation: The question doesn't use proper ## subheading format. FAQ questions should be formatted as "## Why don't I see the same filters as in Expensify Classic?" with the question mark included in the heading.
| - Use the **Workspace Switcher** to move between workspaces | ||
| - Use **Unreported** or **Open** status filters to find expenses without reports | ||
|
|
||
| ## How do comments work on a report? |
There was a problem hiding this comment.
FAQ structure violation: Same issue as line 139 - the question should be formatted as "## How do comments work on a report?" using proper ## subheading format for FAQ questions.
| - **Report status** (e.g., Open, Approved, Reimbursed) | ||
|
|
||
| ## Filter Controls | ||
| ### Available Filters in New Expensify |
There was a problem hiding this comment.
Heading level violation: Using ### (H3) for "Available Filters in New Expensify" creates an inconsistent heading hierarchy. This should be ## (H2) to maintain proper document structure and match other sections like "How Filtering Works".
| description: Learn how to use the Reports page in New Expensify to view, filter, and manage your expense data using report previews, tables, filters, and smart suggestions. | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions] | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions, date range, search, expenses missing] | ||
| --- |
There was a problem hiding this comment.
AI Readiness violation: Missing breadcrumb path below the YAML metadata. Add a breadcrumb path like "Reports > Reports page" after line 6 to help users understand where this feature is located in the navigation.
| - **Report status** (e.g., Open, Approved, Reimbursed) | ||
|
|
||
| ## Filter Controls | ||
| ### Available Filters in New Expensify |
There was a problem hiding this comment.
AI Readiness violation: Use ## instead of ### for subheadings. This heading should be "## Available Filters in New Expensify" to maintain proper heading hierarchy (only use # and ## levels).
HelpDot Documentation ReviewOverall AssessmentThis PR refines the "Getting Started with the Reports Page" documentation with improved clarity, better organization, and more comprehensive information. The changes demonstrate thoughtful restructuring to enhance user comprehension and practical guidance. Scores Summary
Key FindingsStrengths:
Areas for improvement:
RecommendationsHigh Priority:
Medium Priority:
Files Reviewed
Overall Quality Score: 8.3/10 This is a solid documentation improvement that enhances user experience through better organization and more practical guidance. The changes align well with HelpDot standards and provide clear value to users navigating the Reports page functionality. Note: This assessment represents the overall quality and impact of the documentation changes. The improvements in structure and content significantly enhance the user experience. |
| title: Getting Started with the Reports Page | ||
| description: Learn how to use the Reports page in New Expensify to view, filter, and manage your expense data using report previews, tables, filters, and smart suggestions. | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions] | ||
| keywords: [New Expensify, reports page, report preview, report table, filters, smart suggestions, expense management, add expenses, bulk actions, date range, search, expenses missing] |
There was a problem hiding this comment.
AI Readiness violation: Keywords should include navigation paths to help users find this feature. Consider adding "reports navigation" or "reports menu" to help users understand where to find the Reports page in the app.
|
@clarajones-expensify looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
|
no reviewer checklist needed |
|
🚀 Deployed to staging by https://github.com/clarajones-expensify in version: 9.2.35-0 🚀
|
|
🚀 Deployed to production by https://github.com/blimpich in version: 9.2.35-4 🚀
|
Context: https://expensify.slack.com/archives/C090U774ZH7/p1759872215804569
Debugger: https://chatgpt.com/share/e/68e9d7cb-3fe4-8001-b8eb-713dfb83325b