Skip to content

[No QA] [Payment due @FitseTLT] [No QA] Update Distance Expenses help doc for selfDM rate selection#87278

Open
MelvinBot wants to merge 5 commits intomainfrom
claude-updateDistRateHelpDocs-v2
Open

[No QA] [Payment due @FitseTLT] [No QA] Update Distance Expenses help doc for selfDM rate selection#87278
MelvinBot wants to merge 5 commits intomainfrom
claude-updateDistRateHelpDocs-v2

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

Updates docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md to reflect new behavior from #74967:

  1. "Distance expenses created for personal tracking" → "Distance expenses tracked for personal use": Now documents the three scenarios (default Workspace, multiple Workspaces, no Workspace) and the upgrade flow for self-DM rate selection
  2. FAQ "Can I update the Distance expense unit or rate?": Updated to explain that tracked expenses in self-DM now support rate selection

This replaces #87194, which had unresolvable merge conflicts due to unrelated git histories.

Fixed Issues

$

Tests

  • Verify that no errors appear in the JS console
  1. Visit the help site docs preview
  2. Navigate to the Distance Expenses help article
  3. Verify the "Distance expenses tracked for personal use" section correctly describes the three scenarios
  4. Verify the FAQ about updating distance rate/unit reflects the new self-DM behavior

Offline tests

N/A — documentation-only change

QA Steps

// [No QA] — documentation-only change

  • 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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

N/A — documentation-only change

Co-authored-by: Fitsum Abebe <FitseTLT@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 7, 2026

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

Updated articles:

## Can I update the Distance expense unit or rate?

The distance unit and rate can only be updated by a Workspace Admin on the Workspace. It is not possible to adjust the distance rate or unit at the expense level.
For expenses on a Workspace, rates are managed by the Workspace Admin. For tracked distance expenses in your self-DM, you can tap the **Rate** field to select a rate from one of your Workspaces or create a new Workspace with a custom rate.
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.

@MelvinBot revert this change it is not needed

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.

Reverted this FAQ answer back to the original text in e7c0fe7.

description: Learn how to create a Distance expense using GPS tracking, map-based routes, manual entry, or odometer readings, and how the reimbursement rate is determined in New Expensify.
keywords: [New Expensify, distance expense, mileage reimbursement, create expense, distance rate, workspace rate, map route, reimbursement rate, manual mileage, manual distance, global create, track distance, GPS, GPS tracking, start GPS, track route, track mileage, mileage tracking, calculate mileage reimbursement, mileage rate, odometer, odometer reading, odometer image, odometer mileage, odometer distance, start reading, end reading]
internalScope: Audience is all members. Covers creating Distance expenses using GPS tracking, map-based routes, manual entry, and odometer readings, plus how reimbursement rates are applied. Does not cover configuring Workspace distance rates in detail or broader report submission workflows.
internalScope: Audience is all members. Covers creating Distance expenses using GPS tracking, map-based routes, manual entry, and odometer readings, plus how reimbursement rates are applied — including selecting or creating Workspace rates for personal tracked expenses. Does not cover configuring Workspace distance rates in detail or broader report submission workflows.
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.

@MelvinBot this change is also not needed.

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.

Reverted the internalScope line back to the original text in 96af605.

MelvinBot and others added 2 commits April 8, 2026 13:01
Reverts the "Can I update the Distance expense unit or rate?" FAQ
answer back to its original text as requested by FitseTLT.

Co-authored-by: Fitsum Abebe <FitseTLT@users.noreply.github.com>
Reverts the internalScope frontmatter back to its original text
as requested by FitseTLT.

Co-authored-by: Fitsum Abebe <FitseTLT@users.noreply.github.com>
[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/reports-and-expenses/Managing-Distance-Rates)

### Distance expenses created for personal tracking
### Distance expenses tracked for personal use
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.

@MelvinBot your changes here completely ignored the distance expenses linked with 1v1 DMs which is also included as expenses outside of a workspace

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.

Good catch — updated in 113c54e. The section now covers both scenarios:

  • 1v1 DMs: default P2P rate based on currency, no rate picker
  • Self-DM: Workspace rate selection (default Workspace, multiple Workspaces, or no Workspace)

Expands the "Distance expenses outside of a Workspace" section to
document both 1v1 DM behavior (default P2P rates, no rate picker)
and self-DM behavior (Workspace rate selection) as requested by
reviewer.

Co-authored-by: Fitsum Abebe <FitseTLT@users.noreply.github.com>
@FitseTLT
Copy link
Copy Markdown
Contributor

FitseTLT commented Apr 8, 2026

@MelvinBot make it ready for review

Copy link
Copy Markdown
Contributor

@FitseTLT FitseTLT left a comment

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 changed the title [No QA] Update Distance Expenses help doc for selfDM rate selection [Payment due @FitseTLT] [No QA] Update Distance Expenses help doc for selfDM rate selection Apr 8, 2026
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

🎯 @FitseTLT, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - no internal issue.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@MelvinBot MelvinBot marked this pull request as ready for review April 8, 2026 13:16
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Marked this PR as ready for review.

@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

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 review from Kel-Expensify and removed request for a team April 8, 2026 13:16
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

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

[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/reports-and-expenses/Managing-Distance-Rates)

### Distance expenses created for personal tracking
### Distance expenses created outside of a Workspace
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 level violation: Governance rules require only # and ## headings — ### is not allowed (see HELP_AUTHORING_GUIDELINES.md Section 4 and TEMPLATE.md). This should be changed to a ## heading.

Additionally, this heading is not task-based. All ## headings must start with an action verb or question word (How, What, Where, Who, Why, When). Consider something like:

Suggested change
### Distance expenses created outside of a Workspace
## How distance rates work outside of a Workspace

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

HelpDot Documentation Review

Overall Assessment

This PR updates the Distance Expenses help article to describe how distance rate selection works in different contexts (1v1 DMs, self-DMs with/without a default Workspace, and users without a group Workspace). The content is informative, well-structured within its section, and addresses a real user scenario. However, there are governance violations in the changed lines that should be addressed.

Scores Summary

  • Readability: 8/10 - The new bullet structure is clear and scannable. The sub-bullets under "Self-DM" effectively break down three distinct scenarios. Minor concern: the parenthetical in the introductory line "(e.g., in a 1v1 DM or your self-DM)" adds useful context but the terms "1v1 DM" and "self-DM" may not be immediately clear to all users.
  • AI Readiness: 5/10 - The changed heading uses ### (a level prohibited by governance) and is not task-based. Both issues reduce retrieval quality. The heading ### Distance expenses created outside of a Workspace is noun-only and does not start with an action verb or question word as required.
  • Style Compliance: 7/10 - The Rate field is correctly bolded as a UI element reference. However, the ### heading level violates the strict "only # and ## headings" rule. The terms "1v1 DM" and "self-DM" should be verified against exact in-product UI labels per the naming conventions (the UI may use different terminology). The trailing whitespace removal on the FAQ answer is a welcome cleanup.

Key Findings

  • Critical: ### heading in changed lines. The governance files (HELP_AUTHORING_GUIDELINES.md Section 2, Section 9; TEMPLATE.md) explicitly prohibit headings deeper than ##. The changed heading ### Distance expenses created outside of a Workspace uses ###. Note: the sibling heading ### Distance expenses created on a Workspace has the same issue but is not part of this diff. Consider restructuring the parent section or promoting these to ## level with task-based phrasing.
  • Critical: Non-task-based heading. The changed heading ### Distance expenses created outside of a Workspace is a noun phrase, not a task-based heading. Per governance, all headings (except # FAQ) must start with an action verb or question word (How, What, Where, Who, Why, When). A corrected version might be: ## How distance rates work outside of a Workspace or ## How to select a distance rate outside of a Workspace.
  • Positive: Clear scenario breakdown. The three sub-scenarios (default Workspace, multiple Workspaces with no default, no group Workspace) are well-differentiated and give users a clear path based on their situation.
  • Positive: UI element bolding. The Rate field reference is correctly bolded per naming conventions.
  • Minor: Terminology verification needed. "1v1 DM" and "self-DM" should be confirmed as the exact labels used in the product UI. If the UI uses different terms (e.g., "direct message" or "personal chat"), those should be used instead per HELPSITE_NAMING_CONVENTIONS.md.

Recommendations

  1. [High priority] Change the ### heading to ## and rephrase it to be task-based (e.g., ## How distance rates are applied outside of a Workspace). This would also require restructuring the parent section, since the sibling heading has the same issues -- though that falls outside this diff's scope.
  2. [Medium priority] Verify that "1v1 DM" and "self-DM" match the exact terminology shown in the Expensify UI. If different labels are used in the product, update accordingly.
  3. [Low priority] Consider whether the FAQ answer for "Can I update the Distance expense unit or rate?" should be updated to reflect the new self-DM rate selection behavior, since users can now tap the Rate field in some scenarios.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md -- 8 additions, 8 deletions. Content quality is good; governance compliance needs attention on heading level and heading phrasing.

Note: This review covers only the proposed changes in the diff, not pre-existing content.

### Distance expenses created outside of a Workspace

If you're creating expenses outside of a Workspace:
If you're creating a distance expense outside of a Workspace (e.g., in a 1v1 DM or your self-DM):
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.

Style note: The terms "1v1 DM" and "self-DM" appear in this line and the bullets below. Per naming conventions, UI references should use the exact text shown in the product. If the UI labels these as "direct message" or "chat" rather than "1v1 DM" / "self-DM," consider updating to match the actual UI terminology. If these are the established product terms, disregard.

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.

Ok @MelvinBot change 1v1 dm to dm chat and self-dm to Your space.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 113c54e76e

ℹ️ 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".

## Can I update the Distance expense unit or rate?

The distance unit and rate can only be updated by a Workspace Admin on the Workspace. It is not possible to adjust the distance rate or unit at the expense level.
The distance unit and rate can only be updated by a Workspace Admin on the Workspace. It is not possible to adjust the distance rate or unit at the expense level.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update FAQ to match self-DM rate selection guidance

This FAQ now contradicts the newly added self-DM guidance above: the section on expenses outside a Workspace says users can tap Rate and pick a different Workspace rate in self-DM, but this answer states it is not possible to adjust the rate at the expense level. In the self-DM context this will mislead users about a supported flow, so the FAQ should be narrowed (for example, to editing custom rates vs selecting existing rates) or updated to reflect the new behavior.

Useful? React with 👍 / 👎.

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.

There is nothing to change regarding the new changes of behavior in the self dm rate selection because it clearly states it is not possible to update at the expense level.

Per reviewer feedback from FitseTLT.

Co-authored-by: Fitsum Abebe <FitseTLT@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Updated terminology in 344f1c3: "1v1 DM" → "DM chat" and "self-DM"/"Self-DM" → "Your space" throughout the doc.

@github-actions github-actions bot changed the title [Payment due @FitseTLT] [No QA] Update Distance Expenses help doc for selfDM rate selection [No QA] [Payment due @FitseTLT] [No QA] Update Distance Expenses help doc for selfDM rate selection Apr 8, 2026
@Kel-Expensify
Copy link
Copy Markdown
Contributor

@stephanieelliott, I've completed my checklist review. Is there anything else left for me to do?

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