Which features would Bugzilla users really miss? If you are not sure whether feature X is supported, under development, roadmapped... just ask.
ragesoss wrote on 2014-04-07 18:42:50 (UTC)
Does Phabricator do charting of open bugs over time, like https://bugzilla.wikimedia.org/chart.cgi?category=MediaWiki%20extensions&datefrom=2012&dateto=&label0=All%20Open&line0=839&name=839&subcategory=EducationProgram&action=wrap&width=700&height=450
qgil wrote on 2014-04-07 18:56:37 (UTC)
Good point that goes beyond Bugzilla, @Ragesoss. I have created this task about porting the tech community metrics we need: T53: Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible
scfc wrote on 2014-04-10 14:18:52 (UTC)
I would have said "Add other users as CC", but that's an "Action" in the list above :-). I don't see any showstoppers; missing in general: Comfort with what I'm used to. The UI feels a bit noisy. Also, I find it very confusing that things like the bug tracker have their own names (apparently "Maniphest"). I'm sure names like "Differential", "Diffusion" (Quick quiz: Don't look it up! What's what?), or "Diviner" have a meaning to their developers, but these feel like bumps in the road for the rest.
What's not missing, but what certainly would be nice: Credentials shared with wikitech (for the common users).
qgil wrote on 2014-04-17 18:57:03 (UTC)
Considering that we are talking about Bugzilla features "really missing", I think we ca clean a bit this list. To be discussed in every task. Thank you Nemo and bawolff for the wave of feedback!
Nemo_bis wrote on 2014-04-18 07:17:43 (UTC)
Considering that we are talking about Bugzilla features "really missing",
A meaningful interface is definitely a feature of bugzilla that I'm missing. I agree that we could make the title of this task clearer.
By the way, after the 30th or so bug I also found a couple small things I liked but I already forgot them. Where to document the things that phabricator does better than our current tools?
qgil wrote on 2014-04-27 05:17:05 (UTC)
I have documented the relevant missing Bugzilla features at https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla#Missing_features
The blockers for a migration are defined at T39: Set up permissions for Phabricator. If you want to propose more blockers, please discuss there (or at the wiki page).
qgil wrote on 2014-04-27 06:19:22 (UTC)
All tasks created related to the Bugzilla vs Phabricator discussion are listed as dependencies for documentation purposes (they are not actual blockers of this task). If you find another task, just add it.
jdforrester wrote on 2014-05-12 17:59:31 (UTC)
What's the Phabricator equivalent for "Default CC", i. e. how can I subscribe to all (new) tasks in a project/component?
When you are a member of a project you can get you to be automatically e-mailed with a variety of information about that project – http://fab.wmflabs.org/settings/panel/emailpreferences/ has options for Differential (code review) and Maniphest (task management).
aklapper wrote on 2014-05-12 20:09:33 (UTC)
scfc wrote on 2014-05-12 21:22:49 (UTC)
@Aklapper: Thanks. Provided that what I just did works, it's a tad complicated (= a "subscribe" button for a project that creates the rule automatically would be nice), but clearly superior to Bugzilla where none of this could be configured by the user.
aklapper wrote on 2014-09-03 15:12:33 (UTC)
Removed some recently added "blocking tasks". Task topic says features Bugzilla users would miss. I don't consider the naming of a button or functionality that wasn't available in Bugzilla "missing features".