At the end of the migration, GH will provide a file that maps the old bpo IDs to the corresponding GH IDs. We should:
[x] edit the issue item schema to add an additional "GitHub id" field
[x] update the field with the GH IDs provided in the file
The GH ID should then be used
[x] at the top of each bpo issue to point to the corresponding GH issue
[x] in a new GH id column in the issue list page
This can be accomplished by editing respectively the issue.item.html template (adding the link at the top, instead of the editing form) and the issue.list.html template (adding a column with the GH ids next to the bpo ids that sends to the GH issue once clicked). This should be implemented as a separate PR to be merged after the migration.
At the end of the migration, GH will provide a file that maps the old bpo IDs to the corresponding GH IDs. We should:
The GH ID should then be used
This can be accomplished by editing respectively the
issue.item.htmltemplate (adding the link at the top, instead of the editing form) and theissue.list.htmltemplate (adding a column with the GH ids next to the bpo ids that sends to the GH issue once clicked). This should be implemented as a separate PR to be merged after the migration.