[No QA] Add help site docs for Duplicate Report feature by MelvinBot · Pull Request #87835 · Expensify/App

MelvinBot · 2026-04-14T06:34:42Z

Explanation of Change

Add help site documentation for the Duplicate Report feature (tracked in #81206). This covers 5 merged implementation issues:

New article How-to-Duplicate-a-Report.md — documents the new "Duplicate report" action available in the report More menu, including what gets copied, workspace behavior, and FAQ.
Update Expense-and-Report-Actions.md — adds "Duplicate report" row to the Secondary Actions table.
Update Understanding-Report-Statuses-and-Actions.md — adds "Duplicate report" to the More menu bullet list.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/623952

Tests

Verify docs routes validation passes (createDocsRoutes.sh)
Verify new article follows existing patterns (matches structure of How-to-Duplicate-an-Expense.md)
Verify table row in Expense-and-Report-Actions.md matches column format of existing rows

Offline tests

N/A — docs-only changes, no runtime behavior.

QA Steps

Verify the new article renders correctly on the help site
Verify the updated tables in Expense-and-Report-Actions.md and Understanding-Report-Statuses-and-Actions.md display correctly

Verify that no errors appear in the JS console

AI Tests

createDocsRoutes.sh — passed (docs routes file is up to date)

Human Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"

QA

// TODO: The human co-author must fill out the QA tests before marking this PR as "ready for review"

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).

Add new article How-to-Duplicate-a-Report.md covering the new Duplicate report action, and update Expense-and-Report-Actions.md and Understanding-Report-Statuses-and-Actions.md to include the new action in their reference tables. Co-authored-by: Stephanie Elliott <[email protected]>

OSBotify · 2026-04-14T06:38:26Z

A preview of your ExpensifyHelp changes have been deployed to https://c5de408e.helpdot.pages.dev ⚡️

Updated articles:

melvin-bot · 2026-04-15T02:43:13Z

melvin-bot · 2026-04-15T02:43:15Z

@lschurr 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]

github-actions · 2026-04-15T02:46:06Z

HelpDot Documentation Review

Overall Assessment

This PR adds a new help article for the Duplicate Report feature along with corresponding cross-reference entries in two existing articles. The new article is well-structured, follows the single-workflow principle, and includes all required YAML metadata. However, there are several governance violations that need to be addressed before merge, most notably the use of prohibited "More" terminology instead of the required three dots convention.

Scores Summary

Readability: 8/10 - The article is clear, scannable, and well-organized with logical sections. Minor issue: a missing space after the period in the intro paragraph ("Duplicate report.This" should be "Duplicate report. This"). Step instructions are mostly action-oriented and sequential.
AI Readiness: 9/10 - All YAML metadata fields are present and well-crafted, including internalScope with clear audience and exclusions. Headings are task-based using action verbs and question words. Includes a "How to" heading. Keywords cover realistic search phrases.
Style Compliance: 5/10 - Multiple governance violations found: (1) Step 4 uses "Select More" which is explicitly prohibited -- must use "Select the three dots (⋮)"; (2) FAQ heading references "More menu" which is also prohibited; (3) Navigation instruction phrasing deviates from the prescribed format; (4) Quotation marks used inside bold UI reference text.

Key Findings

Critical issues that must be addressed:

Three Dots Menu Rule violation (Step 4): "Select More" must be changed to "Select the three dots (⋮)" per HELPSITE_NAMING_CONVENTIONS.md. The governance file explicitly states: "Do not call it 'More'" and "Do not write 'More menu'."
FAQ heading references prohibited term: "Why is the Duplicate report option not showing in the More menu?" uses "More menu" which is prohibited. Suggested revision: "Why is Duplicate report not showing after selecting the three dots on my report?"
Navigation phrasing mismatch (Step 1): "In the navigation tabs (on the left on web, and at the bottom on mobile)" does not match the prescribed format. Per governance, when web and mobile are structurally the same, use: "Click the navigation tabs (on the left on web, on the bottom on mobile)." The word "Click" should begin the instruction, "and at" should be just "on," and "In" should not be used.

Minor issues:

Missing space: In the intro paragraph, "Duplicate report.This" is missing a space before "This."
Quotation marks in UI reference: **"Copy of [Original report name]"** wraps the UI element name in quotation marks. Per Button Naming Standards, UI elements should not be wrapped in quotation marks. Consider: The new report is named Copy of [Original report name].
Inconsistent Workspace capitalization: In the "What happens" section, one bullet uses lowercase "workspace" ("the new report is created on that workspace") while another uses capitalized "Workspace" ("created on your primary Workspace"). Per naming conventions, use the exact term as shown in the UI consistently.
Step 2 vagueness: "Locate the report you want to duplicate" is borderline against the prohibited language rule ("Find the setting"). Consider making this more deterministic, e.g., "Click the report you want to duplicate" (which also makes Step 3 redundant, streamlining the flow).

Positive aspects:

Thorough internalScope metadata that clearly defines audience, coverage, and exclusions
Good cross-link to the individual expense duplication article, placed outside numbered steps as required
FAQ section addresses realistic user questions with direct, concise answers
The additions to Expense-and-Report-Actions.md and Understanding-Report-Statuses-and-Actions.md are consistent and well-formatted
Clean heading hierarchy using only # and ## levels as required
Single-workflow focus maintained throughout the article

Recommendations

[Must fix] Replace "Select More" in Step 4 with "Select the three dots (⋮)"
[Must fix] Rewrite the FAQ heading to remove "More menu" reference
[Must fix] Revise Step 1 navigation phrasing to match the prescribed format exactly
[Should fix] Add the missing space after the period in the intro paragraph
[Should fix] Remove quotation marks from the bold UI element name in the "What happens" section
[Should fix] Standardize "Workspace" capitalization throughout
[Consider] Consolidate Steps 2 and 3 into a single, more deterministic step

Files Reviewed

docs/articles/new-expensify/reports-and-expenses/Duplicate-a-Report.md (new file) - Good structure and metadata; requires three dots menu and navigation phrasing fixes
docs/articles/new-expensify/reports-and-expenses/Expense-and-Report-Actions.md (+1 line) - Table row addition is well-formatted and consistent with existing entries
docs/articles/new-expensify/reports-and-expenses/Understanding-Report-Statuses-and-Actions.md (+1 line) - Bullet addition is appropriate and correctly placed

Scoring is based on the governance rules defined in docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md.

stephanieelliott · 2026-04-15T02:54:16Z

Applied all relevant bot comments

stephanieelliott · 2026-04-15T02:56:00Z

@garrettmknight gonna get this merged ASAP because it's being linked in the product update post tomorrow. But tagging you in here in case there is anything that needs to change - if so we can open up a followup PR

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fea345c371

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

OSBotify · 2026-04-16T03:59:47Z

🚀 Deployed to staging by https://github.com/kadiealexander in version: 9.3.60-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot assigned stephanieelliott Apr 14, 2026

MelvinBot requested a review from a team April 14, 2026 06:34

github-actions bot changed the title ~~Add help site docs for Duplicate Report feature~~ [No QA] Add help site docs for Duplicate Report feature Apr 14, 2026

Update and rename How-to-Duplicate-a-Report.md to Duplicate-a-Report.md

fea345c

stephanieelliott marked this pull request as ready for review April 15, 2026 02:43

stephanieelliott self-requested a review as a code owner April 15, 2026 02:43

melvin-bot bot requested review from lschurr and removed request for a team April 15, 2026 02:43

stephanieelliott previously approved these changes Apr 15, 2026

View reviewed changes