(Redirected from Feature requests)
Jump to: navigation, search

Other languages:
Deutsch • ‎English • ‎español • ‎suomi • ‎français • ‎italiano • ‎日本語 • ‎한국어 • ‎Nederlands • ‎português • ‎português do Brasil • ‎русский

Phabricator is an open-source software development platform used for project management, bug reporting, feature requests, and code review in an integrated fashion.

The migration to Phabricator is work in progress. See the timeline below for more information.

Get started[edit | edit source]

Wikimedia Phabricator documentation overview
Intro to Wikimedia Phabricator

For a Wikimedia-centric overview, watch the Tech Talk The Very Basics of Phabricator. Former Bugzilla users are encouraged to read our Phabricator versus Bugzilla comparison.

You can also watch a screencast about handling tasks/bugs.

First missions include

If you have questions, check the Help and the FAQ. Your questions are very welcome.

For Phabricator support and camaraderie, join #wikimedia-devtoolsconnect.

There is a test instance at Use it to learn and experiment, not for serious work.

Get involved[edit | edit source]

We are working on the migration of several developer infrastructure services to one single Phabricator instance. It's a very exciting project! We welcome your help.

  • Learn to use Phabricator. Play and test in our Labs instance as much as you want. Check out the documentation and short videos on Phabricator/Help.
  • Git and Gerrit users are welcome to the Gerrit-Migration project. We need help learning about the possibilities of Phabricator in this area: what is missing, what exists in a different way, what is remarkably interesting, which are the blockers that should be reported upstream?

Report bugs and feature requests[edit | edit source]

Please see How to report a bug for general information how to report bugs in any projects via Wikimedia Phabricator.

Regarding reporting bugs in the Phabricator software itself:

We have two different projects to handle Phabricator related tasks:

See the Wikimedia Phabricator bug workflow for more details.

Developers[edit | edit source]

As a PHP developer, you're welcome to contribute enhancements and new features upstream. Learn more at Phabricator/Code.

Weekly update / maintenance window[edit | edit source]

Phabricator doesn't have releases, and therefore it is up to us to decide how close do we want to follow the upstream version. There is a weekly window for updates and other maintenance tasks on Wednesdays at 5:00PM Pacific (Thursday Midnight, 0:00 UTC) (check your timezone) and users will get redirected to Phabricator/Maintenance. We don't necessarily update Phabricator every week, but we reserve this window to use as needed, usually twice per month, depending on the urgency of outstanding bugs fixed upstream. The expected downtime during this window is between 0 and 30 minutes.

Migration timeline[edit | edit source]

Beware, the Phabricator team may change this sequence as plans evolve (although we try not to).

  1. YesYDone Deployment of (project)
  2. YesYDone Migration of data from to
  3. YesYDone New test instance in Labs open to everyone, blocked by
  4. YesYDone open to all Wikimedia users
  5. YesYDone Test instance containing Bugzilla reports automatically migrated
    • YesYDone end of Bugzilla preview feedback period, announcement of Bugzilla migration date.
  6. YesYDone, 2014-11-21: Bugzilla migration (1-4 days downtime, see detailed timeline), blocked by
  7. YesYDone except for minor queues, 2014-12-18 00:00UTC-08:00UTC: Phabricator RT migration: RT migration (8 hours downtime of Phabricator; blocked by
  8. YesYDone Burndown charts & migration from Scrumbugz
  9. In progress In progress Define main tasks (epics) for code review in Phabricator
  10. YesYDone, 2015-06-30: Total migration from Mingle; cf. T825
  11. In progress In progress, before 2015-06-30? Total migration from Trello; cf. T825
  12. To do To do, before 2015-07-31? Proof of concept of code review in Phabricator
  13. To do To do, before 2015-07-31? Total migration from gitblit
  14. To do To do, before 2015-12-31? Total migration from Gerrit
  15. To do To do, before 2015-12-31? Total migration from Jenkins

See also[edit | edit source]