Phabricator/Help/pl

Drogi użytkowniku Phabricatora, jeżeli masz pytania, zapytaj na stronie Dyskusji. Ulepszamy naszą dokumentację na podstawie otrzymanych opinii. Jeżeli chcesz testować Phabricatora, powinieneś użyć instancji Cloud Services. (Instancja testowa niestety nie zawsze jest w trybie online).

Aby uzyskać podstawowe informacje o tym, czym jest i co może zrobić Phabricator,. Lub czytaj dalej tę stronę, aby zacząć od razu.

There are also if you have a low bandwidth. Or keep reading this page to dive right in and get started.

Tworzenie konta
Możesz połączyć swoje nowe konto Phabricator ze swoim globalnym kontem wiki Wikimedia lub z kontem programisty Wikimedia. W obu przypadkach nie jest potrzebne oddzielne hasło.

Z globalnym kontem wiki
When in doubt you can use your Wikimedia username, but note that Phabricator usernames cannot include non-ASCII characters such as العَرَبِيةُ or 中华民族 or Xï, nor spaces. Instead of a space, use an underscore " ". You will also need to provide a valid email address for verification, but your address will not be visible to other users.
 * Na początku, upewnij się, że jesteś w Wikimedii. ** Jeśli nie masz konta w Wikimedii,.
 * Przejdź do Strony logowania Phabricatora (link jest wyświetlany jako strzałka do drzwi w prawym górnym rogu, gdy jesteś wylogowany).
 * Kliknij przycisk słonecznika z napisem „Zaloguj się lub zarejestruj - MediaWiki”.
 * MediaWiki.org poprosi Cię o zgodę na połączenie.
 * Phabricator zapyta Cię o nazwę użytkownika. W razie wątpliwości użyj swojej nazwy użytkownika Wikimedia, ale pamiętaj, że nazwa użytkownika Phabricator nie może zawierać znaków innych niż - ASCII, takich jak العَرَبِيةُ lub 中华民族 lub Xï, ani spacji (użyj tylko podkreślenia „ ”). Prawidłowy adres e-mail będzie również wymagany do weryfikacji, ale nie będzie pokazywany innym użytkownikom.
 * Kliknij Zarządzaj (Manage) na pasku nawigacyjnym po lewej stronie.
 * Click Edit Profile and fill in the "Also Known As" field (for example, with your full name) to make it easier for others to find you.

Z kontem programisty Wikimedia

 * Jeśli masz konto programisty Wikimedia &mdash; znane również jako konto LDAP, konto Gerrit lub konto wikitech - możesz go również użyć do zalogowania. Ta sama nazwa użytkownika Phabricator może mieć podłączone zarówno MediaWiki.org, jak i LDAP. Może to być kopia zapasowa, w mało prawdopodobnym przypadku, gdy Wikimedia SUL nie działa.

Uwierzytelnianie wieloskładnikowe

 * „Nie” zachęcamy do korzystania z uwierzytelniania wieloskładnikowego w Wikimedia Phabricator z wyjątkiem sytuacji, gdy masz dostęp do zadań bezpieczeństwa. Jeśli nadal planujesz z niego korzystać, przeczytaj najpierw wytyczne i wymagania dotyczące uwierzytelniania wieloskładnikowego, a następnie skonfiguruj, jeśli nadal chcesz.

Accessing Phabricator

 * Ze względu na ciągłe nadużycia, dostęp do Phabricatora jest zablokowany dla niektórych adresów IP z określonych krajów (takich jak Egipt). Niektóre (ale nie wszystkie) serwery proxy, VPN i węzły wyjściowe Tora są również blokowane. Podczas uzyskiwania dostępu do Phabricator przy użyciu tych adresów IP, użytkownicy zobaczą błąd HTTP 500 lub 501. Jeśli Twoje IP jest zablokowane i nie możesz znaleźć użytecznego serwera proxy, aby uzyskać dostęp do Phabricatora, możesz skontaktować się z security@undefinedwikimedia.org, aby dodać swój adres IP do białej listy.
 * If you find that your Phabricator account has been disabled, please add a note on Talk:Phabricator/Help.

Email addresses
(Tylko jeśli nie jest to możliwe, skontaktuj się z Bugwrangler.) Nie możemy poprawić Twojego adresu e-mail, ale możemy usunąć Twoje konto, abyś mógł się ponownie zarejestrować.
 * Jeśli nie możesz zweryfikować swojego konta Phabricator, ponieważ podałeś nieprawidłowy adres e-mail, dodaj notatkę na Talk:Phabricator/Help.
 * If you see the error "Email address already taken" when trying to create a Phabricator account on the page "Login or Register - MediaWiki", you have likely already registered a Phabricator account that's connected to your Wikimedia developer account. You'll need to log into Phabricator using your developer account. You can reset your password: wikitech:Special:PasswordReset if you've forgotten your developer account password.

Changing accounts

 * Jeśli uznasz, że Twoje konto Phabricator jest wyłączone, dodaj notatkę na Talk:Phabricator/Help.
 * Jeśli chcesz zmienić swoje konto programisty, które jest połączone z kontem Phabricator: Zaloguj się do Phabricator za pośrednictwem globalnego konta wiki, które jest również połączone z kontem Phabricator.
 * First, note that your Phabricator account must at all times be associated with either a global wiki account or a developer account.
 * To change the global wiki account that's connected to your Phabricator account:
 * Log into Phabricator with the developer account currently connected to your Phabricator account. (Jeśli twoje konto Phabricator jest powiązane tylko z twoim kontem programisty, ale jeszcze nie z globalnym kontem wiki, najpierw połącz globalne konto wiki z kontem Phabricator.)
 * Under Settings: External Accounts, remove your old global wiki account and connect your new global wiki account.
 * To change the developer account that's connected to your Phabricator account:
 * Log into Phabricator with the global wiki account currently connected to your Phabricator account. If your Phabricator account is only connected to your developer account but not to any global wiki account, you must first connect a global wiki account to your Phabricator account.
 * Under Settings: External Accounts, remove your old developer account and connect your new developer account to your Phabricator account.

Other issues
To claim your old Bugzilla and/or RT account(s), click this link.

Otrzymywanie aktualizacji i powiadomień
Phabricator powiadamia Cię o odpowiedniej aktywności, w tym o własne działanie.

Phabricator oferuje kilka narzędzi do otrzymywania powiadomień, które chcesz otrzymywać.


 * Jeśli interesuje Cię pojedynczy obiekt (zadanie, makieta…) po prostu kliknij  na jego stronie. Dodanie komentarza spowoduje automatyczną subskrypcję.
 * Jeśli interesuje Cię cała aktywność w projekcie, możesz kliknąć  na stronie podsumowania projektu. Więcej informacji można znaleźć w podręczniku użytkownika Projects w sekcji „Oglądanie projektów”.

Zobacz, aby dowiedzieć się, jak zmniejszyć liczbę powiadomień e-mail i filtrować powiadomienia e-mail.

Rozwiązywanie problemów
Jeśli otrzymujesz nieoczekiwane powiadomienia e-mail dotyczące zadania:


 * Może mogłeś być zapisany do zadania.
 * Możesz być członkiem projektu lub podprojektu związanego z tym zadaniem. Dostępna jest lista wszystkich projektów, których jesteś członkiem.
 * Może oglądasz projekt powiązany z tym zadaniem. Dostępna jest lista wszystkich projektów, które obserwujesz.
 * W Twoich preferencjach e-mail w sekcji „Maniphest Tasks” mogłeś włączyć opcję „Jedno z zadań podrzędnych zmienia stan”.
 * Możesz mieć skonfigurowaną osobistą Regułę Heralda. Sprawdź "X-Herald-Rules" pole nagłówka wiadomości, aby zobaczyć listę wszystkich zastosowanych reguł Heralda.
 * Jeśli nic nie pomaga, sprawdź pole nagłówka wiadomości „X-Phabricator-Stamps”, aby uzyskać dalsze informacje. Zobacz.

Tworzenie bardziej złożonych reguł dla powiadomień (Herald)
Możesz stworzyć niestandardowe (osobiste) reguły powiadomień w Wikimedia Phabricator's Herald. Jest to bardziej zaawansowana opcja i może być trudna w użyciu i powinna być używana ostrożnie ze względu na wydajność.

Tworzenie zadania
Istnieje kilka sposobów tworzenia zadania, w zależności od informacji, które chcesz nieść:


 * Nowe zadanie: kliknij przycisk Zakładka po prawej stronie górnego paska nawigacji. Z menu rozwijanego wybierz Utwórz zadanie. Otrzymasz pusty formularz.
 * Problem dotyczący zabezpieczenia: kliknij przycisk Zakładka po prawej stronie górnego paska nawigacyjnego. Z menu rozwijanego wybierz opcję Zgłoś problem dotyczący bezpieczeństwa. Otrzymasz formularz z oznaczeniem „Bezpieczeństwo” i linkiem do specjalnych instrukcji dotyczących zgłaszania błędów bezpieczeństwa.
 * Podzadanie istniejącego zadania: kliknij Edytuj powiązane zadania…> Utwórz podzadanie znajdujące się w prawej kolumnie bieżącego zadania. Zależność między oboma zadaniami zostanie ustawiona, a niektóre wartości zadania nadrzędnego będą domyślnie przenoszone (Przypisane do, Abonenci, Priorytet, Projekty). Połączenie między dwoma zadaniami zostanie pokazane na „Grafie zadań”. Przed utworzeniem podzadania przejrzyj i dostosuj tagi projektu i subskrybentów!

Wypełnij formularz, pozostawiając niezmienione pola, których nie jesteś pewien.

Phabricator obsługuje pewne formatowanie w obszarach tekstowych. Zobacz.

Skorzystaj z podglądu na żywo na końcu strony, aby sprawdzić, czy tekst wygląda zgodnie z oczekiwaniami.

Wybór projektu
Aby powiązać zadanie z projektem (tagiem), który korzysta z Phabricatora, wystarczy zacząć wpisywać jego nazwę w polu "Tagi" i wybrać projekt z listy pasujących projektów (lista pokaże tylko pięć pasujących projektów). Możesz wyszukiwać projekty i czytać krótkie opisy projektów, klikając icon lupy w polu „Tagi”. Możesz dodać jeden lub więcej projektów do pola „Tagi”. Jeśli nie masz pewności, możesz również pozostawić je puste - triagery zajmą się zadaniami, które nie mają ustawionego projektu. Dostępna jest (długa) lista projektów. Naciśnij, aby wyszukać projekty. (Ta lista jest również dostępna pod adresem Phabricator/Projects.)

Ustawianie priorytetu zadania
Priorytet powinien zwykle być ustalany przez menedżerów produktu, opiekunów lub programistów, którzy planują pracę nad zadaniem, lub przez zgłaszającego błędy lub doświadczonych członków społeczności, a nie przez zgłaszającego, który zgłasza błąd lub przez zewnętrznych obserwatorów. Zobacz Phabricator project management po szczegóły.

Korzystanie z poczty elektronicznej (email)
Możesz także tworzyć zadania, wysyłając e-mail do [mailto:task@phabricator.wikimedia.org task@phabricator.wikimedia.org]. Temat zostanie użyty jako tytuł zadania, treść zostanie użyta bezpośrednio w postaci, w jakiej jest, a załączniki zostaną dołączone do zadania. Aby ustawić projekt, dodaj odpowiednie polecenie "!projects” i jego hashtag na początku treści, np. . Dostępne są dalsze polecenia do ustawiania osoby przypisującej zadanie, priorytetu lub statusu za pośrednictwem email.

'' Uwaga: jeśli Twój podpis e-mail nie jest sformatowany zgodnie z de facto standardami (w tym „--” do oddzielenia od tekstu podstawowego), również zostanie opublikowany. Zachęcamy do usunięcia prywatnych informacji ze swojego podpisu za pierwszym razem, dla pewności. ''

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:

Do not use. Interwiki prefixes like  are not supported in Phabricator. You can also indent two spaces. Or create a Paste and link to the Paste from the task.
 * 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.,.
 * If you want to paste lines of code, add a line with three backticks before and after the code:.
 * Use  to define list items with checkboxes in the task description. Change it to   to resolve a list item.

Przesyłanie plików z załącznikami
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.

Zarządzanie projektami
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.

Priorytetyzacja
See Phabricator/Project management

Przypisywanie
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:

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 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).
 * The global search at https://phabricator.wikimedia.org/search/query/advanced/, confusingly labeled "advanced search".
 * 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.

You can search for specific task IDs by leveraging a hidden "IDs" field, revealed when a search URL takes the following format: https://phabricator.wikimedia.org/maniphest/?ids=1,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.

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

MediaWiki templates and links

 * You can link to Phabricator tasks from wiki pages (via interwiki linking) using  and its shorter version , for instance   generates [[phab:T454|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.

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

Get Notified about new UBN Tasks
See Setup UBN Notifications

Inne linki

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