This is a tracking bug for the Bugzilla -> Maniphest (Phabricator issue tracker) import script so we can keep track of subtasks that are specifically about the automated import.
Elements of a Bugzilla bug report:
* Status and Resolution: to be converted, T212
* Product (with potential access restrictions): not going to exist as products must have components, T43
** Note that products might be not "open for bug entry" so new tickets can be created
* Component: to be converted to projects, T43 - Note that components might be not "open for bug entry" so new tickets can be created. Wikimedia Bugzilla components contain interesting chars such as []()_./'!:
* Version: add to initial description in Maniphest task if value != "unspecified"
* Hardware / OS / Platform: add to initial description in Maniphest task if value != "All" or "---"
* See Also: add to initial description in Maniphest task if not empty
* URL: add to initial description in Maniphest task if not empty
* Priority: Keep/Convert, T268
* Severity: To be dropped, T102
* Target Milestone: TBD, T100, T101. (likely to become sprints). Phabricator roject type with a "delivery"/lorry/truck symbol.
* Assigned to / Assignee: Keep/Convert. TODO: Default mailing list accounts such as wikibugs-l@lwo, wikidata-bugs@lwo, Pywikipedia-bugs@lwo should be set up in Phab (see T453!) and to watch projects via Herald (see https://secure.phabricator.com/book/phabricator/article/herald/ ) which they have been subscribed to before in Bugzilla (can be checked via https://bugzilla.wikimedia.org/editusers.cgi ).
* Summary: Keep/Convert
* Keywords: To be converted to projects, T266
* Whiteboard: add to initial description in Maniphest task if not empty. More than 1600 tickets with a non-empty Status Whiteboard field.
** Also used by Scrumbugs to create burndown (T153) charts, all entries have the format "u=Teamname c=BugzillaComponentName p=IntegerNumberOfPoints s=YYYY-MM-DD", see e.g. https://bugzilla.wikimedia.org/show_bug.cgi?id=67128 or https://bugzilla.wikimedia.org/show_bug.cgi?id=63655
* (Personal) Tags: To be dropped. On 2014-07-09, there were 132 personal/non-public tags (DB table: "tag") in use in Bugzilla, by 53 different users, as per https://rt.wikimedia.org/Ticket/Display.html?id=7824 . (Users can search for tagged tickets via Custom Search: //Tags | match regular expression | .+//) TODO: Investigate if they can be turned into Phabricator "flags" but lowest priority. If not, I could warn users via email that their Tags data will get lost and that they should save buglist.cgi or such.
* CC List: Keep/Convert
* Web browser: convert the available entries into projects with the prefix "browser support"
* Mobile Platform: To be dropped, basically unused - see https://bugzilla.wikimedia.org/show_bug.cgi?id=41197#c5
* Reporter: Keep/Convert
* Depends on / Blocks: Keep/Convert
* Alias: T240 - To be dropped; not setting up 100 redirects for using a bug alias instead of the ID as a URL parameter
* Attachment (with potential access restrictions): Keep/Convert
* Comment (with potential access restrictions): Keep/Convert
* Votes: To be dropped. Cannot easily convert to tokens as Bugzilla is missing API support for this, see T88 - might convert after Day 1 from the database instead, if needed? We do not automatically CC voters when migrating. We might enhance Phabricator's Tokens application (see http://fab.wmflabs.org/token/leaders/ and http://fab.wmflabs.org/token ) to provide better search (e.g. exclude closed tasks) at some point but that's low priority. Related discussions: T264, T88. User can find a list of their votes [[ https://bugzilla.wikimedia.org/page.cgi?id=voting/user.html | here]].
priorties per T268:
| **Bugzilla** | **Phabricator** |
| Unprioritized | Needs Triage |
| Immediate | Unbreak Now! |
| Highest | Unbreak Now! |
| High | High |
| Normal | Medium |
| Low | Low |
| Lowest | Needs Volunteer |