nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

can you create project roles specific to a project?

Chag

can you create project roles for a specific project? for example, if i want to create a IT project I want it to have only IT related roles(helpdesk , SA or DBA) in this project only can that be done? I dont want those roles to show up in other projects. I could not find anywhere how to do this maybe they need to add a scheme for this?

Accepted answers

Nic Brough -Adaptavist-

No, the whole point of a role is that it goes across all projects. It gets unnecessarily complex if you start trying to limit them to sets of projects.

If you don't want to use a role in a project, don't put anyone in it. Just educate your project owners as to which are useful (assuming you've got differing permission/notification/workflow schemes)

All comments

Joe Pitt

No, but you don't need to put anyone in them.

Nic Brough -Adaptavist-

No, the whole point of a role is that it goes across all projects. It gets unnecessarily complex if you start trying to limit them to sets of projects.

If you don't want to use a role in a project, don't put anyone in it. Just educate your project owners as to which are useful (assuming you've got differing permission/notification/workflow schemes)

Chag

thank you that makes sense.

Joe Pitt

The day to day problem with using groups is only JIRA admins can manage group membership, whereas the project lead can manage users assigned to roles in their project. If your staff membership and responsibility doesn't change much this may not be an issue with you. In larger organizations people are swapped in and out of projects or the staff and having to funnel everything through the JIRA admin is a pain.

Jose M_

But it works

Jose M_

Roles are used in workflows or permission schemes. Instead of a role you can use a transition, whose condition should be a specific (project) group.

Rob Horan

I wholeheartedly disagree that the point of a role is to go across all projects. The point of a role is to provide project admins the ability to delegate permissions to project functions without having to go to a system admin to make changes.

There may be roles that are only applicable to a single project. I am facing this problem right now with an enterprise-class client. I have asked for two new roles to be created and the admin team is pushing back as they would be included in EVERY project on that instance, for which there are many.

The project admins MUST have the ability to add/remove team members on their own as people come and go on a rolling basis. The ONLY way to do this is to use roles, and this is clearly an invasive option if there is no way to hide roles from projects that do not use them.

Shooting down very reasonable functionality needs by saying 'the whole point of' anything is extremely limiting, and goes against the fundamental flexibility that Atlassian has promised would come with Jira.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration