Page MenuHomePhabricator

Milestone project tags should inherit their parent project's tag colour
Closed, ResolvedPublic

Assigned To
None
Authored By
hach-que
Apr 6 2016, 8:41 PM
Referenced Files
F1208317: pasted_file
Apr 6 2016, 8:41 PM
F1208320: pasted_file
Apr 6 2016, 8:41 PM
Subscribers

Description

We use project tag colors to give immediately visibility to the different types of projects that we're currently working on, so that when I have tasks from multiple projects on the go, I can quickly group the tasks by project without having to actually read the project name. In particular, we use blue tags to indicate low-priority open source project work, and use unique colours for commercial projects, general business work or external work.

For example, here's a screen capture of a list of tasks for me:

pasted_file (352×159 px, 23 KB)

When I created a new project, and a new milestone in that project, I set the project's tag colour to orange, because it's a new commercial project and I want to at a glance be able to see the tasks associated with it. However, the milestone project doesn't get that colour, and gets lost in all the other blue tags, which means now I need to read the project tags to group my work:

pasted_file (113×273 px, 12 KB)

(The top task should have an orange project tag)

While I could add the parent project as well as the milestone to the task, this feels redundant because the milestone project tag also includes the parent project name anyway.

Revisions and Commits

Restricted Differential Revision
Restricted Differential Revision

Event Timeline

epriestley added a revision: Restricted Differential Revision.Apr 6 2016, 8:58 PM
epriestley closed this task as Resolved by committing Restricted Diffusion Commit.Apr 6 2016, 9:13 PM
epriestley added a commit: Restricted Diffusion Commit.
epriestley added a revision: Restricted Differential Revision.Oct 5 2016, 4:53 PM
epriestley added a commit: Restricted Diffusion Commit.Oct 6 2016, 10:57 AM