Shared destination restrictions / multi-home

English Forum Product Feedback
1

Proposal: Restrict the scope of task multi-homing.
Reason: It is necessary to restrict the scope of task availability and allow users to choose the scope of communication.
Settings:

  • Not share
  • Team only
  • Public

Related Posts:

Related Settings: Team permissions

Current multi-homing feature restriction options here

  • Project admins only
  • Project admin and editors

Help Center: Restricted custom field values

2

I tried to see if I could achieve something similar with the following settings.
Somehow, it worked as I wanted.

Relationship between teams, projects, and tasks

  • Team1: Team privacy = Membership by request (A member has to request to join this team)
    – Project 1: Created in Team 1
    –Task 1: Created in Project 1
  • Team2: Team privacy = Private (A member must be invited to join this team)
    – Project 2: Created in Team 2. Multihoming allowed only for admins
    – Task 2: Created in Project 2

Multihoming test

  • Multihoming Task 1 to Project 2: Possible
  • Multihoming Task 2 to Project 1: Not possible (Even if I try to multihome Task 2 in Project 2, the menu to add it to another project does not appear.)

Since there are only a few tests, I feel like the content is insufficient.

1 Like