How to associate a Team to a Work Management project

[Serge Calderara]

Dear all,

I have created a sample Work management project with Team managed option

Then I have created a Team name DEV-TEAM in my instance where I have USer1 and User2

I understood that Team managed project are manage by a uniaue team member of that project

Q : How can I add my team DEV-TEAM to be the only members which gets access a my Work Management project ?

- Do I need to add indiviually each user ? ( which will be stupid)

- Can I associate directly my TEAM named DEV-TEAV in a project role somehow ?

Thanks for clarification

Regards

[Trudy Claspill · Accepted solution]

Hello @Serge Calderara 

Currently it is not possible to use Teams to allocate access to a project. You need to allocate access to the project by individuals or by User Groups.

For more information on access for Team Managed projects refer to

https://support.atlassian.com/jira-software-cloud/docs/add-people-to-team-managed-projects/

And for details on the permissions allocated to Roles refer to

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/

[Serge Calderara]

hello @Trudy Claspill Thanks for your info.

So once again then if it is define as you describe, the Atlassian logic is again wierd.

If it is mentionned that for team based project you can handle isolated project as a Team, I was clearly expected that :

1. You create a Team from the Team menu
2. Then you add members to that team
3. Then you give Access of that created Team to the Team project base without the need to create an other group

So actually team is nothing else that grouping people at the platorm level and simply be able to have view of the team activity

Question :

In some documentation I have read that anyone in a team based project can administer the project . I can confirm that when you check the Access menu.

What is the proper Project access setting in order that only pepole with Administrator role can configure the project ?

Initially what it is said from atlassian documentation is that a team-based project is fully isolated from other project, this could be true if shema behind the scene are only for that project BUT it is not really so isolated becausause based on the Access Project Acess option the "Open" selection makes all users accessing to that team project even you did not give them any role in it

regards

[Trudy Claspill]

Hello @Serge Calderara 

Generally the ability to administer a project is based on the Project Role assigned to the user within that specific project.

Whether you are on a Free subscription or a paid subscription is also a factor.

In the Free subscription it is not possible to assign specific project roles to specific users and it is not possible to change the overall Project Access setting for a Team Managed project.

Based on your screen image showing that you can set the Project Access option for the project, you must be using a paid subscription.

More detailed information about the Team Managed Project Access setting definitions and the permissions allocated to the default roles can be found here:

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/

On the topic of a Team Managed project being "fully isolated" from other projects, please provide a link to the documentation you are referencing. Without that context I can't definitively provide an explanation for what they meant by that. However do note that Team Managed projects are not truly completely isolated when it comes to the customizations. Team Managed projects can't use the Schemes (i.e. Screen Schemes, Field Configuration Schemes, Workflow Schemes, etc.) that are used by Company Managed projects, but they can access the Custom Fields created for Company Managed projects if those fields have a Global Context. And while custom fields created directly in a Team Managed project can't be used in other projects, those custom field names are visible when a user it trying to construct an issue filter.

What is the proper Project access setting in order that only pepole with Administrator role can configure the project ?

The ability to configure the project is based on the Role assigned to the user within that project, not the Project Access setting. Only the users with the Administrator role in that project (and also users with the global permission to Administer Jira permission) will be able to configure the customizations for the Team Managed project.

Project Access determines who can see the project, and some default settings for what they can do in the project.

When it comes to the ability to see a project and the issues in it, Team Managed project can have that access restricted through use of the Project Access setting. You would "isolate" the project to be visible and accessible to only the people you add to it by setting the Project Access to Limited.