|Resolved||Qgil||T553 Engineering Community team goals for October 2014|
|Resolved||Qgil||T174 Launch Wikimedia Phabricator Day 1|
|Resolved||Qgil||T175 Nominate a team in charge of deploying and maintaining Wikimedia Phabricator code|
|Resolved||• RobLa-WMF||T17 Allocate resources for the migration and maintenance|
|Resolved||Qgil||T19 Define which features existing in our current tools are really missing in Phabricator|
|Resolved||Qgil||T15 Migrate Bugzilla to Phabricator|
|Resolved||Aklapper||T22 Identify features Bugzilla users would miss in Phabricator|
|Open||None||T54 Adding dependencies while creating a (sub-)task|
qgil wrote on 2014-04-15 16:28:47 (UTC)
How is this different from Bugzilla? There you also need to create the bug first, and then set dependencies.
In fact Phabricator allows you to "Create Subtask", which carries CCed people and priority to the new subtask, which saves you one potential step.
scfc wrote on 2014-04-20 00:23:48 (UTC)
@Qgil: If I go to https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia%20Labs (for example), I have a field "Depends on" and a field "Blocks". Do you mean something different by "dependencies"?
I use this feature to avoid having another mail sent for the change; IIRC I've also seen this used for pre-set bug templates (= links for potential bug reporters that pre-set components, dependencies, etc. so that bugs end up in the right place).
aklapper wrote on 2014-07-18 00:26:06 (UTC)
It is cumbersome and annoying, but I don't think this should block us from Day 1 of using Phabricator, so I'm going to move this to the "Wikimedia Phabricator Maintenance (after Day 1)" project.