Issue visibility permissions for different departments.
I created two departments as two projects: Department A and B. The employees for each department were created: A1, A2...A5 and B1, B2...B5. Every employee has full access to issues (create new ones, edit them, comment on them, etc.), but only within their own department.
I would like to configure our work like this:
- Employee A1 creates an issue iA1, which is only visible to all employees in department A.
- Employee B2 creates an issue iB1, which is only visible to department B.
- !For example, employee A1 from department A creates an issue iA2, which is ONLY visible to himself and to B1 and B5.
How can I configure the permissions like this?
Thank you!
Please sign in to leave a comment.
Hi Ilya!
This will be achieved if project A employees have roles (containing permissions) only in project A. The same would go for project B employees who would have roles in project B only.
In this case, the role configuration should be a bit different. If specific issues need to be shared with external users, you should grant a role that contains the Read Issue permission to this external group of users as well. This way, all issues with default visibility (visible to issue readers) will be readable by both the internal and the external groups.
In all issues that you want to keep private, however, you'll need to have an issue-level visibility set to the project team or a specific group. This can be achieved via the pre-selected visibility setting in new issues using the Default visibility setting on the general project configuration page or using custom workflows for visibility assignment automation.
You might find these articles helpful:
Hi Stanislav, thank you!