How do I confine trainee accounts in JIRA 4.4 to one project with standard developer permissions and avoid global groups, given current login issues with group inclusion?
In my experience, the best approach was to fully leverage custom permission schemes designed specifically for trainee roles. I set up a dedicated trainee role confined to the single project, ensuring that their access rights were strictly limited to that area. Instead of relying on global groups, the solution involved tailoring the permission schemes to bypass global settings and tightly control what trainees could do. This method may require additional configuration, but it effectively separates trainee capabilities from other developer permissions and mitigates broader access issues.
In my experience, limiting trainee accounts to a single project can be efficiently managed by employing custom permission schemes localized to that project. Instead of relying on global groups, I established a distinct trainee role that only has access permissions for one project. This involved configuring the project’s permission scheme to recognize and restrict access based solely on the role assigned at that level. Although it required a detailed setup process, the approach minimizes unintended exposures and simplifies administration by isolating trainee activities. The extra effort in customization ultimately leads to a more secure and streamlined environment.
i’ve tried a similar fix by making a unique trainee role and then linking it to a project-only permission scheme. it separated their access cleanly without mixing into global groups, which fixed login issues for us. sometimes a small customized tweak goes a long way.