Skip to content

[Due for payment 2026-03-02] [Domain Control] [Release 3.4] Set or unset a vacation delegate #79570

Closed

Description

@jmusial

Part of this project #76750

Implement reset domain:

Issue Owner

Current Issue Owner: @jmusial

Activity

  1. moved this from Todo to In Progress in Bring Domain Control to NewDoton Jan 30, 2026
  2. godong0128 commented on Feb 11, 2026

    @godong0128

    Proposal

    Problem:
    Currently, the Vacation Delegate feature only allows users to set a delegate for themselves via their profile settings. Domain admins lack the ability to manage or set vacation delegates for members within their domain control settings, which is necessary for administrative oversight during member absences.

    Solution:
    Implement the "Vacation Delegate" management feature within the Domain Control module.

    1. UI Updates:
      • Modify src/pages/domain/BaseDomainMemberDetailsComponent.tsx to include a "Vacation Delegate" menu item in the member details view.
      • Create a new page src/pages/domain/Members/DomainMemberVacationDelegatePage.tsx (modeled after the existing VacationDelegatePage.tsx) that accepts a member's accountID or email as a parameter.
    2. Logic & Actions:
      • Leverage the existing setVacationDelegate and deleteVacationDelegate actions in src/libs/actions/VacationDelegate.ts.
      • Ensure the API call uses the member's email as the target for the delegate assignment.
    3. Routing:
      • Define new routes and screens in src/ROUTES.ts and src/SCREENS.ts for the domain-specific vacation delegate setting.
    4. Localization:
      • Add necessary translation keys in src/languages/en.ts for domain member vacation delegate descriptions.
  3. melvin-bot commented on Feb 11, 2026

    @melvin-bot

    📣 @godong0128! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  4. godong0128 commented on Feb 12, 2026

    @godong0128

    Hi @melvin-bot , here are my contributor details as requested:

    Upwork Profile Link: https://www.upwork.com/freelancers/~01d2028d0e2af7cefe
    Email: godong0128@gmail.com

    I'm looking forward to contributing to this project!

  5. 1 remaining item

  6. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 23, 2026
  7. changed the title [-][Domain Control] [Release 3.4] Set or unset a vacation delegate[/-] [+][Due for payment 2026-03-02] [Domain Control] [Release 3.4] Set or unset a vacation delegate[/+] on Feb 23, 2026
  8. melvin-bot commented on Feb 23, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  9. melvin-bot commented on Feb 23, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.24-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-03-02. 🎊

    For reference, here are some details about the assignees on this issue:

    • @jmusial does not require payment (Contractor)
    • @ZhenjaHorbach requires payment through NewDot Manual Requests
    • @situchan requires payment (Needs manual offer from BZ)
  10. rayane-d commented on Feb 25, 2026

    @rayane-d
    Contributor

    This is done 🎉

  11. melvin-bot commented on Mar 3, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

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 productionWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions