Hi, can you please add in the permissions field a permission e.g. "Storm project: view only if assigned teammember" (for Storm task/ticket/teammember as well) and/or a multiple selectbox in the project/task/ticket creation where you can assign peoples/organizations/all directly...? E.g. when you are only assigned for a task in a project, you can only see your assigned tasks/own created tasks and the project itself, but not the other tasks of your project, only if you have created the project by yourself? This would be a great and needed feature! Thanks!

Comments

Roberto Gerola’s picture

Roberto Gerola commented

Hi.
Teammeber feature is yet under development and not yet finished feature.
When finished it will be integrated with control access system.

Roberto

peterx’s picture

peterx commented

Is there a roadmap for team members and person? I am ready to open ticket creation to users and want to use Drupal roles to limit what each person can see and change. Some people belong to organizations and should be able to see everything for that organisation plus attach tasks to tasks and projects plus create tickets.

Some staff and all contractors can be attached to projects or tasks in any organization and should see only the projects or tasks they are attached to, plus any child tasks. I think this is where team member comes in. Is that the intention for team members?

Magnity’s picture

Magnity commented
Component: User interface » Code
Priority: Critical » Normal
Magnity’s picture

Magnity commented
Title: project(/task/ticket) view(/add/edit/delete) through teammembers module or direct assign people » Team members permissions
Component: Code » Storm Teammember
Magnity’s picture

Magnity commented
Status: Active » Closed (duplicate)

Although this one is older, i'd like to combine this issue into #380008: Development of Storm Teammember, where the current discussion about Storm Teammember is going on.

Permissions are one of a range of options being looked at.