Page MenuHomePhabricator
Create Task
Maniphest T10144

Document why projects will never affect visibility
Closed, ResolvedPublic
Actions

Description

Given a task "Company Movie Night".
It is assigned to two projects "Frontend" and "Backend" so members of both projects are aware of it.
The task is visible/editable for members of those teams.

Now I decide to invite the "Mobile" team as well.
In the task, I add "Mobile" as a project (besides "Frontend" and "Backend") and now:

actual: I need to modify visible/editable and need to add members of project "Mobile" manually because it is a static list

expected: there is a setting:

  • Visible to:
    • Members of Projects:
      • "Please, Mr. Phabricator, look in the 'Projects' field and use all the projects listed there as a dynamic list"

I don't think this is possible right now.
Please explain to me whether this request is reasonable or if the approach is stupid to begin with and/or if there exists a workaround/better workflow.

Revisions and Commits

rP Phabricator
D15108rPcb1c3424a86a Use "tag" more consistenty when referring to associating a project with an…
D15107rP7bbd949703d6 Document that tagging something with a project never affects visibility

Related Objects

Event Timeline

mna created this task.Jan 13 2016, 4:44 PM
chad closed this task as Invalid.Jan 13 2016, 5:03 PM
chad claimed this task.
chad added a subscriber: chad.

See Support Resources. Maniphest here is used for feature requests and bug reports. Generally how to use Phabricator questions should go to the community.

epriestley reopened this task as Open.Jan 13 2016, 5:03 PM
epriestley added a subscriber: epriestley.

We do not intend to ever implement this. It is intentional that adding and removing projects never affect policies.

I'll write this up formally somewhere since we've now shipped Spaces and it comes up every so often.

epriestley added a comment.Jan 13 2016, 5:04 PM

Oops, collided midair there. I'm just going to redirect this into "write docs".

epriestley renamed this task from Derive visibility from assigned projects to Document why projects will never affect visibility.Jan 13 2016, 5:05 PM
epriestley claimed this task.
epriestley triaged this task as Wishlist priority.
epriestley added a project: Documentation.
chad added a comment.Jan 13 2016, 5:05 PM

Tru dat.

joshuaspence added a subscriber: joshuaspence.Jan 13 2016, 8:11 PM
epriestley merged a task: T9165: Clarify effects of different kinds of Visible-To.Jan 20 2016, 2:47 PM
epriestley added subscribers: revi, bbrdaric, Krenair and 3 others.
epriestley added a project: Projects.Jan 22 2016, 12:05 PM
epriestley moved this task from Backlog to Projects v3 on the Projects board.Jan 22 2016, 12:09 PM
epriestley added a revision: D15107: Document that tagging something with a project never affects visibility.Jan 24 2016, 5:24 PM
epriestley added a revision: D15108: Use "tag" more consistenty when referring to associating a project with an object.Jan 24 2016, 5:42 PM
epriestley mentioned this in D15108: Use "tag" more consistenty when referring to associating a project with an object.Jan 24 2016, 6:01 PM
epriestley closed this task as Resolved by committing rP7bbd949703d6: Document that tagging something with a project never affects visibility.Jan 24 2016, 6:02 PM
epriestley added a commit: rP7bbd949703d6: Document that tagging something with a project never affects visibility.
epriestley added a commit: rPcb1c3424a86a: Use "tag" more consistenty when referring to associating a project with an….
eadler removed a subscriber: eadler.Jan 24 2016, 6:19 PM
urzds added a subscriber: urzds.Jul 12 2017, 11:16 AM
Phabricator · Built by Phacility