Page MenuHomePhabricator

Allow to watch only single column of the workboard
Closed, DuplicatePublic

Description

Root problem:

User is not interested in being notified about all tasks of the given tag, but only on those which are in particular column.

Subproject not applicable here, since taks must be tagged with given project. And it is not a milestone, as it is permanent category of tasks on the board.

Event Timeline

Danny_B created this task.Jul 24 2016, 3:00 PM
chad added a subscriber: chad.Jul 24 2016, 3:07 PM

@Danny_B Are you aware we don't take feature requests that omit root problems?

chad added a comment.Jul 24 2016, 3:14 PM

You should see this information about the feature request form:

Describing Root Problems has more information on how to describe a root problem when filing a feature request. This might be solved with T5474, or maybe not, but we don't know the "why" of this request.

I don't have any idea where further/deeper to go than to what I already described in the description:
User is not interested in being notified about all tasks of the given tag, but only on those which are in particular column.
If you ask "why", I can imagine perhaps "I don't want to be spammed by things I am not interested at".
Perhaps might yet be worth to note, that it obviously applies to boards sorted by categories/area, not progress-wise (Kanban).
I can also assume it is related to discouraging of "tracking tasks" (ie. due to many issues with task graphs) which are typically exactly equal to such workboard column - they "monitor" certain area of the project, so user is subscribed to them, but not watching the entire project.
I don't know what to add more. Better if you ask.

In T11368#187082, @chad wrote:

You should see this information about the feature request form:

Sure I did. Guess why I put the (attempt of) Root problem description in the task description? ;-)

Describing Root Problems has more information on how to describe a root problem when filing a feature request. This might be solved with T5474, or maybe not, but we don't know the "why" of this request.

Nope, that's something different.

chad added a comment.Jul 24 2016, 4:31 PM

I understand a high level problem of "i get too much mail when watching a project", but I don't really have a picture of the specific "root problem". We don't really want to guess why a specific column is more interesting. Knowing the background of the project and columns might provide some insight. Maybe they need to "sign off" for instance in anything that comes into a specific column, like "QA". We just don't know, so it's hard to understand what the correct upstream solution is without these details.

Mostly I don't think watching columns is worth building, so I want to understand how things are set up and built that a user feels this is the correct solution (the 5 "whys"). It could be solved with column triggers (add me as a subscriber when things go into this column, T5474). Or with outbound mail rules (only send me project mails when object is in this column, T5791).

@Danny_B I am curious about your actual root problem as well. I have heard this from some end users but have yet to get a clear use case. Can you give an example of how you are using your workboards that this is a problem for you. I understand "too much email make it stop" however that is not something that is actionable and very short sighted.

eadler added a project: Restricted Project.Sep 15 2016, 6:08 PM