From Meta
This page is a translated version of the page Phabricator and the translation is 6% complete.
Outdated translations are marked like this.
Miraheze White Logo.png

Miraheze's issue tracking platform. Report bugs, request features, and more!

Report bugs/anything else Report security issue Request custom domain Request configuration changes

Phabricator기능 요청, 버그 제보 등을 위해 사용하는 이슈 트래킹 소프트웨어입니다.

Pictogram voting info.svg Note: Phabricator is only for technical issues! If you require assistance with something non-technical in nature (i.e. adoption requests, disruptive users, help with CSS, etc.), please ask on the Community noticeboard or Stewards' noticeboard.

기술적인 정보는 여기에서 확인할 수 있습니다.


Creating an account/Logging in

Error: no text specified (help).

To create an account or log in, please use the following steps:

  1. Go to Phabricator.
  2. If you are not logged in, click "Log In" at the top right.
  1. On the next page, click the "Log In or Register // MediaWiki" button at the bottom right (this logs you in to your Miraheze account).
Pictogram voting info.svg Note: Always click the "Log In or Register// MediaWiki" button at the bottom right. Do not log in straight from Phabricator, that login prompt is not for wiki users.
  1. If prompted, sign into your Miraheze account.
  1. A prompt appears asking you if you want to allow Miraheze Phabricator to log you in, click "Allow".
  1. If you haven't made an account already, you will be asked to confirm your username and add your email.
Below are images that may assist you in this process, the images show how each screen/step should look. Each image is labelled what step it corresponds to.
Extended content
Main Screen for Phabricator (Step 1/2)
Phabricator Login screen. Click the "Log In or Register // MediaWiki" button at the bottom right (Step 2a)
Meta Login Screen (Step 3)
OAuth screen asking for permission to log you into Phabricator, click Allow (Step 3a)
Phabricator Create Account Screen (Step 4)

Filing tasks

Once you are logged in, click the links at the top of the page to file tasks. Alternatively, if you click "Maniphest" in the Main Page, a button titled "Create Task" should appear.

When making requests, title them descriptively. For example, if you encounter a bug such as a database error on your wiki, a good title could be "Database errors on "".

Pictogram voting info.svg Note: Unless you have been instructed to, do not assign the task to anyone (including yourself). System administrators assign tasks to other system administrators, users, or even to themselves to help track the task's progress. Additionally, unless the task is an urgent one (such as errors on all wikis, downtime globally, etc.), do not set the priority to "High" or "Unbreak Now!". This does not cause your request to be processed faster. Even if your wiki is inaccessible, you should leave the priority at "Needs Triage" or "Normal" and a system administrator will change it if needed.

Pictogram voting info.svg Note: Do not fill in "Tags" or change "Subscribers" if you do not know what you are doing. Leave them blank and if needed, someone will change them.

In the description of the task you are creating, be descriptive on the issue or feature you are requesting. If your task is regarding a wiki in particular, please link to it. If the task you are creating is using a template (e.g. Custom domain requests, security issues, etc.), please follow the guidelines laid out on the page.

Once you have filled out your request, a system administrator will process it shortly. Please have patience if your task is not dealt with immediately!

Who can file tasks?

All Miraheze users are free to file bug reports and to give feedback. However, for more sensitive issues such as custom domain requests, article imports, database name changes, changing of restricted settings, among others, only bureaucrats should files those tasks. Even if you are a sysop, it is recommended a bureaucrat files the task.

요청 및 제보

  • 위키에 (ManageWiki에 없는) 확장 기능이나 설정 변경을 요청하려면 이 양식을 사용하세요.
  • 버그 등을 제보하려면 이 양식을 사용하세요.
  • 보안 문제를 제보하려면 이 양식을 사용하세요.

기술적인 자세한 정보를 보려면 Tech:Phabricator 문서를 보세요.

작업 분류

  • 모든 기능 요청과 대부분의 설정 변경은 기본적으로 "Normal"로 분류됩니다. 요청이 빠르게 처리되도록 하기 위해 요청의 우선 순위를 변경할 필요가 없습니다. 모든 기능 요청과 설정 변경은 선착순으로 처리되며, 이전 요청이 완료되었을 때 처리됩니다.
  • "High" 우선 순위는 전체 농장에 영향을 끼치는 문제나 한 위키에 중대한 영향을 끼치는 문제에 사용됩니다. "Unbreak Now"는 긴급한 문제나 농장이 다운되었을 때 사용됩니다.
  • Miraheze의 직접적인 기능에 대해 중요하지 않은 작업, 단순 아이디어나 현재 처리될 수 없는 작업은 "Low"로 분류됩니다.

Additionally, there are also statuses on Phabricator:

  • Open: Tasks that are currently waiting on someone to take care of them, or that are in progress.
  • Resolved: Tasks that have been completed.
  • Invalid: Tasks that are inappropriate for Phabricator and the request should have been made somewhere else.
  • Declined: Tasks that either can't be done at this time, won't be done or the conclusion was that it was not needed at the time.
  • Stalled Tasks that are waiting on an external entity to respond before any further action from us can be taken.

요청을 어떻게 분류해야 할지 확실하지 않다면, 시스템 관리자가 적절하게 분류하도록 놔 두세요.


  • 태그/프로젝트는 작업을 주제별로 정리하는 데 사용됩니다. 예를 들어 "Feature request for (example.miraheze.org에 대한 기능 요청)"이라는 작업에는 모든 기능 요청과 설정 변경에 사용되는 "Configuration" 태그가 추가될 것입니다.
  • 검토가 필요한 확장 기능에는 Extension-Review 태그가 추가될 것입니다.
  • Miraheze 및 그 서버의 일반적인 구동과 관련된 작업에는 Operations 태그가 추가될 것입니다.
  • 다양한 용도로 사용되는 셀 수 없는 다른 태그들이 있습니다. 여기에서 볼 수 있습니다:


There are different types of projects/tags that are used on Phabricator. The current configuration is as follows:

  • Projects / Components
    • These represent the bulk of projects within Phabricator and belong to an area of either software, infrastructure, or activity.
    • Icon: Project
    • Colour: Blue
  • Groups
    • These represent entities of people and serve as a common association for tasks which require involvement or engagement from a certain group or for a group who may be a stakeholder in a task's progression.
    • Icon: Group
    • Colour: Violet
  • ACLs
    • Similar to groups except these are used for controlling access to certain tasks, with their group membership heavily restricted.
    • Icon: Policy
    • Colour: Red
  • Tags
    • Tags represent common objectives or issues that aren't Project-specific.
    • Icon: Tag
    • Colour: Yellow
  • Goals
    • Goals are most commonly our bi-annual planning period objectives.
    • Icon: Goal
    • Colour: Green
  • User
    • User projects can be used to allow a user to categorise tasks easily within a project rather than tracking it via other means such as notifications. Useful for monitoring progression of tasks across a workboard.
    • Icon: Timeline
    • Colour: Checkered

Access Policy

This outlines access to certain ACLs and Administrator privileges on Phabricator.


Phabricator Administrator is not a powerful tool; however, it has access to certain protected information about user accounts and can see sensitive information such as 2-Factor Authentication Status.

Currently, Phabricator Administrator rights have only been granted to Site Reliability Engineers, who already maintain root access on the relevant Phabricator servers. This policy can be reviewed if a use-case can be presented by any member who is not eligible for the rights currently.

ACL: Security

This ACL allows tasks to be restricted from public view when the contents being public could cause a risk to Miraheze's operations, software security or data protection. This ACL can additionally be used when such information could pose a risk to other services until a reasonable disclosure period has passed - when Miraheze may make such information public.

Membership to the group is restricted to:

  • Site Reliability Engineering
  • Trust and Safety
  • Board of Directors (when they take an active part in compliance/regulatory business of the company)

Anyone, who requires access to a certain task, can be added as a subscriber without ACL membership.


Digests of Phabricator Search Queries are available using the PhabDigests tool powered by the volunteer FOSSBots project. This will require your email to be given to volunteers, and the information is not covered under the Miraheze NDA or Privacy Policy. Data stored on this system is subject to a separate privacy policy.

Please contact RhinosF1 or ask in #fossbots 접속 if you would like a digest.


기술적인 자세한 정보를 보려면 이 문서를 보세요.