Fix issue/module relationships

I added an Issue module field to issues and need to move the previous Modules field data into it.

I added the related modules field to Issue and manually cleaned up issues with multiple values.

I used ECA VBO to copy the remaining field values.

  1. Create an ECA model
    1. Create a VBO one by one event and VBO access (see readme).
    2. Use an entity aware trigger to set the value on a single issue.
  2. Create a view listing issues.
  3. Add ECA Bulk Operations field.

 

 

Issues allow one module to be referenced, with a corresponding entity reference to connect them.

Modules can reference multiple issues, and some of those could relate to different modules, or core.

Need to fix relationships to use the module field for the module the issue is for, and add a related modules field and CER for other references.

Modules can also get the related modules field to allow them to reference each other.

Project
Drupal Architect
Tags
Modules
ECA VBO

Comments

Submitted by Admin on Sat, 03/16/2024 - 17:29

Permalink

Added Issue module, Related modules, Related issues fields to Issue.

Issue module references the module the issue is in.
Related modules references other modules that may be impacted by the issue.
Related issues references other issues that may be impacted by the issue.
Corresponding entity reference set up for Issue module - Module issues.
Corresponding entity reference set up for Related issue - Related issue.

Added Module issues, Related issues to Module.

Module issues reference issues for the module.
Related issues reference other issues that may impact the module.
Corresponding entity reference set up for Module issues - Issue module.
Corresponding entity reference set up for Related issues - Related modules.

Submitted by Admin on Sat, 03/16/2024 - 18:13

Permalink

Now some content types have a Modules field, and some use Related modules.

I think there is a module field still there too. Content needs to be migrated.