Now we're back to why David doesn't particularly like that:
Today I used the parent/child relationships e.g. but I don't think it's the proper approach because when I classify tickets I don't necessarily have a parent task ready.

If the categories are ones you come back to again and again, the parent task would only have to be created once. And I could imagine a grandparent task of "Fix Search Stuff" which would make it easy to find the right parent task.

Trey Jones
Software Engineer, Discovery
Wikimedia Foundation

On Thu, Jul 7, 2016 at 4:52 PM, Kevin Smith <> wrote:
On Thu, Jul 7, 2016 at 1:08 PM, Trey Jones <> wrote:
For autocomplete, what about sticking with a department/team/issue format: e.g., Discovery-Search-BadWeight.. or they could all get a personal "_Tag" prefix: _Tag-dcausse-search-badweight. That's super unwieldy, but avoids autocomplete collisions for everything else.

Autocomplete is per-word, so that sample would come up for dc, sea, bad, etc. For example, typing "back" in the upper-right search bar brings up all the xxx-backlog projects.
However, it sounds like we could consider ignoring the "no tracking tasks" directive, at least within Discovery. (Now I am advocating going against the advice given since no one seems to be advocating for it.)

As long as you don't call it a tracking task, I doubt anyone would even notice in order to complain. If it seems like it would solve the issue, I would support that. The whole "no tracking tasks" rule seemed to be a reaction (or over-reaction?) to something going on in bugzilla, so until we see actual problems in phab, I'm in favor of reasonable experimentation.


discovery mailing list