< Phabricator
Other languages:
Bahasa Indonesia Deutsch English​Lëtzebuergesch Nederlands danskespañol français italiano magyaroʻzbekcha polski portuguêsportuguês do Brasil suomi svenskačeština русский українська עבריתاردو سنڌي فارسی پښتو हिन्दीଓଡ଼ିଆ ไทย 中文 日本語 조선말한국어
Phabricator is for software bug reports, feature requests, and planning work.
  • To ask technical questions about Wikimedia projects, see m:Tech
  • To ask technical questions about MediaWiki in non-WMF installations, see Project:Support desk
Dear Phabricator user, if you have questions, please ask on the Discussion page. We improve our documentation based on the feedback received. If you want to test Phabricator, use the Cloud Services instance. (The test instance is unfortunately not always online.)
For a basic overview what Phabricator is and can do, watch the tutorial videos on Wikimedia Commons:
There are also slides if you have a low bandwidth. Or keep reading this page to dive right in and get started.
Creating your account
You can connect your new Phabricator account to either your global Wikimedia wiki account or your Wikimedia developer account. In both cases, no separate password is needed.
Using your global wiki account
Using your Wikimedia developer account
If you have a Wikimedia developer account — also known as an LDAP account, Gerrit account or Wikitech account — you can use it to log in as well. A single Phabricator username can have both and LDAP connected. This can function as a backup in the unlikely event that Wikimedia SUL is not working.
Connect your Wikimedia SUL and LDAP accounts only to a single Phabricator username! Otherwise you will end up creating two separate Phabricator accounts.
Multi-factor authentication
We discourage the use of multi-factor authentication on Wikimedia Phabricator, except for users who have access to Security tasks. If you still intend to use multi-factor authentication, please first read the multi-factor authentication guidelines and requirements, after which you can set it up if desired.
Accessing Phabricator
Email addresses
Changing accounts
Other issues
To claim your old Bugzilla and/or RT account(s), click this link.
Receiving updates and notifications
Phabricator notifies you about relevant activity, including your own actions.
Phabricator offers several tools to receive the notifications you wish to receive.
See Phabricator/Help/Managing mail for reducing the amount of mail notifications and about filtering mail notifications.
If you receive unexpected mail notifications for a task:
Creating more complex rules for notifications (Herald)
You can create custom (personal) notification rules in Wikimedia Phabricator's Herald. This is a more advanced option and can be difficult to use and should be used carefully due to performance reasons.
Creating a task
Creating a task or reporting a bug can be tricky—for a step-by-step guide and particularly how to word it and give the most information, and therefore get the best outcome, see How to report a bug.
There are several ways to create a task, depending on the information you want to carry:
Fill the form, leaving the fields you are not sure about unchanged.
Phabricator supports some formatting in text areas. See #Formatting and markup.
Use the live preview at the end of the page to check whether your text looks as you expect.
Selecting projects
In order to relate a task with a project (tag) that uses Phabricator, you just need to start typing its name in the Tags field and select the project from the list of matching projects (the list will only show five matching projects). You can search for projects and read short project descriptions by clicking the magnifier icon in the Tags field. You can add one or more projects to the Tags field. If you are unsure, you can also leave it empty — triagers will take care of tasks that have no project set. There is a (long) list of projects available. Press Edit Query to search for projects. (This list is also available at Phabricator/Projects.)
Setting task priority
Priority should normally be set by product managers, maintainers, or developers who plan to work on the task, or by the bugwrangler or experienced community members, not by the reporter filing the bug report or by outside observers. See Phabricator project management for details.
Using email
You can also create tasks by sending email to​. The subject will be used as the task title, the body will be used directly as is, and attachments will be included on the task. To set a project, add the corresponding command "!projects" and its hashtag at the beginning of the body, e.g., !projects #mediawiki-core. Further commands to set the task assignee, priority or status via email are available.
Note: if your email signature is not formatted following de facto standards (including "-- " to be separated from the body text) it will be posted as well. You are encouraged to remove private information from your signature in your first attempt, just to be sure.
Passing certain values in the task creation URL
"Report a bug in Phabricator" link can pass numerous values via URL parameters appended to the generic task creation link.
This is a very advanced feature. Learn more here.
Another option is to request a custom form for task creation which also supports setting a task subtype (e.g. "bug report" or "feature request"). See custom forms.
Task status and life cycle
See mw:Bug management/Bug report life cycle for the meaning of the Status field values.
To close a task as a duplicate of another task, select "Edit Related Tasks… > Close As Duplicate" in the side bar.
Commenting and editing a task
To reply, you need an account as well. Phabricator allows you to post and edit comments and descriptions using text formatting and inserting images or other files; see Uploading file attachments. You can use toolbar at the top of the input text area and you can use Phabricator's own formatting.
Use the live preview at the end of the page to check whether your text looks as you expect.
To edit the description of a task, select "Edit Task" in the side bar.
Formatting and markup
Phabricator supports some formatting in text areas.
Note that Phabricator's own markup language is different from MediaWiki's markup.
Popular use of markup includes:
Uploading file attachments
You should upload patches for review to Gerrit, unless it is a security patch.
Phabricator file uploads inherit permissions from the tasks to which they are posted, which often makes them publicly-viewable. See below for more details.
There are several ways to upload files: You can add a file (for example a screen photo) to a comment or a task description via drag and drop with your mouse. Users can also copy and paste images via the clipboard functionality of their system.
If this is not available on your system you can use phabricator:file/upload and refer to the file number (like "123") that is shown after a successful upload by writing F123 in a comment. This will create a link to the file. To include the file in the comment, enclose the ID in braces: {F123}. Per default it's included as thumbnail. For more formatting options, see Formatting and markup. If you have to upload files frequently and consider the currently available options uncomfortable, you could also add a text panel to your homepage with a direct link.
Note that you cannot upload a file and then decrease the access level to the file (e.g linking it to a restricted security ticket). You would have to delete the file and re-upload it with stricter access permissions. It is recommended to upload files which should have restricted access together with the creation of a restricted (security) ticket. Further, note that anyone with the full URL to a file can download the file or share the link with others. There is no authentication protecting files from being accessed. Phabricator files rely entirely on security through obscurity; guessing the (pseudo-random) URL for any given file would be very difficult, if not impossible. If you need more protection for particularly sensitive files then you should consider a more secure alternative.
If you ever need to delete a file that you uploaded, open the list of files you authored, select the file and click "Delete File" in the sidebar.
Project management
Read Phabricator/Project management for essential information on maintaining and managing projects, e.g. on using project workboards, common practices, and agile workflows.
In Phabricator projects are tags and tags are projects. A project can have a workboard. Hierarchy via sub-projects and milestones is available.[2] Tasks can be assigned to more than one project.
Requesting a new project
See Phabricator/Requesting a new project.
When do you need a project?
In general, you need a project…
Parent tasks and subtasks
Tasks can be a parent task or a subtask of any number of other tasks. If Task A cannot be solved until Task B is solved, then Task A is the parent task and Task B is the subtask. Such relations can be set via "Edit Related Tasks…". Parent tasks and subtasks are displayed under "Task Graph" in the task. This feature can be used to accomplish a few different things:
NOTE: There is an "Edit Related Tasks… > Create Subtask" feature. In addition to setting up the correct parent/subtask relationship, it also carries the CC (subscription) list into the new subtask; the downside of this is that it can create a lot of unwanted noise in other people's email, forcing them all to manually unsubscribe; it is sometimes better to manually create the new task, and then manually mark it as a subtask, thus letting other people subscribe if they want to.
See Phabricator/Project management#Setting task priorities
See Phabricator/Project management#Assigning tasks
"Tracking" tasks
The term "tracking task" was brought over from Bugzilla, where it had a specific meaning: A task which was blocked on other tasks, but which itself did not represent any work, and which was not tied to a specific release/date. An example might be a task named "Clean up the documentation", which might then have a variety of subtasks, each of which would describe specific work to be done. These "tracking" tasks tended to stick around for a long time (or forever), as their subtasks would get resolved but new ones would get created. In Phabricator, projects are favored over 'tracking tasks' with dependencies.
Note, however, that there are other types of work-less umbrella tasks which do still make sense in Phabricator. Notably, "Release" tasks. An upcoming release could be represented by a task, which lists as subtasks all the actual work tasks which are targeted for that release. Once the release goes out, it can be resolved. A similar use would be to have a task which represents a teams overall goals for the quarter, and then each goal might (or might not) be a blocking subtask.
Searching for items
Search context (global vs advanced)
Phabricator consists of several applications (task management in "Maniphest" being one of them, or Diffusion for code browsing). There are 2 different search forms:
Inside Maniphest, custom, saved searches and advanced search options are listed in the navigation bar on the left.
Search terms
Special care needs to be put in choosing correct search terms.
Some locally-valid properties for the "Query" field:
The advanced search forms are not explicit about the logic but in general use AND between different fields.
You can exclude specific projects from the results by entering not(projectname) (equivalent to NOT) and combine several projects via any(projectname) (equivalent to OR) via the auto-completion suggestions.
There's a limit of 5 items in the maniphest autocomplete.
To increase this limit, see these userscripts for Chrome and for Firefox.
You can search for specific task IDs by leveraging a hidden "IDs" field, revealed when a search URL takes the following format:,2,3,4#R
After the field is revealed, while you can still get results by manipulating the URL directly, you can also input directly into the field. The format is the number of the task only (removing the typical "T" prefix), comma-separated. This can be useful if you are pasting tasks from another place, such as a spreadsheet or database.
Another way to reveal the "IDs" field on various search forms is by enabling the "Expert Mode" checkbox in your phabricator user settings. To enable expert mode, first visit and then click the "Developer Settings" menu on the left sidebar.
Alternatives ways to find something
If you don't remember the exact words used in an item you are looking for you can follow one of these paths:
Selecting Dates and Date Ranges
This is only available in the Advanced Search.
Using the Date fields like "Created After" and "Created Before" allow entering absolute and relative dates. Note that Maniphest uses UTC.
To get a list of tasks which were created in the last 24 hours, set the "Created After" field to "-24 hours" or "-1 day". Note that "Updated Before" actually means "Last updated before" and that absolute date values like "2014-11-26" refer to UTC time while your time zone setting might be different.
The "Updated After" and "Updated Before" fields return any and all changes to a task.
For example, when a task is moved to another column in a board it registers as "updated". This may add noise to your search results.
Examples of how Maniphest interprets searches:
The "X days ago" range can be confusing. Phabricator interprets today as part of any data set. Even if it is 12:30 UTC, Phabricator will interpret that as a potential day in the range.
Saving and Managing Searches/Queries
Queries can be saved and managed inside Maniphest.
Maniphest offers links to some predefined search queries in the navigation bar on the left. For example, click authored to get a list of tasks that you have created.
Search query addresses (URL) are stable so you can save and reuse them. You can share the address in your web browser's address bar with other people, e.g. via posting the link on a wikipage.
If you want to save a search, select the "Save Query" button at the bottom of the Advanced Search UI.
When looking at the navigation bar on the left in Maniphest, click on the "Edit Queries…" link. You will see a list of your saved queries. All users have a default set which can be deleted in this UI.
Some options in this UI:
Once you save a query, you cannot change its parameters, but you can change its name. To edit a query, click on it's name, change parameters and save it as a new query. Also, Phabricator allows users to save multiple queries with the same name.
To make the user name dynamic (e.g. for "Tasks assigned to the person running this query") in searches that you'd like to share with others, select Authors > Magnify glass icon > Browse Users > "Current viewer".
Note that some common queries are also available in the "Activity" tabs on the Phabricator frontpage.
Finding the Maniphest task corresponding to a Bugzilla bug number
This is only available in the Advanced Search.
All Phabricator tasks migrated in 2014 from Bugzilla have a Reference field that contains a value "bz" followed by the number of the equivalent report in Bugzilla. If you want to search the task corresponding to a specific Bugzilla report, use the Reference field in the advanced search or just add 2000.
Advanced features
Using Dashboards
Dashboards are specially designed home pages which can display a wide range of custom information. They can be created, managed and shared between users.
Click here for a detailed Dashboard walkthrough.
Batch edits
Phabricator offers the possibility to perform mass/bulk edits for tasks. At the end of any Maniphest search query you will find a "Batch Edit Selected" to edit all the tasks you have selected using Shift-click. Users willing to use this feature need to join the Triagers group. Note: to see more than 100 tasks at a time, you can update Page Size in the query.
Batch editing can be reversed by noting the "Bulk Job" ID that is generated at the start of a Batch Edit. This can be accessed by clicking "Details" before or after executing. On the following page, there will be a "Continue" menu item to the right, which will generate a Maniphest query of all the affected tasks.
If you have to perform the very same 'uninteresting' action on a lot of tasks (cleanup or reorganizing project structures) and you do not want to trigger notifications, ask someone with CLI server access (people listed under "phabricator-admin" or "phabricator-roots") to silence that specific batch edit before running it, so no notifications will be triggered for that batch edit. Silent batch-moves of tasks from one column to another column (via "Move tasks to column…" in the column header dropdown) on the same workboard are not supported as of July 2020.
Please be mindful about silencing a batch edit. For example, silencing is usually not appropriate for closing tasks as task subscribers would expect to get a notification.
The Bookmark menu toward the right side of the top navigation bar can be customized with links to your preferred forms and actions. See the Profile Menu instructions for more information.
Personal lists of items
The "Flag For Later" functionality offers marking objects (like tasks or revisions) which "you want to remember to look at later". Eight flag colors are available. Flags are personal and private so your lists cannot be shared with others. Your flagged objects are listed on flag. They can be searched by color or object type, in contrast to tokens.
Phabricator badges
Badges are awarded to users to distinguish certain people or people in a particular group.
Currently all active badges can only be awarded by administrators.
Restricting access to tasks
If you are a member of the #WMF-NDA project tag, then access to a task that you plan to create can be restricted to members of the #WMF-NDA project by clicking the Bookmark dropdown in the top bar and selecting "NDA Protected Task".
Access to a task that you plan to create can be restricted to a list of specific users by changing the "Visible To" field to something else than "Public".
Access to an existing task can be changed via "Edit Task" and then changing the "Visible To" field to something else than "Public". Note that setting "All Users" on a task will not restrict access to a task, as everybody can simply create an account and then still access a task with that visibility.
To avoid vandalism, this "Visible To" field is only available to users who are members of some ACL projects. A list of all projects that you are a member of is available.
Security issues
If you want to file a new Security issue, you must follow Reporting security bugs to make sure that the initial task is not public! An existing task can be converted into a Security issue via "Protect as security issue" in the side bar.
Displaying and using a Space
Spaces (upstream documentation) allow restricting access to groups of objects (like tasks) to members of a specific group only. See Restricting access via Space policies for setting up.
If you can access at least two spaces, you see an additional Spaces dropdown under "Visible To" when creating and editing an object. Users with access to only one space will not see this control.
In Maniphest's task view, the Space will also be displayed in front of the task summary. You can batch-edit tasks to move them to a different Space.
Note that you will still have to associate the corresponding "public" project (if existing) to a task to make a task in a restricted Space (which you have access to) to show up in search queries and the workboard of the project. The "public" project could be automatically added via requesting a global Herald rule.
When creating tasks in Spaces, use the "Create Advanced Task" option in the "Create Task" dropdown. This option will display an additional Spaces dropdown under "Visible To" in the task creation UI that will allow you to set visibility to the Space for which this task should be visible.
If you instead create a task via the "Create Simple Task" option in the "Create Task" dropdown, then after you create it, you will have to edit the task to restrict visibility to members of the Space. Before this edit, the task will be visible to anyone and notifications about your task might have been sent to public logged IRC channels and other subscribed individuals.
  • Task creation view when having access to at least two Spaces
  • Task view when the task is in a non-public Space
  • Workboard view of two tasks in a non-public Space
  • The drag&drop feature of the workboard
MediaWiki templates and links
Main page: Help:Interwiki linking
Tracked in Phabricator
Task T177
  • You can link to Phabricator tasks from wiki pages (via [[meta:Help:Interwiki linking|interwiki linking) using phabricator: and its shorter version phab:, for instance [[phab:T454|example]] generates example.
  • Template:Tracked has been updated to include links to Phabricator objects — see at the right how
    is rendered.
  • Template:Phabricator is also available;
    generates task T176.
Existing Bugzilla links and templates will still work, because those links will continue to point to which will redirect them to the converted Phabricator task.
On every project page you find a "Reports" link in the sidebar. This is mostly useful for team projects. It offers information on task throughput, age of tasks, workload per assignee, distribution of open tasks per workboard column, a burndown chart, and an activity chart. You can also filter the data for a certain time period.
Apart from that, Phabricator doesn't support further statistics, metrics, charts, reports (e.g. over time) or however you may call them, whether built-in or via an API.[3]
Phabricator also offers tables showing the open tasks by priority and by either user or project.
Some additional overall statistics can be found in the "Phabricator monthly statistics" emails sent to wikitech-l.
Exporting task data
The results of an Advanced Search query on phab:maniphest/query/advanced/ can be exported to CSV and JSON formats. Use the "Use Results 🡒 Export Data" in the upper right corner. If you are on the workboard of a project, the column header dropdown menu allows you to "View Tasks as Query" per column.
Code browsing (Diffusion)
Further information: Phabricator/Diffusion
Diffusion is the Phabricator repository browser[4]. Another option is using gitiles at for repository read-only mirroring. Right now, we're mirroring some of our Git repositories to Phabricator for demonstration purposes.
To request and set up a new code repository, see Gerrit/New repositories/Requests​.
Default fields (Forms)
Further information: Phabricator/Help/Forms
Phabricator allows some customization of the fields shown for a given task, prefilled values for fields, and setting a task subtype (e.g. "bug report" or "feature request"). These are handled via the Forms feature.
API (Conduit)
Conduit is the name of the web API. offers some explanation and examples. See the Conduit upstream documentation. Also see Phabricator/Bots.
Phatality is a plugin for the Wikimedia production Logstash installation which makes it easier to create Phabricator tasks for production errors.
See Introducing Phatality.
Automated Regular Search Summaries
  • You can get a regular email with the results of a saved Phabricator query.
  • The emails are currently delivered by the PhabSearchEmail tool maintained by RhinosF1 on a weekly or monthly basis although, more frequenices can easily be added.
  • To request a summary email, fill out this form and let RhinosF1 know your email.
Get Notified about new UBN Tasks
See Setup UBN Notifications
Other links
  1. However, if you have made commits to any repositories mirrored in Phabricator (regardless of whether the commit was in Gerrit or elsewhere), other users will be able to see the connection between the account and the email address.
  2. T3670 (subprojects), on the upstream Phabricator instance
  3. T13279 (statistics), on the upstream Phabricator instance
  4. Diffusion repository browser user guide, on the upstream Phabricator instance
Last edited on 5 November 2021, at 19:46
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
HomeRandomLog in Settings DonateAbout MediaWiki.orgDisclaimers