- #Bugzilla migration update
- #Bugzilla migration software
- #Bugzilla migration code
You can help by providing feedback and code.īugzilla users might miss some features that Phabricator still lacks, or is not pursuing.
We can have specific teams with specific permissions whose members could add new members, rather than relying on admins only.īelow you can find a selection of known issues. We can decide who can create projects, rather than only let a few administrators do so. Tasks needing triaging appear at the top of lists (including search results) and in personal dashboards of the members of the affected projects. #Bugzilla migration update
Note that the wikibugs-l mailing list does not yet receive update notification emails from Phabricator ( T763). Also see Phabricator/Help#Receiving updates and notifications for more information. "email me when someone mentions (your regexp here)". Herald allows you to create custom notifications based on queries, e.g. Hence you do not need to ask Bugzilla admins anymore if they can add you to the default CC list of a Bugzilla component to receive mail notifications for all changes. You can become a member of a project and subscribe to a project in Phabricator. Web notifications show activity relevant to the tasks you are subscribed to (once enabled, see T1047). More general information: Phabricator/Help#Writing comments and descriptions. If you add a comment or edit a task while someone else is doing the same, your Subscribers/CC list changes might overwrite or might get overwritten. You can hide your own comments (admins can make them visible or delete them for good). You can edit your own comments (with history). You can add files and inline images to comments with a simple drag & drop. Enjoy auto-saved comments while you type. Documentation: Phabricator/Help#Creating a task. A toolbar allows to add Phabricator's specific markup. The description ("comment 0") of a task can be edited by multiple users (with history/diffs available) to evolve the task and summarize long discussions. Type-ahead to select projects, instead of browsing products/components to find the destination. Simple form for newcomers with title, project, CCed users (subscribers), description, assignee and priority. Tasks can be assigned to multiple projects or to none. You can also see in which column/status of the project board the task is currently. #Bugzilla migration code
Explicit titles of tasks, code reviews, and mockups related to the task, without needing to click or memorize numbers.We get project boards ( example) and mockups with notes ( example).Reporters, developers, designers, and product managers use the same tool to discuss bugs/features and report progress.No more "this is not a bug, doesn't belong here" or "this report is being tracked in Mingle/Trello" Tasks can be bugs, and they can be tasks.
However, a "Send Message" button in Phabricator profiles is available via Conpherence since April 2015, see phab:T91392. Private communication is no longer as easy as sending an email we have to figure it out still.
Your email address is private, at last. Log in with your Wikimedia unified login (aka single user login or SUL) or (LDAP) credentials ( T346) - see Phabricator/Help#Signing in. In some special cases (Operations procurement) non-registered users can also interact via email ( T52). Most features are mobile friendly as well. 
by having separate modes for displaying and editing certain report information while bugzilla only collapses advanced fields in bug filing and bug searching windows). The Phabricator UI sometimes hides more complexity than Bugzilla (e.g. On this basis, Phabricator refused to implement some bugzilla features intended to make life easier for inexperienced users.
#Bugzilla migration software
Unlike Bugzilla, the Phabricator UI is primarily designed for software development and not for average non-technical users (according to upstream). 
Phabricator comes with many improvements over Bugzilla.
0 kommentar(er)
