Skip to content

[Due for payment 2026-02-12] [$1500] R3 Add ability to require attendees based on category selection #76155

Closed

Description

@JmillsExpensify

As part of our overall rules and workflows initiative, we're now turning our attention category rules.

Here’s what’s in scope: We’re expanding support for required category fields and coding. Specifically, we’ll add more category-based rules within each NewDot category. For example: “If the category is Meals & Entertainment, then require the Attendees field.”

Image

This issue requires a BE component that will be planned internally, though for the FE the changes are:

Make Description hint more discoverable

Specifically, we'll move Description hint field below Payroll code and above Delete category.

Image

There are no other changes to the existing Description hint field, though I'm including it below for posterity.

Image

Add a Require fields push row

This new row contains options for both Require description and Require attendees, like so.

Image

When clicked the user sees this page in the RHP.

Image

When both fields are required, they'll appear like this (e.g. in the order the toggles appear in the RHP)

Image

Require attendees logic

We'll flag an Attendees violation on an expense when either of the following is true:

  • The attendees array is empty, or
  • The length of the attendees array minus the expense creator is zero.

Inline violation

If a member doesn't add multiple attendees when required for a given category, we'll show an inline violation using standard patterns, like so. Attendees required for this category.

Image

Admin policy logs

Enabled and disabling the requirement for attendee tracking on a given category will use one of two system messages:

  • changed the "Advertising" category attendees to required (previously not required)
  • changed the "Advertising" category attendees to not required (previously required)
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    NewFeatureSomething to build that is a new item.
    on Nov 26, 2025
  2. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new.

  3. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

  4. changed the title [-]Add ability to require attendees based on category selection[/-] [+][$500] Add ability to require attendees based on category selection[/+] on Nov 26, 2025
  5. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    ⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

  6. JmillsExpensify commented on Nov 26, 2025

    @JmillsExpensify
    ContributorAuthor

    This is an internal initiative though we'll eventually have PR review and what not.

  7. self-assigned this
    on Dec 2, 2025
  8. cead22 commented on Dec 3, 2025

    @cead22
    Contributor

    Auth and Web PRs were submitted for review

  9. 129 remaining items

  10. melvin-bot commented on Feb 16, 2026

    @melvin-bot

    @JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. garrettmknight commented on Feb 16, 2026

    @garrettmknight
    Contributor

    $1500 approved for @ikevin127

  12. jayeshmangwani commented on Feb 17, 2026

    @jayeshmangwani
    Contributor

    Since this is a new feature, adding the following regression tests:

  13. jayeshmangwani commented on Feb 17, 2026

    @jayeshmangwani
    Contributor

    Regression Test Proposal

    Preconditions:

    • WS is a Control policy.
    • Workspace Settings -> More features -> Rules must be enabled.
    • Workspace Settings -> Rules -> Attendee tracking must be enabled.

    Tests:

    I. Enable “Attendees Required” for a Category

    1. Navigate to Workspace Settings → Categories → Category Settings.
    2. Verify that the “Required fields” row is visible.
    3. Click on “Required fields” and verify:
    • The header copy reads: “This will apply to all expenses categorized as {Category}”
    • Two ON/OFF toggles are present: Require description and Require attendees
    1. Enable Require attendees.
    2. Go to workspace expenses and create a new expense by selecting for that categpry where attendees required enabled
    3. Click Create Expense without adding any attendees to Attendees row.
    4. Verify a violation appears Multiple attendees required for this category when no attendees (besides yourself) are added.
    5. Click on the Attendees row, select an attendee (besides yourself), and press Save.
    6. Verify that the violation clears.

    II. Confirmation Page Validation

    1. Create a new expense using the FAB.
    2. Select a category where attendees are required.
    3. Click the “Create {amount} expense” button.
    4. Verify that the error message appears on the Attendees row: Multiple attendees required for this category
    5. Click on the Attendees row, select an attendee (besides yourself), and press Save.
    6. Verify that clicking the “Create {amount} expense” button successfully creates the expense.

    III. Existing Expense Violation Display

    1. Open an existing expense with a category that now requires attendees.
    2. Verify the attendees field displays an error indicator.
    3. Edit the expense and add an attendee.
    4. Verify the violation clears.

    IV. Attendee Tracking & Category Rule System Messages Verification

    1. Open a workspace where all preconditions are met.
    2. Navigate to the workspace #admins channel.
    3. Verify that:
      • enabled rules thread is visible.
    4. Open the “enabled rules” thread.
    5. Verify that the system message:
      • enabled attendee tracking is displayed.
    6. Navigate to Workspace → Rules → Attendee tracking and disable it.
    7. Return to the #admins channel and open the “enabled rules” thread.
    8. Verify that the system message:
      • disabled attendee tracking is displayed.
    9. Navigate to Workspace → Rules → Attendee tracking and enable it again.
    10. Go to Workspace → Categories and select any [Category].
    11. Under the Category rules section, verify that the Required fields row is visible.
    12. Click on Required fields and enable the Require attendees toggle.
    13. Return to the #admins channel and open the “enabled rules” thread.
    14. Verify that the system message:
      • updated the category "[Category]"" by changing the Attendees from Not Required to Required
        is displayed.
    15. Navigate to Workspace → Categories → [Category] → Required fields and disable the Require attendees toggle.
    16. Return to the #admins channel and open the “enabled rules” thread.
    17. Verify that the system message
      • updated the category "[Category]" by changing the Attendees from Required to Not Required
        is displayed.

    Do we agree 👍 or 👎

  14. cead22 commented on Feb 17, 2026

    @cead22
    Contributor
    • Can we add steps after I.4 to verify the policy change log message is posted in the admins channel after requiring attendees, then remove the requirement, confirm the relevant change log is posted, then enable it again, and then continue with the test?
    • For II.4 Where does this error appear, where do you add the attendee, and is the submission automatic after adding the attendee?
  15. jayeshmangwani commented on Feb 18, 2026

    @jayeshmangwani
    Contributor

    I’ve updated test cases 1 and 2 to include more detailed steps for clicking the Create Expense button and explicitly adding attendees in the Attendees row.

    For the system messages, I added a new Test 4, since there are two scenarios to cover:

    1. Workspace-level attendee tracking rule
    2. Category-specific attendee requirement rule

    @cead22 , please review the updated tests above and let me know if anything needs to be updated.

  16. cead22 commented on Feb 18, 2026

    @cead22
    Contributor

    👍

  17. melvin-bot commented on Feb 20, 2026

    @melvin-bot

    @JmillsExpensify Still overdue 6 days?! Let's take care of this!

  18. JmillsExpensify commented on Feb 21, 2026

    @JmillsExpensify
    ContributorAuthor

    Looks good to me too. I'll get an issue created for those now.

  19. JmillsExpensify commented on Feb 21, 2026

    @JmillsExpensify
    ContributorAuthor

    Everyone is paid via ND so closing this out.

  20. trjExpensify commented on Feb 27, 2026

    @trjExpensify
    Contributor

    approved $1,500 for @jayeshmangwani

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2InternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions