I love your videos. I've always been in a position to have someone else handle JIRA administration for me. Your series of videos on creating roles, permission schemes and applying them were outstanding and the best explanations I've heard. I'm going to keep your fivver profile should I need any specialized support!!
Thank you for sharing this, Alex. This is really helpful. After following your tutorials I did manage to assign the permissions and create the roles which I need. However, would it be possible to add a group of admins who have access to system admin for their own projects only? That's to say I am wondering if I can have project admins who can edit the screens, custom fields and etc for their project only?
In a company managed project, this isn't possible. But, in a team managed project it is. . . . but I don't recommend you do that. You should limit the number of people that can make these types of changes because otherwise, you are going to end up with an unmanageable Jira. . . but just my 2 cents.
Hi there! Thanks for the series. I got an overview. But has the UI got changed recently? Because I can't find 'Permissions' tab in the 'Project Settings' section.
Hi Alex, Thanks for the videos, i am settingup JSM in as new project and there are already software projects but I am unable to receive issues from email request its say you "dont have required access to this project " Is other projects setting effecting JSM please help
What is the point of creating roles if I can create groups, assign people to those groups and then in permission scheme grant permissions to certain activities e.g., Manage Sprints Grant to GroupA. Your proposal justt makes the whole process complicated. You suggest: creating groups-> assigning users to groups-> assigning roles to groups-> granting permissions to roles, while skipping 'assinging roles to groups' step makes it easier: create groups->assign users to groups->grant permissions to groups
Hi. I really appreciate your videos. I think you are a very good teacher. I do have a problem. When I copy the Default Software scheme, and then remove "all logged in user" on browse projects, and then add administrator, I stop seeing the project. I don't know why that is. Can you please help?
I´ve a question, why not to use the same permissions scheme to all projects if we user the same settings in regards to who can admin, delete view and read??
Thank you so much for your explicit content. Please guide me on how to perform these actions on Free software as "Add People" is not visible and I am getting this notification: "On a free plan, you can only add people using your site's administration settings. Upgrade your plan to better control who can access this project."
That’s the limitation of the Free plan. You’ll have to bump yourself up a level if you want to manage your users and groups. But with less than 10 people. . . Do you really need to manage access?
@@ApetechTechTutorials Hi there! you are right with limited team members, there is no dire need of access management, I was just curious whether there is a way-around for this. Thank you for your clarification.
I find it VERY interesting that you recommend groups for managing project roles. It seems to me to go completely against what project roles are actually designed to do. For one thing, project roles can be are controlled by the project admin. Therefore, you give the project admin some power, so to speak, to control access to their project. At the same time you save administrative effort, because you can delegate the exact management of project permissions to the project admin. However, group membership can only be controlled by the org/site admin. On the other hand you can use ONE permission scheme to control project permissions for many projects via project roles. I.e. in the specific case you describe, you would ruin the advantages of managing project permissions that the project admin controls via project roles. Because now the project admin would have to contact the org/site admin every time someone leaves the project, for example. The org/site admin would then have to remove that person from the group. So it would be MORE administrative effort in total (2 people involved). Actually, in this case you would not need project roles at all, because you could enter the groups directly in the permission scheme. As I said, I find your approach interesting and would like to discuss it. No offense and thanks for the contribution :)
I see your point. . . in a small organization, that would work perfectly fine. But, when you have a large organization, the user needs to be onboarded and granted a Jira license. Only the SITE admin can do this, so why not add users to a group while they are there? Additionally, the project admin still has the ability to add users manually using the People section, but my solution is for a scalable model. One that requires a user to be placed into a group once and then inherit all the permissions they need. Your way of doing it requires the project admin to do a lot of manual work. The projects/teams I work with typically have somewhere around 50-150 projects. . . that's a lot of manual labor that could be resolved by placing folks in the right group with the right role which by the way can be managed/controlled by the project admin. Many ways to skin a cat, I just recommended based on the pain points my clients go through. . . everyone will be different.
Do you have any videos on how to lock down Jira so that external customers can only see their one project that they are assigned to as opposed to seeing every project when they browse for a project?
I would LOVE a tutorial like this. We have an external vendor that needs to create tickets for QA in one project. I do not want them having access to other projects, but it is more than read-only. Would love help with this!
To get more resources and get in contact with me check out this link linktr.ee/apetech
I love your videos. I've always been in a position to have someone else handle JIRA administration for me. Your series of videos on creating roles, permission schemes and applying them were outstanding and the best explanations I've heard. I'm going to keep your fivver profile should I need any specialized support!!
Thank you for sharing this, Alex. This is really helpful. After following your tutorials I did manage to assign the permissions and create the roles which I need. However, would it be possible to add a group of admins who have access to system admin for their own projects only? That's to say I am wondering if I can have project admins who can edit the screens, custom fields and etc for their project only?
In a company managed project, this isn't possible. But, in a team managed project it is. . . . but I don't recommend you do that. You should limit the number of people that can make these types of changes because otherwise, you are going to end up with an unmanageable Jira. . . but just my 2 cents.
Hi there! Thanks for the series. I got an overview.
But has the UI got changed recently? Because I can't find 'Permissions' tab in the 'Project Settings' section.
I don't think this part of the UI has changed. Maybe you aren't in a company-managed Jira Software project?
Hi Alex, Thanks for the videos, i am settingup JSM in as new project and there are already software projects but I am unable to receive issues from email request its say you "dont have required access to this project " Is other projects setting effecting JSM please help
What is the point of creating roles if I can create groups, assign people to those groups and then in permission scheme grant permissions to certain activities e.g., Manage Sprints Grant to GroupA.
Your proposal justt makes the whole process complicated. You suggest: creating groups-> assigning users to groups-> assigning roles to groups-> granting permissions to roles, while skipping 'assinging roles to groups' step makes it easier: create groups->assign users to groups->grant permissions to groups
Hi. I really appreciate your videos. I think you are a very good teacher. I do have a problem. When I copy the Default Software scheme, and then remove "all logged in user" on browse projects, and then add administrator, I stop seeing the project. I don't know why that is. Can you please help?
I´ve a question, why not to use the same permissions scheme to all projects if we user the same settings in regards to who can admin, delete view and read??
Thank you so much for your explicit content. Please guide me on how to perform these actions on Free software as "Add People" is not visible and I am getting this notification:
"On a free plan, you can only add people using your site's administration settings. Upgrade your plan to better control who can access this project."
That’s the limitation of the Free plan. You’ll have to bump yourself up a level if you want to manage your users and groups. But with less than 10 people. . . Do you really need to manage access?
@@ApetechTechTutorials Hi there! you are right with limited team members, there is no dire need of access management, I was just curious whether there is a way-around for this. Thank you for your clarification.
I find it VERY interesting that you recommend groups for managing project roles. It seems to me to go completely against what project roles are actually designed to do. For one thing, project roles can be are controlled by the project admin. Therefore, you give the project admin some power, so to speak, to control access to their project. At the same time you save administrative effort, because you can delegate the exact management of project permissions to the project admin.
However, group membership can only be controlled by the org/site admin.
On the other hand you can use ONE permission scheme to control project permissions for many projects via project roles.
I.e. in the specific case you describe, you would ruin the advantages of managing project permissions that the project admin controls via project roles. Because now the project admin would have to contact the org/site admin every time someone leaves the project, for example. The org/site admin would then have to remove that person from the group. So it would be MORE administrative effort in total (2 people involved). Actually, in this case you would not need project roles at all, because you could enter the groups directly in the permission scheme.
As I said, I find your approach interesting and would like to discuss it. No offense and thanks for the contribution :)
I see your point. . . in a small organization, that would work perfectly fine. But, when you have a large organization, the user needs to be onboarded and granted a Jira license. Only the SITE admin can do this, so why not add users to a group while they are there? Additionally, the project admin still has the ability to add users manually using the People section, but my solution is for a scalable model. One that requires a user to be placed into a group once and then inherit all the permissions they need. Your way of doing it requires the project admin to do a lot of manual work. The projects/teams I work with typically have somewhere around 50-150 projects. . . that's a lot of manual labor that could be resolved by placing folks in the right group with the right role which by the way can be managed/controlled by the project admin. Many ways to skin a cat, I just recommended based on the pain points my clients go through. . . everyone will be different.
Do you have any videos on how to lock down Jira so that external customers can only see their one project that they are assigned to as opposed to seeing every project when they browse for a project?
Not really, but this video probably comes close to what you'll need. th-cam.com/video/KqK4DA0CZQM/w-d-xo.html
I would LOVE a tutorial like this. We have an external vendor that needs to create tickets for QA in one project. I do not want them having access to other projects, but it is more than read-only. Would love help with this!
Is there a way to restrict users from seeing Reports tab in Jira Cloud? Thanks!
Thanks, Could you please give group permission vedio
How do I lock a project on my project drop down list from being viewed ? If i am working on two different projects for different companies.
I literally just want to add my external team to see only one board in our company and it’s so complicated 😢 why jira whyyyyy
Did you find a soulution for this ?
I'm going trough the same issue. And you can always ask for atlassian community support .