Skip to content

[No QA] Update help site docs for Attendees expense table columns#86991

Open
MelvinBot wants to merge 2 commits intomainfrom
melvin-helpsite-attendee-columns-85332
Open

[No QA] Update help site docs for Attendees expense table columns#86991
MelvinBot wants to merge 2 commits intomainfrom
melvin-helpsite-attendee-columns-85332

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Summary

  • Updates help site documentation to reflect the new Attendees and Per attendee columns added to the expense table in feat: Person Amount and Attendees in Expense Table #85332.
  • Adds the new columns to the expense table column list in Managing-Expenses-in-a-Report.md.
  • Adds a new section to Adding-Attendees.md explaining how attendees appear in the expense table.

Test plan

  • Verify the Adding-Attendees.md article renders correctly on the help site
  • Verify the Managing-Expenses-in-a-Report.md article renders correctly on the help site
  • Confirm column names match the UI labels exactly

Co-authored-by: nkdengineer nkdengineer@users.noreply.github.com

…lumns

Add documentation for the new Attendees and Per attendee columns that
appear in the expense table when expenses have attendees.

Co-authored-by: nkdengineer <nkdengineer@users.noreply.github.com>
@github-actions github-actions bot changed the title Update help site docs for Attendees expense table columns [No QA] Update help site docs for Attendees expense table columns Apr 2, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 2, 2026

@stephanieelliott stephanieelliott requested a review from a team April 8, 2026 06:45
@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 @muttmuure

@melvin-bot melvin-bot bot requested review from muttmuure and removed request for a team April 8, 2026 06:45
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

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

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.

3 participants