If issues are moving away from www.drupal.org, then we have to remove or replace all the places where issues are integrated. For example:
- The text filter replacing
[#3265096 ]with #3265096: Move issues from www.drupal.org to git.drupalcode.org - Entity references to issues, such as on:
- Change records
- Organizations
- Issue parent/child/related relations
We'll also need to provide a way to grant issue credit.
Comments
Comment #2
drummComment #3
fjgarlin commentedIssue content type (/admin/structure/types/manage/project-issue/fields/) #3292161: Decouple issues from www.drupal.org issues (parent and related)
Change record content type (/admin/structure/types/manage/changenotice/fields) #3265112: Decouple change records from www.drupal.org issues
Organization content type (/admin/structure/types/manage/organization/fields) #3292162: Decouple organizations from www.drupal.org issues
Modules
I'll create the child issues but wanted to give an overview of the findings here.
Comment #4
fjgarlin commentedUseful information:
field_data_field_issues => 6309 rows (change record)field_data_field_org_services_issue => 2269 rowsfield_data_field_org_train_issue => 244 rowsComment #5
crasx commentedCommented on the wrong issue, ignore!
Comment #6
fjgarlin commentedComment #7
fjgarlin commentedComment #8
fjgarlin commentedDeployment instructions added to all relevant child and related.
The suggested order is:
After the above is deployed, then all places on www.drupal.org where internal issues were entity references will now be links, thus allowing for both internal and external links in preparation for the GitLab migration.
Comment #9
drummWith #3292161: Decouple issues from www.drupal.org issues (parent and related) fixed, this is done!