Belonging to more than one organization

> let admin to choose multiple belonging organizations
Multiple organizations per person ? Not sure it is appropriate.

Can you present some examples ?

Thanks, Roberto

Thanks for your clarification, but this will be superseded by the team member feature I am working on.

In few words it will be possible to create several teams, every team associated with an organization/project/task/ticket :

  $schema['stormteammember'] = array(
    'fields'                => array(
      'tid'                       => array('type' => 'int', 'not null' => TRUE, 'default' => 0),
      'organization_nid'          => array('type' => 'int'),
      'organization_title'        => array('type' => 'varchar', 'length' => 128),
      'project_nid'               => array('type' => 'int'),
      'project_title'             => array('type' => 'varchar', 'length' => 128),
      'task_nid'                  => array('type' => 'int'),
      'task_stepno'               => array('type' => 'varchar', 'length' => 128),
      'task_title'                => array('type' => 'varchar', 'length' => 128),
      'ticket_nid'                => array('type' => 'int'),
      'ticket_title'              => array('type' => 'varchar', 'length' => 128),
      'person_organization_nid'   => array('type' => 'int'),
      'person_organization_title' => array('type' => 'varchar', 'length' => 128),
      'person_nid'                => array('type' => 'int'),
      'person_title'              => array('type' => 'varchar', 'length' => 128),
      'role'                      => array('type' => 'varchar', 'length' => 50),
    ),
    'primary key' => array('tid'),
  );

Hi, Roberto.

Your module is great help for small companies doing web development for their clients.

This feature "one person per multiple organizations" would be a great feature - and probably your "teams" extension will do something similar. I would like to ask about this teams feature and is there anything I can do to make it happen quicker? I mean if this feature reached some sort of testing stage or is still in development - probably you could organize a separate thread and put up the code - so other people can help you building it?

Here's the description of our quite common workflow where multiple organizations are required per person:
- Our client has two organizations
- The client doesn't want to have multiple logins to manage both his organizations
- We do multiple projects for the client for both his organizations
- The client needs to create and see tickets for both his organizations
- The client needs permissions to manage people, projects, tasks and tickets across two organizations.

The issue is that we cannot assign the same storm person to multiple organizations, and even if we could - that person wouldn't be able to see projects, tasks, tickets belonging to more than one organizations.

>The issue is that we cannot assign the same storm person to multiple organizations,
>and even if we could - that person wouldn't be able to see projects, tasks, tickets belonging to more than one organizations.

This would break all the logic I have followed until now, it isn't possible to implement.
The same feature will available in the team members component.

>I would like to ask about this teams feature and is there anything I can do to make it happen quicker?
I'm looking for some sponsors to help me. Are you available to sponsor this feature entirely or in part ?

Thanks, Roberto

Hi, Roberto.

Currently I can create another Storm Person and select existing user. The trick is that I can create another person with the same name and with the same username but assign it to different organization. After that the user will be able to create projects for both organizations and to create tickets for those projects and see tickets for different organizations. This is trick, but it works.

The issue is that if two people in the same organization create tickets/projects - they won't be able to see other's person tickets unless they both (people) belong to both organization.

Say: Tom belongs to Company 1 and Company 2, while Simon belongs to Company 1.

When Simon creates a ticket - Tom can't see it while if Tom creates a ticket - Simon can see his own and Tom's tickets. The expected behavior is that they both should see each other tickets, as they both belong to Company 1 and the project created for Company 1.

I cannot sponsor development of this feature by monetary support but I can help you build it (which is sponsorship as well). I have experience developing many modules for Drupal for my company's custom Drupal based projects.

Thanks, Ivan.

Was looking in the database and the user object and confirming that assigning one person to two different organization means complete rewrite of many STORM modules.

Will try to implement groups using taxonomy and hook_sql_rewrite() as a separate module.

damn, need this too, but #6 doesn't work for me...

Check out #380008: Development of Storm Teammember - it may be that this could allow cross organisational teams that will fulfill the same function.