My question is, if it is possible to have users or usergroups being assigned to a project, but with different visibility rights. So not all users can see different project releases or subprojects.
Release/Subproject: Test_1 visible by users a,b,c
Test_2 visible by users a,c,d
Test_3….. visible by users a, x, y, z...
There's some trickery you might be able to use, but it deoends on how you're defining these areas.
Generally, a project's access is defined by it's permission scheme. It doesn't go lower than that in any way - if you've got browse/resolve/edit/create/logwork/etc permission in the project, you have it across the entire project.
There IS something called "issue security" which can then hide individual issues within a project. You could use that, but it works off a specific field (security level) which you set to a single level. Each level can have a different access group.
Depending on how you want to split the access, you could find/write a plugin or script that can read your "release" field(s) and set the security level appropriately. But it could be tricky.
Also, before running off down that route, I'd have a broader look at the permissions scheme - you CAN use things like "content of custom field X" to determine some permissions, and that might work for you. But again, it does depend on your config and what the release field does.
yes it means that if I create 1 project and keep having "independent" versions with different names in it, each of the versions is only visible to a certain user group or users. For exmaple, if I was doing Agile that the sprints have different names and only several users are able to see some of the sprints.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot