Phabricator/versus Bugzilla

Related Phabricator task: T116: Document benefits for Bugzilla users.

Improvements
Almost everything below is mobile friendly!

Task-centric environment

 * Tasks can be bugs, and they can be tasks. No more "this doesn't belong to Bugzilla" or "this report is being tracked at..."
 * Reporters, developers, designers, and product managers use the same tool to discuss bugs/features and report progress.
 * We get project boards (example) and mockups with notes (example).
 * Explicit titles of tasks, code reviews, and mockups related to the task, without needing to click or memorize numbers.
 * You can also see in which column/status of the project board the task is currently.

Flexible taxonomy

 * Projects can be created like keywords; there is no rigid tree structure.
 * Tasks can be assigned to multiple projects. No more discussions about where a bug belongs.

User account

 * Log in with your Wikimedia SUL credentials (planned).
 * Your email address is finally private.

Creating tasks

 * If we want, we can make a simple form for newcomers with only title, project, description, leaving the rest of files to advanced users only.
 * Type-ahead to select projects, instead of browsing products/components to find the destination.
 * The description of a task can be edited by multiple users (diffs available) to evolve the task and summarise long discussions.
 * A toolbar and a specific markup allows formatting of descriptions.

Commenting

 * Auto-save of comments while you type.
 * A toolbar and a specific markup allows formatting of comments.
 * You can reference to tasks and their current title will be added automatically, e.g. {T39} gives T39: Migrate Bugzilla to Phabricator
 * You can mention users e.g.  @qgil, CCing them to the task in the same go.
 * You can add files and inline images to comments with a simple drag & drop.
 * You can edit your own comments.

Notifications

 * With Herald you can create notifications based on queries, e.g. email me when someone mentions (your regexp here).

Calls to action

 * Unbreak Now! (highest priority) tasks appear in everybody's dashboards.
 * Tasks needing triaging appear at the top of lists (including search results) and in personal dashboards of the members of the affected projects.

Permissions

 * We can decide who can create projects.
 * We can have an EditBugs team whose members could invite new members.

Considerations

 * It is a paradigm different to Bugzilla's, and we need to plan for it (T68)
 * Offering a simpler UI, some advanced actions require an extra click e.g. T58, T94, T101.
 * We are still investigating the possibilities for interacting via email, also for non-registered users (T97)
 * T159: Use ElasticSearch backend for Maniphest to get stemming feature
 * Will users find their way with type-ahead for assigning tasks to projects? See T52.
 * T57: Copy / quote text of previous comments when replying

Missing features
Follow the tasks open upstream that are relevant to Wikimedia at the Upstreaming to Phabricator.org project board. All the tasks related with Bugzilla vs Phabricator are listed as dependencies at T46: Identify features Bugzilla users would miss in Phabricator.

The most important features Phabricator misses today are:
 * No way to hide/delete comments (T146)
 * No way to enforce the policy of a project to all tasks related to it e.g. a task in "Security" can be made public (T95)

Not part of Phabricator, but requires porting:
 * T221: Plan to port IRC bots
 * T53: Support Phabricator in Metrics Grimoire

Remarkable / under discussion:
 * T175: Phabricator is assistive technology–unfriendly (investigating the impact)
 * T74: Suggestions of possible duplicates when creating a new bug/task
 * T162: Lack of dependency tree (i.e. tracking bugs)
 * T126: RSS/Atom feeds (not in Phabricator's plans)