Amir E. Aharoni wrote:
In Bugzilla some projects used prefixes in bug titles.
I guess that it was
done to make sure that people understand to what project does the bug
pertain as quickly as possible. The one that I ran into most frequently is
"VisualEditor:", and there may be others.
In Bugzilla, bug summaries were important. IRC and e-mail notifications
only included the bug summary, not the associated product or component, so
you could receive messages that were not very helpful. For example, "Long
lines in preformatted paragraphs should not wrap" is actually specific to
VisualEditor, so it would more properly be "Long lines in preformatted
paragraphs should not wrap in VisualEditor".
In Phab I see that bug (task?) lists and search results
always have a
project (briefcase) tag near them. If these tags indeed appear every time
the bug title is shown, then the prefixes are redundant.
Does any object to start removing them?
The prefixes have always been a bit silly. But I don't know why we can't
be as specific as possible in the one-line summary. Compare "Adding
external links should trigger CAPTCHA" and "Adding external links using
Flow should trigger CAPTCHA". The latter is clearly preferable.
Looking at Phabricator's e-mail notifications, it seems to have the same
issue as Bugzilla: the e-mails don't include any information about the
project(s) associated with a task.
Given this, I'm not sure why we would edit task titles to include less
information. It feels like shooting ourselves in the foot.
MZMcBride