On December 18th (Tuesday), Wikihub will be unavailable from 7-9am.

Page tree
Skip to end of metadata
Go to start of metadata

Project Administrator Role

One of the best new features of roles-based JIRA projects is that those people in the Administrator role can assign members to roles within their project.  Administrators can also view other schemes used such as the notification, permission and issue level security schemes. 

Here are the default roles that have been set up for all JIRA projects:

  1. Administrators - anyone in this role can perform any task within your project. They can delete all user comments, edit all issues and change the name of the reporter. A project administrator can also manage project role membership. Because they have such unrestricted access to issues, we recommend that you limit the people who are in the Project Administrator role. However we strongly suggest you have at least two people in this role.
  2. Developers - these are usually the people who do the coding work for your project and depending on your permission scheme, will be able to assign, close or edit issues.
  3. Analysts - these are usually the people who assist with tasks in the project such as QA testing, UI/UX work. Depending on your permission scheme, they often have the same permissions as the developers.
  4. Customers - traditionally customers have a limited role in your JIRA project. They can create issues, upload attachments and comments but they cannot edit issues.

Depending on the permission scheme attached to your project, people in each of these roles will have a different set of permissions. For instance, if your project uses the Standard Permission scheme, people in the Developer role can assign issues. In the Medium Restrictive scheme, they cannot.  In some permission schemes, only Administrators can close an issue; in the less restrictive schemes, other roles can perform this task. Users may play different roles in different projects. For more information on the different permission scheme available, check out the Permissions Scheme Options page.

To Manage Your Project's Roles Membership:

 

  • Click on the COG icon in lower left panel of your Project Summary page        

  • Click on the View Project Roles link under the Roles section
    • you should see a list of the default roles and who is in each role for your project. 


  • jira-users is there be default.  Unless you have a permission scheme to allows for the Role Users to have any access, this has role has no rights to your project.
  • To add, click Add Users to a Role in the top right hand corner.  The following box appears.

 

  • As you start typing, a list of all the possible user names will appear in a pull down list. If the person you want is not in this list, you have either mistyped their name or they are not a JIRA user.  They can become a jira-user by going to the website https://jira.berkeley.edu and CAS Authenticating.  Check out  the JIRA Getting Started page for more information.


  • To remove a name/group, click on the garbage can symbol.

There are two categories used for permissions; Users and Groups.  Users can be added to a role by the Administrators or into a group by the JIRA Administrators.  Permissions work the same for users in a role or in a group however Administrators can add people to Roles but only JIRA Administrators can add people to groups.

Change the Project Lead Information

On that same View Project Roles page, click on Edit Defaults.  This will display the Project Lead and Default Assignee values.

    

Administrator Role Scheme Views

Other schemes used in your project are set up by the JIRA Administrators.  Administrators can only view the different schemes used by their projects but cannot change them.

To View your Project's Permissions and Issue Level Security Schemes

To see what each role is permitted to do in your project, click on either the Permissions or Issue Security tabs on the left side or the scheme link under the Permissions section of the Summary Page. To see who can and cannot view individual issues within your project, click on the scheme link. All JIRA projects using Roles and having an Issues security scheme use the Role Generic Issue Security Scheme.  Check out the Issue Level Security Page .

To see who will be sent an email notification when a particular JIRA event happens e.g. Issue Created or Issue Commented, click on the Notifications tab on the left side or the scheme link in the Notifications section of the Summary page. To see what Notification schemes are available, check out the Notification Email Options Page.

 

If you have any questions about your project's schemes or how to change them, contact jira-support@lists.berkeley.edu.

 

 

  • No labels