Phabricator/Bugzilla Equivalents
Some common tasks in Bugzilla do not have direct analogues in Phabricator and others may not be obvious to a new user. This page serves to document these common tasks and how similar situations should be handled when using Phabricator.
Tasks
Querying for Information
Query a user's review queue
You may query a user's review queue by crafting an advanced differential search query. Take the following steps:
- Visit this example query page: https://phabricator.services.mozilla.com/differential/query/IeE2zgiqj9EX/
- Change "Responsible Users" to the user you're interested in.
- You probably do not want "Exact User: <username>" as it excludes revisions for the user's projects.
- Click "Search".
- The user's review queue are items under the "Must Review" and "Ready to Review" headings.
Query a user's activity
You may query a user's activity by visiting their profile page: https://phabricator.services.mozilla.com/p/<username>/. An example user's profile page is here: https://phabricator.services.mozilla.com/p/bzbarsky/. The "Recent Activity" box lists only recent activity, but you may click the "View All" button to be taken to an advanced query of the user's activity.
Save a frequently used query
Most query advanced query pages will have a "Save Query" button on the results page. Clicking this will allow you to give the query a name and add it to your personal query list. After saving a query you can share it with others by copying the URL of the results page (Note, this url does not include the saved query name and is quite opaque).
Making requests to other users
Make a needinfo? request
Phabricator does not have a feature directly comparable to Bugzilla's needinfo? request. We suggest one of the following alternatives:
- Use an @ mention. Including @<username> in a comment on Phabricator will notify the provided user of your message. This is a one-time notification which does not require acknowledgement, so it is best to make it clear with your text that you expect a response.
- Add the user as a blocking reviewer and indicate your intent by including a comment. This will prevent the Phabricator revision from becoming Accepted until the indicated user has either Accepted the revision, Resigned as a reviewer, or been removed as a reviewer. Since this is re-purposing the normal request for review it is best to include a comment making your intended use clear.
Request feedback? on a patch
Phabricator does not distinguish between asking for final review and requesting other forms of feedback. It is best to use an explicit comment explaining you would like feedback, along with one of:
- Requesting review from the user you'd like feedback from.
- Using an @ mention. Including @<username> in a comment on Phabricator will notify the provided user of your message. This is a one-time notification which does not require acknowledgement, so it is best to make it clear with your text that you are expecting feedback.
Request review? on a patch
TODO: moz-phab, add reviewer, blocking vs non-blocking.
Clear a review? flag from your own patch
TODO: plan changes vs edit reviewers.
Clear a review? flag asked of you
TODO: request changes vs resign.
Request uplift approval on a patch
TODO
Request checkin-needed to land your changes
TODO: Move to phabricator tag.
Request review? of an image file
TODO: Pholio
Request sec-approval? on a patch
TODO