I did a google search and found the Tempo Team plugin gives you team roles. That isn't part of the base product. To work in JIRA you need to stop thinking about 'hiding' things. There is no way to hid in JIRA. You chose to allow access. Thinking that way will make it easier to figure out how to do what you want.
You'll need to remove the users from any roles in the project, or groups in the system that give them "browse" permission (check the permission scheme to see what that says)
By default, JIRA tends to put the "can log in" group into projects, so you will probably find you have to go through your projects and remove the group "jira-users" from the roles, replacing it with the individuals or groups who should retain access. I'd also recommend removing it from the default roles, so new projects don't inherit it automatically.
Prasad, you can do it by roles or by groups. Its done via Permission Schemes - simply deny the "Browse" permission to the group or role you wish to exclude.
We were not able to classify simply by role in our company, because of the sheer magnitude of people in the User role - who needed to be further classified for the project's permission scheme. So we created user groups - Default permission scheme was modified and it denied permission to everyone except a core group.
Individual project permission schemes were created - they allow permissions to specific groups of users who were given individual permissions within a project. We also have clients accessing our JIRA instance, with a greater need for customisation of permission schemes. For e.g. Client users may Browse and comment issues. But the Client approver is a single user who may edit issues, transition issues and link issues as well... etc.
Got to admin -> issues -> permission schemes
Bear in mind if you do this with groups, you'll need to keep creating more schemes every time a project is created. Roles are a far better approach, because you can use a small handful of well understood schemes, and easily change the users and groups in use in a project. Roles can do everything groups can, and more and the groups in permission schemes are a nightmare to maintain, especially in larger systems.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs