Wikimedia recently migrated from using Bugzilla for issue report tracking to the Maniphest tool that is included in Phabricator: https://www.mediawiki.org/wiki/Phabricator . This also requires updating lots of information on the Wikimedia wiki pages. https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle includes the diagram https://www.mediawiki.org/wiki/File:Bug_Life_Cycle_Diagram.png with its SVG version at https://www.mediawiki.org/wiki/File:Bug_Life_Cycle_Diagram.svg .

You will have to understand the status of a bug report that Bugzilla had (described in the old version of the page in https://www.mediawiki.org/w/index.php?title=Bug_management/Bug_report_life_cycle&oldid=1060865 ) and their corresponding status in Phabricator/Maniphest covered in the table at https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated . You will also need to find out which status can be changed to which other statuses of a ticket. You can find out by creating a test ticket in the Phabricator test instance at https://phab-01.wmflabs.org/ and changing its status. You will have update the diagram (or create a new one) to reflect how things work in Phabricator. Also mention that "Patch-For-Review" is not a status anymore but is now a project in Phabricator until Wikimedia has also migrated its Code Review infrastructure from Gerrit to Phabricator).

This task requires existing skills in using an application to create and edit SVG files. You will have to attach a draft to the task in Google Melange and once the draft looks good, you will have to upload/overwrite the PNG file and the SVG file on mediawiki.org with your updated version.

Students are required to read Wikimedia's general GCI instructions at https://www.mediawiki.org/wiki/Google_Code-in_2014#Instructions_for_GCI_students first!