Hi,

maybe not the best place to talk about that but...

I'd like to categorize some phab tasks so that I can access them quickly in the future. At first I thought that tags would be a perfect fit by creating my own custom tags. But as far as I understood tags are projects and I'm not allowed to create them. I suppose that if this feature is protected behind permissions this is because phab admins do not want someone to pollute the system with random tags.

My usecase is:

Sometimes users report queries that are not performing very well. Usually by reading the query I can identify and classify the cause. This cause can be something like:
- bad weighting of words in the title
- text analysis issue
- index/db discrepancies
- ...

This list is quite vague...

While it's not worth fixing a particular issue that mentions a specific query it's sometimes helpful to retrieve such tickets (where sometimes I added a comment) while I'm working on this class of problems:
- just to have more examples to test
- maybe I was wrong with the initial classification and the problem is elsewhere

Retrieving such tickets is painful today, because I have to rely on search, not to blame phab developpers, search is hard we all know :)

Today I used the parent/child relationships e.g. https://phabricator.wikimedia.org/T128073 but I don't think it's the proper approach because when I classify tickets I don't necessarily have a parent task ready.

Thanks for your suggestions.

_______________________________________________
discovery mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/discovery

Reply via email to