Phabricator/Help/de

Lieber Phabricatornutzer, liebe Phabricatornutzerin, wenn Du Fragen hast, stelle sie auf dieser Diskussionsseite. Wir verbessern unserer Dokumente, basierend auf den Rückmeldungen, die wir erhalten. Wenn Du Phabricator testen willst, solltest Du den folgenden Link nutzen: Labs instance Die Testmöglichkeit ist leider nicht immer online.

Für einen grundlegenden Überblick, was Phabricator ist und kann,. Oder lies diese Seite weiter, um direkt einzutauchen und loszulegen.

Erstellen eines Kontos
Du kannst Dein neues Phabricator-Konto entweder mit Deinem globalen Wikimedia-Wiki-Konto oder mit Deinem Wikimedia-Entwicklerkonto verbinden. In beiden Fällen wird kein separates Passwort benötigt.

Mit Deinem globalen Wiki-Konto



 * Stelle zunächst sicher, dass Du bei Wikimedia bist.
 * Wenn Du noch keinen Wikimedia-Account hast, dann.
 * Gehe zur Phabricator Login-Seite (der Link wird als Pfeil zu einer Tür oben rechts angezeigt, wenn du abgemeldet bist).
 * Klicke auf die Schaltfläche "Login or Register - MediaWiki".
 * Du wirst von MediaWiki.org aufgefordert, die Verbindung zu genehmigen.
 * Phabricator wird Dich nach einem Benutzernamen fragen. Verwende im Zweifelsfall einfach Deinen Wikimedia-Benutzernamen. Beachte jedoch, dass der Phabricator-Benutzername keine Nicht- ASCII - Zeichen wie العَرَبِيةُ oder 中华民族 oder Xï oder Leerzeichen enthalten darf (verwende einfach einen Unterstrich) " " stattdessen). Eine gültige E-Mail-Adresse wird ebenfalls zur Überprüfung benötigt, anderen Benutzernwird sie jedoch nicht angezeigt.
 * Klicke in der linken Navigationsleiste auf Manage.
 * Klicke auf Edit Profile und gib Also Known As (z.B. Deinen vollen Namen) an, um die Suche nach Dir zu erleichtern.

Mit Deinem Wikimedia Entwickler-Konto



 * Wenn Du ein Wikimedia Entwickler-Konto hast – es wird auch als LDAP-Konto oder Gerrit-Konto oder Wikitech-Konto bezeichnet – kannst Du Dich auch damit anmelden. Mit demselben Phabricator-Benutzernamen können sowohl MediaWiki.org als auch LDAP verbunden sein. Dies kann ein Backup sein, falls Wikimedia SUL Kim seltenen Fall ausnahmsweise nicht funktionieren sollte. Verbinde Deine Wikimedia SUL- und LDAP-Konten mit einem einzigen Phabricator-Benutzernamen! Andernfalls erstelle zwei separate Phabricator-Konten.

Mehrfach-Faktor-Authentifizierung

 * Wir empfehlen die Verwendung der Multi-Faktor-Authentifizierung in Wikimedia Phabricator ausdrücklich nicht, es sei denn, Du hast Zugriff auf Sicherheitsaufgaben. Wenn Du sie trotzdem verwenden möchtest, lies zuerst die Richtlinien und Anforderungen für die Multi-Faktor-Authentifizierung und dann, wenn Du es immer noch willst.

Fehlerbehebung

 * Aufgrund anhaltenden Missbrauchs können einige IPs aus bestimmten Ländern (z. B. Ägypten) nicht auf Phabricator zugreifen. Einige (aber nicht alle) Proxys, VPNs und Tor-Exit-Knoten sind ebenfalls blockiert. Beim Zugriff auf Phabricator über diese IP-Adressen wird ein HTTP 500- oder 501-Fehler angezeigt. Wenn Deine IP-Adresse blockiert ist und Du keinen verwendbaren Proxy für den Zugriff auf Phabricator findest, kannst Du Dich an security@undefinedwikimedia.org wenden, um Deine IP-Adresse auf die Whitelist setzen zu lassen.
 * Wenn Du Dein Phabricator-Konto deaktiviert findest, ergänze einen Hinweis auf Talk:Phabricator/Help. (Nur wenn dies nicht möglich sein sollte, wende Dich an den Bugwrangler.) Wir können Deine E-Mail-Adresse nicht korrigieren, aber wir können Dein Konto löschen, damit Du Dich erneut registrieren kannst.
 * Wenn Dein Phabricator-Konto deaktiviert ist, sende bitte einen Hinweis an Talk:Phabricator/Help (Diskussion:Phabricator/Hilfe).
 * Wenn beim Versuch, ein Phabricator-Konto über "Anmelden oder Registrieren - MediaWiki" zu erstellen, die Fehlermeldung "E-Mail-Adresse bereits vergeben" angezeigt wird, hast Du wahrscheinlich bereits ein Phabricator-Konto eröffnet, das mit Deinem Wikimedia Entwickler-Konto verbunden ist. Du musst Dich in diesem Fall über Dein Entwicklerkonto bei Phabricator anmelden. Verwende wikitech:Special:PasswordReset, wenn Du das Kennwort Deines Entwicklerkontos vergessen haben solltest.
 * Um Deinen Phabricator-Benutzernamen aus irgendeinem Grund zu ändern, sende bitte einen Hinweis an Talk:Phabricator/Help (Diskussion: Phabricator / Hilfe) und füge einen Link zu Deinem Phabricator-Profil hinzu.
 * So änderst Du das globale Wiki-Konto oder Entwicklerkonto, das Deinem Phabricator-Konto zugeordnet ist:
 * Beachte, dass Dein Phabricator-Konto jederzeit entweder einem globalen Wiki-Konto oder einem Entwicklerkonto zugeordnet sein muss.
 * Wenn Du Dein globales Wiki-Konto ändern möchtest, das mit Deinem Phabricator-Konto verbunden ist: Melde Dich über Dein Entwicklerkonto, das auch mit Deinem Phabricator-Konto verbunden ist, bei Phabricator an. Entferne dann Dein altes globales Wiki-Konto und verbinde Dein neues globales Wiki-Konto mit Deinem Phabricator-Konto. (Wenn Dein Phabricator-Konto nur mit Deinem globalen Wiki-Konto, aber noch nicht mit einem Entwicklerkonto verbunden ist, verbinde zuerst ein Entwicklerkonto mit Deinem Phabricator-Konto.)
 * Wenn Du Dein Entwicklerkonto ändern möchtest, das mit Deinem Phabricator-Konto verbunden ist: Melde Dich über Dein globales Wiki-Konto, das auch mit Deinem Phabricator-Konto verbunden ist, bei Phabricator an. Entferne dann Dein altes Entwicklerkonto und verbinde  Dein neues Entwicklerkonto mit Deinem Phabricator-Konto. (Wenn Dein Phabricator-Konto nur Deinem  Entwicklerkonto, aber noch nicht auch einem globalen Wiki-Konto zugeordnet ist, verbinde zuerst ein globales Wiki-Konto mit Deinem Phabricator-Konto.)

Anforderung Deiner früheren Bugzilla- und RT-Konten
Folge diesem Link.

Erhalt von Updates und Benachrichtigungen
Phabricator benachrichtigt Dich über relevante Aktivitäten, einschließlich Deiner eigenen Aktionen.

Phabricator bietet verschiedene Tools, um genau diejenigen  Benachrichtigungen zu erhalten, die Du erhalten möchtest.


 * Wenn Du an einem einzelnen Objekt interessiert bist (eine Aufgabe, ein Modell…), klicke einfach auf der Seite auf >Subscribe<. Wenn Du einen Kommentar hinzufügst, kommt die Seite automatisch auf Deine Beobachtungsliste.
 * Wenn Du an allen Aktivitäten innerhalb eines Projekts interessiert bist, kannst Du auf der Zusammenfassungsseite des Projekts auf >Watch Project< (Projekt beobachten) klicken. Weitere Informationen findest Du im Benutzerhandbuch [Projects] unter "Projekte beobachten".

Informationen zum Reduzieren der Anzahl von E-Mail-Benachrichtigungen und zum Filtern von E-Mail-Benachrichtigungen findest Du unter.

Fehlerbehebung
Wenn Du unerwünschte E-Mail-Benachrichtigungen für eine Aufgabe erhältst:


 * Möglicherweise hast Du die Aufgabe abonniert.
 * Du bist möglicherweise Mitglied eines Projekts oder eines Teilprojekts, das dieser Aufgabe zugeordnet ist. Eine Liste aller Projekte, bei denen Du Mitglied bist ist verfügbar.
 * Möglicherweise beobachtest Du ein Projekt, das dieser Aufgabe zugeordnet ist. Eine Liste aller Projekte, die Du beobachtest ist verfügbar.
 * In Deinen E-Mail-Einstellungen unter "Maniphest-Aufgaben" hast Du möglicherweise "Eine der Unteraufgaben einer Aufgabe ändert den Status" aktiviert.
 * Möglicherweise hast Du eine persönliche Herald-Regel eingerichtet. Überprüfe das Feld "X-Herald-Rules" Betreffzeile, um eine Liste aller angewendeten Herald-Regeln anzuzeigen.
 * Wenn nichts hilft, überprüfe das Betreffzeilenfeld "X-Phabricator-Stamps" auf weitere Informationen. Siehe.

Komplexere Regeln für Benachrichtigungen erstellen (Herald)
Du kannst benutzerdefinierte (persönliche) Benachrichtigungsregeln in Wikimedia Phabricator's Herald erstellen. Dies ist eine erweiterte Option, die schwierig zu verwenden sein kann und aus Performancegründen sorgfältig verwendet werden sollte.

Eine Aufgabe erstellen
Abhängig von den Informationen, die Du erstellen möchtest, gibt es verschiedene Möglichkeiten, eine Aufgabe zu erstellen:


 * Zum Erstellen einer neue Aufgabe: Klicke auf die Schaltfläche "Lesezeichen" rechts in der oberen Navigationsleiste. Wähle im Dropdown-Menü die Option Aufgabe erstellen. Es öffnet sich ein leeres Feld.
 * Bei einem Sicherheitsproblem: Klicke auf die Schaltfläche "Lesezeichen" rechts in der oberen Navigationsleiste. Wähle im Dropdown-Menü die Option "Sicherheitsproblem melden" (Report Security Issue). Es erscheint ein Formular mit dem Tag "Sicherheit" und einem Link zu speziellen Anweisungen zum Melden von Sicherheitslücken.
 * A subtask of an existing task: click Edit Related Tasks… > Create Subtask located in the right column of the current task. The dependency between both tasks will be set, and some values of the parent task will be carried by default (Assigned To, Subscribers, Priority, Projects). The connection between two tasks will be shown in the "Task Graph". Please review and adjust the project tags and the subscribers before creating a subtask!

Fill the form, leaving the fields you are not sure about unchanged.

Phabricator supports some formatting in text areas. See.

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  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 [mailto:task@phabricator.wikimedia.org task@phabricator.wikimedia.org]. 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.,. 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. See custom forms.

Task status and life cycle
See 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:


 * Mentioning users as in  will create a link to their profile and will subscribe them to the task.
 * Adding a task number as in  will create a link to the task including a hover card.   inserts the title of the task in your text.
 * Adding a project name as in  will create a link to the project main page.
 * If you want to quote text, you can simply add " " at the beginning. If you want to reply a comment including it as a quote, click the drop down arrow at the right end of the comment you want to reply.
 * If you want to display an uploaded mockup image file, e.g., like, embedded in your comment, write.
 * If you want to create an external link, e.g.  in wiki markup, use Markdown syntax in Phabricator:
 * If you want to add a web address (URL link) in a comment for example to provide a testcase, copy and paste the full web address from your web browser's address bar, e.g., . Do not use  . Interwiki prefixes like   are not supported in Phabricator.
 * If you want to paste lines of code, add a line with three backticks before and after the code: . You can also indent two spaces. Or create a Paste and link to the Paste from the task.
 * Use  to define list items with checkboxes in the task description. Change it to   to resolve a list item.

Uploading file attachments
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  in a comment. This will create a link to the file. To include the file in the comment, enclose the ID in braces:. 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. 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…


 * when you have an established team running one or several projects (start here, ask more only when you need more)
 * when you need a workboard (i.e. a sprint)
 * when you need a tag or keyword to organize a type of task that can be part of any project (for example "Accessibility")

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:


 * Blockers and Subtasks. A (parent) task might simply be blocked by another (sub)task, representing a dependency (see Special:MyLanguage/Phabricator/Project management on how to add a subtask).
 * Tracking. A "workless" (parent) task blocked by several (sub)tasks might be tracking a collection of (sub)tasks within a release or other time period. Note that "Tracking" here has a different meaning from the deprecated #Tracking tag in Phabricator.
 * Approval. Several (parent) tasks (such as draft team goals) might be blocked by a single (sub)task which represents the draft tasks getting approved, after which those draft goals are now real goals.

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.

Prioritization
See Phabricator/Project management

Assignment
See Phabricator/Project management

"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.

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:


 * The global search at https://phabricator.wikimedia.org/search/query/advanced/, confusingly labeled "advanced search". This one is fairly simple. It is in the upper right corner. By default, it searches across all applications and hence all types of documents (open tasks, closed tasks, code commits, etc…). You can change the default context using the the arrow menu to the left of the search bar. For example, select "Open Tasks" to only show results in open tasks from the Maniphest issue tracker. Or select "Current Application" to search Maniphest in Maniphest, Diffusion in Diffusion etc. Tags specified are unioned (OR'd).
 * Advanced, application specific search, for example at https://phabricator.wikimedia.org/maniphest/query/advanced/ for Maniphest. This one has more fields, and auto-completion that includes "Not in:..." (equivalent to NOT) and "In any:..." (equivalent to OR) (for example, type "echo" in the "Tags" field). There is also an advanced search for most other applications (e.g. file/query/advanced for Files). To only search for tasks / bug reports, use the Maniphest advanced search. Tags specified are intersected (AND'd).

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:


 * Case insensitive:  is the same as
 * phrase search works:
 * basic tokenization is performed, e.g. to strip punctuation
 * Stemming is performed: "edited" is also found when searching for . However,   does not match   as quoted text does not stem.
 * Substring search is supported:  matches , but   does not.
 * matches  as quoted and substring-operator text uses substring search.
 * Boolean queries to exclude certain terms are possible by using the - symbol before the unwanted term. E.g. use  to exclude "non-fatal" errors from results.
 * To only search in a task title but not in the task description or comments, use  which is the same as  . To search for one term in the task title and other terms anywhere in a task, use   or  . See https://secure.phabricator.com/book/phabricator/article/search/ for more information.

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  (equivalent to NOT) and combine several projects via   (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.

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:


 * use the activity feed and edit the query to be restricted to certain projects or timeframes
 * use the activity feed to list all actions that you performed in a certain timeframe at feed/query/EW2FwdAi.Kfz/
 * use an external search engine;
 * remove all search terms, refine the search only by project etc. and then scan all the possible results manually or use Ctrl+F to search specific strings (this might require setting "Page Size" to a high value to display more than only 100 results);
 * file a new task, mentioning that a past report exists as well, and wait for someone to merge the new report to the old.

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:
 * "02/25/2015" - interpreted as "00:01 on February 25th, 2015" (UTC)
 * "5 days ago" - interpreted as "00:01 on the fourth calendar day before today" (UTC)
 * "2:45 AM 5 days ago" - interpreted as "02:45 on the fourth calendar day before today" (UTC)

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:


 * Use the line elements on the left to drag queries up and down in the list.
 * The "x" will permanently delete a Query.
 * The Pencil icon allows a user to edit the name of a query
 * Clicking on the name of a Query will bring up the search options and results of that query

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.

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.

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.

Favorites
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".

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.

MediaWiki templates and links

 * You can link to Phabricator tasks from wiki pages using  and its shorter version , for instance   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.

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.

Statistics
Phabricator offers tables showing the open tasks by priority and by either user or project. On every project page you also find a "Reports" link to a Burndown chart for that project. 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.

Phragile and Phlogiston are further external reporting tool options for Phabricator which were developed by Wikimedia developers.

Exporting task data
The results of an Advanced Search query on 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)


Diffusion is the Phabricator repository browser. Another option is using gitiles at https://gerrit.wikimedia.org/r/plugins/gitiles/?format=HTML 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)


Phabricator allows some customization of the fields shown for a given task. These are handled via the Forms feature.

API (Conduit)
Conduit is the name of the web API. https://phabricator.wikimedia.org/conduit/ offers some explanation and examples. See the Conduit upstream documentation. Also see Phabricator/Bots.

Phatality
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.

Other links

 * Other
 * OAuth consumer phabricator-production, use Special:OAuthManageMyGrants to manage connected apps
 * Phabricator etiquette