Phabricator/Help/es

Estimado usuario de Phabricator, si tienes preguntas, realízalas en la página de Discusión. Mejoramos nuestra documentación gracias a la retroalimentación. Si deseas hacer pruebas con Phabricator, usa la instancia en Labs.

Para usuarios con conocimientos avanzados, accede al siguiente enlace. Si eres un usuario nuevo, continúa leyendo la guía.

Crea tu cuenta



 * Primero, asegúrate de haber en Wikimedia.
 * Si no tienes una cuenta,.
 * Ve a Phabricator login page (el enlace muestra una flecha y una puerta al cerrar sesión).
 * Haz click en el botón del girasol que dice ¨Login or Register-MediaWiki¨.
 * Se te preguntará mediante MediaWiki.org para aceptar la conexión.
 * Phabricator pedirá un nombre de usuario, pero puedes usar el de Wikimedia. Recuerda que Phabricator no incluye carcateres no latinos (العَرَبِيةُ o 中华民族). También se requerirá una dirección de correo electrónico, la cual permanecerá oculta para el resto de usuarios.
 * Si tu cuenta de Phabricator está deshabilitada, añade una nota en Talk:Phabricator/Help. If you do not receive timely feedback, contact the Bugwrangler.
 * Haz click en Manage en la barra de navegación izquierda.
 * Luego dirígete a Edit Profile y edita tu Also Known As (también conocido como). Esto permitirá que sea más sencillo encontrarte.


 * Avanzado
 * Si tienes una cuenta en wikitech.wikimedia.org (también conocida como cuenta LDAP o Gerrit), puedes utilizarla para iniciar sesión. Un mismo usuario de Phabricator puede tener enlazadas una cuenta de WikiMedia.org y LDAP al mismo tiempo, sirviendo como respaldo en caso de que Wikimedia SUL deje de funcionar. ¡Fusiona tus cuentas SUL y LDAP en un solo usuario de Phabricator!. De todos modos puedes crear 2 cuentas diferentes.
 * Nosotros "no" fomentamos el uso de la autentificación multi-factor en Wikimedia Phabricator. Si aún quieres utilizarlo, lee guías y requerimientos para la autentificación multi-factor.

Solicitando tus cuentas de Bugzilla y RT
Sigue este enlace

Recibiendo actualizaciones y notificaciones
Phabricator te notifica sobre actividad relevante, incluyendo tus propias acciones. Puedes cambiar las preferencias de correo electrónico a tu gusto, desde filtrar acciones específicas hasta no recibir ninguna notificación.

Phabricator ofrece varias herramientas para filtrar y recibir notificaciones que te interesen.

Puedes definir tus preferencias de correo electrónico para acciones específicas dentro de un task (como estado, prioridad, autor o cambios en las suscripciones). Los usuarios prolíficos suelen reducir al mínimo sus notificaciones mediante File:Phabricator email settings panel.png. Como miembro de un proyecto, puedes deshabilitar los correos electrónicos mediante  en la página Members. Puedes encontrar más información en la guía Managing Phabricator Email.
 * Si solo deseas estar atento a un asunto (un task (tarea) o mockup (bosquejo)) haz click en . Si comentas, te suscribirás automáticamente.
 * Si te interesa toda la actividad de un proyecto, haz click en . There is more information in the Projects user guide under "Watching Projects".

Creando reglas de anuncios para notificaciones
Sigue este enlace para aprender a crear reglas de notificaciones personalizadas en Wikimedia Phabricator's Herald. Es una opción avanzada y puede ser difícil de usar.

Crear una tarea

There are several ways to create a task, depending on the information you want to carry: Rellene el formulario, dejando los campos en los que no está seguro sin modificaciones
 * A new task: click the Star button toward the right side of the top navigation bar. From the dropdown menu, choose Create Task. You will get a blank form.
 * A security problem: click the Star button toward the right side of the top navigation bar. From the dropdown menu, choose Report Security Issue. You will get a form pre-tagged with Security, and with a link to special instructions for filing security bugs.
 * 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). Subtasks will be listed in the parent task under "Task Graph", sorted by most recently updated.

Formato
Phabricator supports some formatting in text areas. See this help about formatting in Phabricator.

Seleccionar proyectos
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.)

Establecer el grado de prioridad de una tarea
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 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.

Esta es una característica muy avanzada. Más información aquí.

Escribir comentarios y descripciones
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 Remarkup. At the end of the page you have a live preview to check whether your text looks as you expect. 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   including the whitespaces in Phabricator.
 * If you want to add a web address (URL link) in a comment for example to provide a testcase, it is highly recommended to copy and paste the full web address from your web browser's address bar, e.g.,  instead of  . Interwiki prefixes like   are not supported in Phabricator and most customizations that Bugzilla had neither, e.g., Gerrit changes should be pasted as full web addresses too.
 * If you want to paste lines of code, add a line with three backticks before and after the code: . Or create a Paste and link to the Paste from the task.

Note that Phabricator's own markup language is different from MediaWiki's markup. The upstream Phabricator instance hosts a Remarkup Reference for Phabricator's own markup language.

Subir archivos adjuntos
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:. Se incluye de forma predeterminada como miniatura. For more formatting options, visit Remarkup reference. 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.

Advanced users could also use "arc upload" which provides an F number that can be used via  syntax to embed in a comment.

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

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.

Administración de proyectos en Phabricator
Si mantienes o administras un proyecto, sigue este enlace para obtener más información.

Tareas padre y subtareas
Una tarea puede ser padre o subtarea de cualquier número de otras tareas. Estas relaciones se pueden establecer a través de "Edit Related Tasks...". Esta funcionalidad se puede usar para hacer unas cuantas cosas:

Parent tasks and subtasks are displayed under "Task Graph" in the task. NOTE: There is a "Edit Related Tasks... > Create Subtask" feature. In addition to setting up the correct parent/subtask relationship, it also caries the CC (subscription) list into the new subtask.
 * Bloqueadores y subtareas. Una tarea (padre) puede ser bloqueada sin más por otra (sub)tarea, dando lugar a una dependencia (véase Phabricator/Project management para saber cómo añadir una subtarea).
 * Seguimiento. Una tarea (padre) «inactiva» bloqueada por varias (sub)tareas en realidad puede estar haciendo seguimiento de una colección de (sub)tareas para un mismo lanzamiento u otro periodo de tiempo (véase #Tareas de «seguimiento»).
 * 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.

Priorización
Each Task has a Priority field, which is reflected in the sidebar color of Tasks that appear in Workboards. Note that this Priority is inherent to the Task, and thus will be the same in every Project and Workboard that task appears in.

Within a Workboard, Tasks can be arranged in a priority order within a column. Choose "Natural" sort, and then drag-and-drop Tasks up or down within a column. This allows a groomed backlog to be sequenced by priority, or could indicate the urgency of items in a "Needs Review" column. Note that Workboard columns can also be sorted by the underlying Priority field, so while discussing a Workboard with someone not in the room, it is best to agree on and use the same sort order to avoid confusion.

Assignment
Each Task may be assigned to one person. As with Priority, this is inherent to the Task, and affects every Project that Task is in. So it is impossible to have a Task assigned to Robin in one Project, but to Kim in another. The assigned person is displayed as part of the Task card in each Workboard.

Some teams might choose to assign Tasks to people while the Tasks are in a TODO column. Others would have people assign Tasks to themselves only at the moment that they are moving them from TODO to DOING. Assigning a Task to yourself before you are ready to work on it is a form of "cookie licking".

After the main work on a Task is finished, there are 2 main patterns for assignment:


 * The Task remains assigned to whoever did the work, as that task's permanent owner
 * The Task gets reassigned to whoever needs to work on it next

So for example, after code has been written, it might needs a code review from some specific person. In the second case, the Task would be assigned to that person, making it clear who is responsible for moving that task forward. Obviously if there are multiple possible code reviewers, that model would not work. Later, if the issue were waiting for someone to test it, or deploy it, or to run some specific task necessary for the Task to be completed (like a re-index), the Task could be assigned to that person. A team might have a policy that completed tasks should get assigned back to the person who originally created them, so that person can verify that their needs were met, and the task is ready to be closed.

"Hecho"
Each Task has a Status field, which includes the state of Resolved. Resolved tasks are by default hidden from Workboards. When they are displayed, they appear grayed out and struck out. Other statuses include Open and Stalled.

Note that this Resolved status is inherent to the Task, and so will affect that Task's appearance and behavior in every Project (and Workboard) it is in. This is independent of which column a Task might be in, in any given Workboard. So a Task could be Open, and could be in the DONE column of one Workboard, but the DOING column of another. It could also be in the column somewhere else.

As a result, it is important not to mark a task Resolved until it is considered done by ALL of the projects it is in. It's fine to move a Task to your own Workboard's DONE column, but before you mark a task Resolved, ensure that no other project still wants to keep tracking its progress.

Tareas de «seguimiento»
Este término proviene de Bugzilla, donde tenía un significado específico: una tarea bloqueada por otras tareas pero que, por sí misma, no conllevaba ningún trabajo ni estaba ligada a un lanzamiento o a una fecha específica. Un ejemplo sería una tarea titulada «Limpiar la documentación», que podría tener una serie de subtareas, cada una de las cuales describiría algún tipo de trabajo que hacer. Estas tareas de «seguimiento» tendían a permanecer mucho tiempo (o para siempre), ya que sus subtareas originales acabarían resolviéndose, pero a su vez se crearían tareas nuevas. En Phabricator, es mejor crear una (etiqueta) Proyecto para categorizar este tipo de trabajo.

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


Phabricator consists of several applications (task management in "Maniphest" being one of them, and in the future also Diffusion and Differential for code review). The search field in the upper corner allows searching across all these applications.

Using Maniphest (Advanced Search)


Maniphest is a tool which allows users to make detailed queries. Users can refine a query using multiple parameters. Queries can also be saved and managed.

New users will find several saved queries preset inside Maniphest. Clicking on the "Advanced Search" will bring up a new search page.

Click here for a detailed Maniphest walkthrough.

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 is not typically easily reversed, especially the larger the batch. To mitigate this, you can manipulate the URL of a prepared batch edit, and capture the task IDs in the batch. Do this before executing the batch, by copying the "?ids=" part of the URL in the prep stage of a batch change (and it is not possible not after, so when in doubt do it). If you apply that to a Maniphest query, you get the IDs, and can save the query or the URL for later use. See also this this comment for a hack to bulk edit tasks on a workboard.

Favorites
The Star menu in 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.

Crear un proyecto


In Phabricator projects are tags, tags are projects. Hierarchy via sub-projects is available since February 2016. Tasks can be assigned to more than one project, and they can also be submitted without assigning them to any project.

¿Cuándo necesitas un proyecto?
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")

Solicitar un nuevo proyecto
See Phabricator/Requesting a new project.

Restringir el acceso a las tareas
Please see Phabricator/Security for a general overview and for the "Security" dropdown option in tasks. See Phabricator/Creating and renaming projects for default project settings (and using Spaces).

Mostrar y utilizar un Espacio


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

Plantillas y enlaces de MediaWiki

 * Puedes enlazar a tareas de Phabricator desde páginas wiki mediante  y su versión abreviada  . Por ejemplo,   genera 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.

Usar Conpherence
Conpherence es una aplicación de Phabricator que permite realizar conversaciones privadas entre dos o más usuarios, de forma similar a la mensajería instantánea y a las salas de chat privadas. No se sabe de ningún equipo que utilice esto. Puede entrar en conflicto con otros canales de comunicación. Para aprender más, haz clic aquí.

Conpherence has an optional persistent window/column that can be shown and hidden with the keyboard key "\". Users may accidentally activate this feature, and it can only be hidden again by using the "\" key (there is no graphical UI feature to close it).

Estadísticas
Phabricator offers tables showing the open tasks by priority and by either user or 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 reporting tool options for Phabricator.

Difusión


Diffusion is the Phabricator repository browser and repository management tool. Eventually we want to replace Gerrit for code review and repository management, and gitblit for repository read-only mirroring. Right now, we're mirroring some of our Git repositories to Phabricator for demonstration purposes.

Forms


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

Otros enlaces

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