If field_group is enabled on a site, we can do a much better job with the UI on project node forms, since we can group all the release-specific crap into one fieldset, and all the issue-specific crap into another.

Comments

dww’s picture

Status: Active » Needs review
StatusFileSize
new6.75 KB
new2.01 KB
new1.96 KB

Here are patches for project_issue, project_release and drupalorg_project. Since each one of these is responsible for injecting these fields into the project node type(s), I figured they should also be responsible for providing the default field_group definitions. The drupalorg one isn't tested yet, but I think it'll work.

Status: Needs review » Needs work

The last submitted patch, 1821390-1.drupalorg.patch, failed testing.

dww’s picture

Status: Needs work » Needs review
StatusFileSize
new1.61 KB
new1.94 KB

I committed and pushed the issue and release ones, since they seemed to be working fine.

The drupalorg one had some simple bugs, so I committed and pushed fixes for that, too.

Meanwhile, here are new patches for project and drupalorg_project to create a "Resources" vtab for all those wonky fields we're manually migrating from D6.

Status: Needs review » Needs work

The last submitted patch, 1821390-3.drupalorg_project-project_resources.patch, failed testing.

dww’s picture

Status: Needs work » Fixed

I've committed and pushed everything in here, along with another commit to add a 'Project classification' fieldset for all the d.o-specific taxonomy fields on project nodes. I think we're pretty set in here, so I'm going to call this fixed. New UI fixes should happen in new issues at this point.

Automatically closed -- issue fixed for 2 weeks with no activity.