Page MenuHomePhabricator
Create Task
Maniphest T5551

Add default assignee setting to Projects
Closed, DuplicatePublic
Actions

Description

I know we already discussed something like this in another task, which IIRC about enforcing an assignee on tasks. After 2 months of use of Phabricator, I can confirm that enforcing an assignee is not requirement. However, having a default assignee for new tasks filed in a given project would help a lot. It's the easiest way to ensure tasks are looked at without having to enforce strict triage sessions (not practical for small projects).

We have a Phabricator extension to bounce back to the originator tasks created without any project. Finding projects is easy though, knowing who is the "lead" for each project is a lot more impractical. Using Herald rules for each project would be a lot of maintenance and would not scale either.

Related Objects

Event Timeline

swisspol created this task.Jul 3 2014, 4:03 PM
swisspol raised the priority of this task from to Needs Triage.
swisspol updated the task description. (Show Details)
swisspol added a subscriber: swisspol.

An obvious problem is what if you create a task without an assignee while setting 2 projects on it that each have a different default assignee...

swisspol added a comment.Jul 3 2014, 4:05 PM

If it was possible to add custom fields to projects, one could add an assignee / user type field and then have a global herald rule that would act on it?

epriestley added a subscriber: epriestley.Jul 3 2014, 5:26 PM

An obvious problem is what if you create a task without an assignee while setting 2 projects on it that each have a different default assignee...

A possible fix for this is letting projects be assignees, then making a project the assignee.

If it was possible to add custom fields to projects, one could add an assignee / user type field and then have a global herald rule that would act on it?

T406 (which is very old) discusses the idea of integrating oncall rotations into projects. In the simple case this would degrade to "@jane always handles everything for #iphone", but in a more complex case there could be rotations. T760 also discusses building toward tools like PagerDuty. We have some infrastructure for this (e.g., we can send SMSes now).

This is a lot of scope expansion, but if we want to end up there eventually it would supersede anything more narrow that we might build today.

chad renamed this task from Add default assignee setting to projects to Add default assignee setting to Projects.Jul 14 2014, 1:05 AM
chad triaged this task as Wishlist priority.
chad added a project: Projects.
cburroughs added a subscriber: cburroughs.Aug 26 2014, 6:26 PM
aklapper added a subscriber: aklapper.Aug 26 2014, 8:32 PM
devurandom added a subscriber: devurandom.Feb 11 2015, 3:54 PM

When a task is assigned to a project, and all tasks assigned to it are "shown" to this project's "contact", what should happen if that "contact" changes? Should the new contact be "shown" the old tasks? That might make oncall rotations easier to setup.

I use the word "to show" to destinguish temporary oncall assignments (which are just "shown" to someone) from static actual assignments.

epriestley added a comment.Feb 11 2015, 4:12 PM

Yes, tasks assigned to a project would change assignee if the current project's default assignee / on-call lead changed.

We would probably show something like Assigned To: #project (epriestley). If I was swapped out and no longer the owner, those tasks would show Assigned To: #project (alincoln). I could claim a task explicitly, which would make it Assigned To: epriestley and that wouldn't change if the project was edited. A project could also have no automatic assignee/oncall person and just be Assigned To: #project.

It will probably be a while before we build this stuff.

epriestley mentioned this in T8106: Allow a task to be assigned to multiple people.May 7 2015, 1:35 PM
epriestley added a comment.Dec 23 2015, 6:34 PM

I'm just going to merge this into T406 since I think it isn't particularly distinguishable from the upstream perspective.

At HEAD, you may be able to use Herald rules and form customization to accomplish some of this.

epriestley closed this task as a duplicate of T406: Support "Oncall" Users.Dec 23 2015, 6:34 PM
urzds added a subscriber: urzds.Jul 12 2017, 11:15 AM
Herald added a subscriber: eadler. · View Herald TranscriptJul 12 2017, 11:15 AM
Phabricator · Built by Phacility