Different external partners within a project should only be able to see and edit their issues.

[Roger Kessler]

We have different development projects in our company (A,B,C...). We also cooperate with various external partners (1,2,3..).

I would like to unlock the partners for individual projects.
In these projects they should be able to edit the issues marked for them and create new ones.
A project can have different partners at the same time, but they should not see (at least some) issues of the partners.
The structure should be like this:

	Internal	Exteranl Partner 1	Exteranl Partner 2
Project A	create /edit	create / view and edit selected*	create / view and edit selected*
Project B	create /edit		create / view and edit selected*
Project C	create /edit	create / view and edit selected*

Until now I did this with "external share". But this is very difficult for the external partners to keep the overview, because there are only limited possibilities to filter.

I have also read the answer here:
https://community.atlassian.com/t5/Jira-Software-questions/Can-I-apply-the-permission-to-one-specific-issue-using-Issue/qaq-p/1751883
But here only access to one or more specific issues is granted. The external partners should be involved in the project so far that they can create issues themselves. But it may well be that I have not fully understood the answer or the possibilities. 

For a short clarification I would be very grateful, best regards.

[Walter Buggenhout · Accepted solution]

Hi @Roger Kessler and welcome to the Community!

The thread you refer to is a pretty good one in terms of context and approach. Project permissions in Jira are pretty granular. Create issues is a different permission than browse project (view the project) and edit issues.

If you add a custom field to add users to issues (additional to your internal users), that also makes the project visible to users even if they are not added to any issues yet. Granting them the create issues permission should let them add new issues. You can even add the reporter to the browse project permission, so people automatically are able to see their own issues, which probably makes sense.

Preferably, use a group custom field to add all your partner's employees to an issue at once, rather than with a user picker field (where you would have to select every single user separately).

Hope this helps!

[Roger Kessler]

Hello @Walter Buggenhout 

Many thanks for the super fast reply!
I will try this in the sandbox.

Best regards

[Roger Kessler]

A "Permissions Scheme" created and successfully tested, thank you very much.