Another setting on the 'Issues' subtab when editing projects that we haven't ported to D7 yet is #423304: Add a per-project default component setting to simplify the UI when submitting issues
mysql> SELECT COUNT(nid) FROM project_issue_projects WHERE default_component != '';
+------------+
| COUNT(nid) |
+------------+
| 391 |
+------------+
1 row in set (0.04 sec)
Not heavily used, but probably worth fixing.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | project_issue_default_component_v2.patch | 8.29 KB | jthorson |
| #3 | drupalorg_default_component.patch | 559 bytes | jthorson |
| #2 | project_issue_default_component.patch | 5.82 KB | jthorson |
| #2 | drupalorg_default_component.patch | 559 bytes | jthorson |
Comments
Comment #1
jthorson commentedComment #2
jthorson commentedThe following patches create a 'field_project_default_component' field on project pages, which is used during hook_field_widget_form_alter() to set the default component as the #default_value on the project_issues form if one does not already exist.
Because a number of the drupal.org 'Project' node types are actually generated within drupalorg_project, we also need to patch the fieldgroup definitions in that project to ensure the new field is displayed in the correct location.
This has been tested and is mostly working, except that it is not tied into the ajax routines which execute when changing the value of the 'project' field in the 'create issue' form ... which is probably minor enough that it isn't required for the drupal.org D7 launch. Opened #2073509: Per-project default component does not persist when changing project in 'create issue' form as a followup.
Also, these patches don't take care of the upgrade path for existing projects which have a 'default component' set in the existing drupal.org site. Opened #2073511: Upgrade path needed to migrate projects with a 'default component' set. as the followup for the data migration, and tagged it for the Drupal.org D7 migration.
Comment #3
jthorson commentedUpdated patch, now containing the migration path. Drupalorg patch hasn't changed, just re-uploading for consistency.
Comment #4
drummCommitted & deployed on git7. I think this update should be okay to run before the migrate-managed migrations happen, so leaving it as-is.