Skip to content

[No QA] Docs updates for E/A#90094 Add me keyword to assignee and attendee filters#90428

Open
MelvinBot wants to merge 1 commit into
mainfrom
docs/search-me-keyword-all-user-filters
Open

[No QA] Docs updates for E/A#90094 Add me keyword to assignee and attendee filters#90428
MelvinBot wants to merge 1 commit into
mainfrom
docs/search-me-keyword-all-user-filters

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Summary

Test plan

  • Verify the help article renders correctly on the help site
  • Confirm assignee:me and attendee:me descriptions are accurate

Update the search operators help article to document that the me
keyword works with assignee: and attendee: filters, matching the
existing documentation for from: and to: filters.

Co-authored-by: Wildan M <wildan-m@users.noreply.github.com>
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label May 13, 2026
@github-actions github-actions Bot changed the title Docs updates for E/A#90094 Add me keyword to assignee and attendee filters [No QA] Docs updates for E/A#90094 Add me keyword to assignee and attendee filters May 13, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

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

Updated articles:

@stephanieelliott stephanieelliott marked this pull request as ready for review May 15, 2026 02:10
@stephanieelliott stephanieelliott self-requested a review as a code owner May 15, 2026 02:10
@github-actions
Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes two small, targeted updates to the search operators reference article. It adds clarifying input-type hints (email, phone, display name, or me) to the attendee: and assignee: operator descriptions. The changes are accurate, consistent with how from: and to: are already documented in the same article, and correctly reflect the new me keyword feature.

Scores Summary

  • Readability: 9/10 - The added parenthetical details are concise and scannable. The attendee: line is slightly longer than its peers but still readable in context.
  • AI Readiness: 9/10 - YAML metadata, heading hierarchy, and task-based headings are all intact. The added detail improves retrieval accuracy for queries about filtering by "me" or by display name. No metadata update was needed since the existing keywords and internalScope already cover search operator syntax broadly.
  • Style Compliance: 10/10 - The new text mirrors the exact pattern already established by the from: and to: rows in the cross-type operators table (line 44-45 of the article), maintaining consistency. The backtick formatting of me correctly matches how other operator values are styled throughout the article.

Key Findings

  • The changes bring attendee: and assignee: descriptions into parity with the existing from: and to: descriptions, which already listed email, phone, display name, or me. This consistency is a clear improvement.
  • No governance violations were introduced. Heading structure, YAML metadata, and UI terminology remain compliant.
  • The attendee: line retains its example (e.g. attendee:"Jason Mills"), which helpfully demonstrates the display-name usage mentioned in the new parenthetical.

Recommendations

  • No blocking issues. This PR is ready to merge as-is.
  • Minor optional consideration: the assignee: line does not include an inline example like attendee: does. Adding one (e.g., e.g. assignee:me) could further improve clarity, but this is not required and may be out of scope for this PR.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Use-Search-Operators-to-Filter-and-Analyze.md - Two lines updated; both changes are clean, consistent, and governance-compliant.

@stephanieelliott stephanieelliott requested a review from a team May 15, 2026 04:10
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 15, 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 @twisterdotcom

@melvin-bot melvin-bot Bot requested review from twisterdotcom and removed request for a team May 15, 2026 04:11
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 15, 2026

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

@stephanieelliott stephanieelliott self-assigned this May 15, 2026
You can use the following operators to filter tasks:

- `assignee:` – assigned member
- `assignee:` – assigned member (email, phone, display name, or `me`)
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.

Consistency suggestion: The attendee: line (line 64) includes an example (e.g. attendee:"Jason Mills"), and the from:/to: lines also show examples. Consider adding a brief example here too for consistency, e.g.:

Suggested change
- `assignee:` – assigned member (email, phone, display name, or `me`)
- `assignee:` – assigned member (email, phone, display name, or `me`), e.g. `assignee:me`

@github-actions
Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes a small, targeted update to two operator descriptions in the search operators article. It adds clarifying input types (email, phone, display name, or me) to the attendee: and assignee: filter descriptions, bringing them into consistency with the existing from: and to: operator descriptions already in the article. The change is clean, accurate, and well-scoped.

Scores Summary

  • Readability: 9/10 - The added parenthetical detail is concise and follows the exact same pattern already established by from: and to: in this article. The inline code formatting of me is clear and scannable. No issues with sentence flow or step formatting.
  • AI Readiness: 9/10 - The additions improve retrieval quality by making the article more explicit about accepted input types for these operators. Users searching for "how to filter by me keyword" or "search assignee by email" will now find relevant content. No changes to headings or metadata were needed for this scope.
  • Style Compliance: 10/10 - The phrasing mirrors the existing convention used for from: and to: operators verbatim, maintaining deterministic and consistent language throughout the article. No UI terminology issues, no prohibited language, no formatting violations.

Key Findings

  • The primary value of this PR is internal consistency: from: and to: already document "(email, phone, display name, or me)" and now attendee: and assignee: match that pattern exactly.
  • The use of inline code backticks for me is appropriate since it represents a literal keyword the user types into the search field.
  • No governance violations were identified in the proposed changes.

Recommendations

  • No changes required. This PR is ready to merge as-is from a documentation quality perspective.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Use-Search-Operators-to-Filter-and-Analyze.md - Two operator descriptions updated for consistency. No issues found.

Note: No inline comments were necessary -- the changes are clean and compliant with all governance standards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants