Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Setup several projects all visible within our department and define access to different customers

Paul Efford March 31, 2022

Hi Community,

I am to set up Jira in my department and having troubles because of the permissions the departments have. May you advise me, what the best configuration for my use case would be? (I will be talking here about projects but it might be found out, that should later be boards or whatever else)

- My company has a Jira admin, who grants permissions to users and typically creates projects for them

- I am employed in a department and been tasked to set up our projects
- I do not have (and will not be granted) an admin account

- My department is a software department so projects are mainly related to software and or to proposals of implementations (so not code in the first stage but a lot of docs, in case this may be useful to get the big picture)

- In our department, we want to have different projects (15-50), ones related to the other ones but each **must** have its own Backlog

- The scheme of the projects should all be the same: if changing something in the scheme, all projects should actualize

- We will all be allowed to work on all projects within the department with no restrictions

- external customers must be **only** able to see the projects, for which they have been granted access to

- Each user wants to have just **one** screen an view his own related issues, don't matter if belonging to different projects (not a flat Kanban but issues being classified by Project > Epic > Sprint)


May you have a hint for this?
Thanks in advance,
Paul

1 answer

0 votes
Piotr Zadrożny _Eyzee_
Community Champion
April 1, 2022

Hi @Paul Efford 

Your Jira admin should prepare project configuration for you, based on your requirements. You just don't have sufficient permissions to do so.

I cannot suggest you proper configuration regarding workflow, fields, screens because you provide too little details on that matter. All of those configuration (also with permission and notification schemes) should be prepared as templates to be used by all of your deparment projects (shared configuration). On all of created projects you need boards (Kanban/Scrum) displaying issues from that particular project.

To meet your permission requirements on Permission Scheme your Jira Admin should grant Browse Project permission (along with other permissions your team need like Edit, Create, Transition Issues) to group to which all your department employees belongs to. Futher more Browse Project permission (along with other permission required by External users) shoud be granted to Project Role (for example "Clients" or "External") and on specific project its Preject admin will be able to add external user to that role to grant access,

Regarding this "single view" for your team I believe that filter or prepared dashboard with configured gadgets shared with all your team members (group) will be most suitable.

Best regards,

Piotr

Suggest an answer

Log in or Sign up to answer