Le 24/11/2014 10:46, Amir E. Aharoni a écrit :
Hi,
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 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?
Hello,
When tasks ends up in multiple projects (when multiple parties are
involved), it is useful to use one of the project as a prefix to more or
less identify which project is responsible for fixing it (much like
assigning a bug to a group).
Another way would be for each team to have their own bug and use sub
tasks / blocker referencing the other teams tasks.
An example, given I need to setup a new server for continuous
integration. In Bugzilla I would probably have created a bug under
'continuous integration', cc some ops and prefix it with [OPS]:
Component: continuous integration
Subject: [OPS] set up new Jenkins server
Assignee: Myself
CC: some ops
The prefix is handy there to figure out instantly who is working on it.
Note how it is assigned to myself whereas it is for ops, I am the
assignee because I am responsible for the completion of this bug.
With Phabricator I can have a task that reference a task in the
operations team:
T1:
Project: continuous integration
Subject: Track ops installing new Jenkins server
Assignee: Myself
Blocked by: T2
T2:
Project: operations
Subject: Install new Jenkins server
Assignee: One ops
Blocked by: T1
In this case the prefix are not needed, the responsibilities are clearly
established.
Splitting tasks seems better than using prefix for the above use case.
--
Antoine "hashar" Musso