Use Cases:
1. An Organization type Vendor has different set of fields and permission than that of Client. People who interact with Vendor are different and Client are different.
2. There can be different types of Task with different set of fields according to type. For example a meeting can be a task which requires different set of fields as against a task that needed to be executed in a Project. A code sprint be another type of task.
For the above use cases, what an organization using PM would do is try to bang in every field into one mega Entity and set up complex system of permissions and display. Which would complicate the overall development of PM system.
Proposed feature request that would solve this.
1. Instead of depending upon single entity type ( default provided by PM ), user can create a more than one content type and register it in PM. We can restrict entity to "nodes" only if required.
2. Just implement a a bundle_copy hook in modules supporting these feature so people could clone the node_type and use it to create their flavour of PmType.
Just FYI: bundle copy is not a dependency, it would be just for the user's convenience. And its going to be in D8 core anyways.
A feature like this couldn't be implemented in a contrib module ever. So that's why i am asking this in here.
Closed: outdated
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
All feature request against 7.x would be closed. The focus is now on Drupal 10 release. If you feel this issue is relevant for Drupal 10 version of the project, please feel free to re-open and update the issue. Thanks for the discussion/contribution.
You may follow 📌 Port PM to Drupal 10 Active to know more about Drupal 10 status.