Component admin panel does not include project column

[Jeffrey.Ratcliffe@…]

Having upgraded from smp 0.0.4 to 0.5.1, I was expecting the legacy component admin panel to disappear.

However, additionally, I was expecting to see a "project" column in the standard component admin panel. This is missing, and setting

[simple-multi-project]
legacy_component_panel = True

does not reenable the legacy panel.

The project panel is still there, and the logs show that the plug-in is loaded

[Jeffrey.Ratcliffe@…]

The other smp functionality is still there, e.g. from the roadmap, editing a milestone allows the user to select a project.

The problem seems to be only with the admin panels.

Perhaps this is linked to #12910

[anonymous]

is the module switched on, can you have look at the plugin page of the Admin panel?

[Jeffrey.Ratcliffe@…]

Yup. That was it. I had

simplemultiproject.admin.smpadminpanel = enabled
simplemultiproject.admin_component.smpcomponentadminpanel = enabled
simplemultiproject.environmentsetup.smpenvironmentsetupparticipant = enabled
simplemultiproject.milestone.smpmilestoneproject = enabled
simplemultiproject.model.smpmodel = enabled
simplemultiproject.roadmap.smproadmapproject = enabled
simplemultiproject.roadmap.smproadmapprojectfilter = enabled
simplemultiproject.ticket.projectticketspolicy = enabled
simplemultiproject.ticket.smpticketproject = enabled
simplemultiproject.timeline.smptimelineprojectfilter = enabled
simplemultiproject.version.smpversionproject = enabled

instead of

simplemultiproject.* = enabled

I am nonetheless surprised that the legacy panel remained hidden.

[Jeffrey.Ratcliffe@…]

It would be useful if the documentation explained what the subplug-ins were available, and which were responsible for which functionality.

[anonymous]

Replying to Jeffrey.Ratcliffe@…:

It would be useful if the documentation explained what the subplug-ins were available, and which were responsible for which functionality.

Have a look at the plugin admin page. There is some information available for each plugin there.

[Ryan J Ollos]

This should be fixed on the latest trunk.