Hi community,
I need to define default project members / -groups which do only apply for a specific permission scheme. Since default members of project roles are defined globally, I wonder how I can assign these members to a specific permission scheme.
any idea?
Jürgen
Hi @Jürgen Wieser,
In case this is really a specific case that you want to re-apply to a couple of well defined projects, you could consider adding your default groups to the respective permissions in the scheme itself. That would ensure you don't have to re-define them each time you start a new project.
For individual users, I would not do that. That would have a potential major impact on your onboarding / off-boarding process since you need to involve a Jira administrator to apply every change there. Adding individual users goes against any best practice, on a side note.
Since I assume projects like these are always created in a controlled manner, I would make sure that you document the users you may need to add individually when you create a new project (if that still applies). That would normally only require a very limited effort at project creation.
Hope this helps!
Hi Walter,
thanks for the quick response.
I guess I need to explain more in detail the use cases:
Jira is used in the company for several topics, e.g.
- customer projects for developing and assemby of device (and here there are multiple departments working their own projects, where different user groups are defined for the different departments)
- software projects
- QM- projects
- etc.
I have defined project templates with respective schemes (Permission, Notification, Workflows, etc.)
I have also defined global groups for the various project types and departments
Since projects are sensitive with respect to permissions I want to avoid that per default employees will be able to browse projects owned by diffrent departments.
When creating a new customer project, site admin creates a new project based on this specific project template.
Now I want to be able to assign specific user groups to a project role used within that permission scheme.
And I want to assign another user group to that project role when using a different project template which is assigned to another permission scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jürgen Wieser,
Thx for the detailed explanation. That is exactly how I had it in mind as well.
As you have rightfully observed, specifying default members per role is a global setting in Jira, which cannot be adjusted per permission scheme. You probably also noticed that copying a project from a template project does copy the permission scheme, but not users and groups assigned to the roles therein.
If you create projects rather often based on a specific project template, you could add the user groups to the same permissions you have linked to roles directly in the permission scheme itself. If you do so, you no longer have to link groups to roles on a per project basis. You should obviously only do that for those groups you consider to be your default groups. That still leaves room to add ad hoc users and groups on each individual project according to your needs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh yes, I didn't think about this. This works fine.
thanks a lot for this hint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.