Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We are advising to work with roles as it has a couple of advantages</p> <h3> a. You can setup the complete configuration based on roles.</h3> <p>For instance you might have a workflow transition 'validated' which can only be executed by someone who is a tester.</p> <p>You have the choice to add a transition condition 'user is in group tester' or 'user has the role tester'. </p> <p>If you are working in an organisation where users have different roles in different projects, choosing the first transition condition (user is in group tester) will not work (or you would need a new workflow for each project) </p> <p>The same applies for notifications.<br> You can configure a notification on the 'issue resolved' event, specifying that the 'users in group tester' get notified or 'users who have the role tester'. </p> <p>When using roles, adding someone to a project is very simple - just check what role the person has in the project, add them in the project configuration (view members) and you are done. He will have the right permissions, get the right notifications ...</p> <h3>b. Configuration</h3> <p>When you use roles for configuration, you don't need system administration rights to add someone to a project. The project lead will be able to add the user. No need to bother the system admin.</p> <hr> <p>Looking at your description, I would have </p> <ol> <li> A project role 'employee' <li> A project role 'customer' <li> A group 'employees' <li> configure the project role such that the group employees is a default member of the project role employee </ol> <p>This way you can use the same permission scheme for all projects. When adding a new project, you just need to add the client specific userid to the client role. When a new employee start, you add him to the employees group.</p> <p>The day that you have a specific, ultra secret project, where only a couple of employees need to have access, you can remove the group 'employees' from the role 'employee' and add the specific users to the role.</p> <p>Hope this helps</p> <p>Francis</p>
    singulars
    1. This table or related slice is empty.
    1. POWhen and how should one use project roles instead of groups within JIRA?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USFrancis Martens
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhen and how should one use project roles instead of groups within JIRA?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow does the JIRA Users global permission relate to this, if at all? It seems that users must have this permission in order to log in to JIRA. Since JIRA Users can only be assigned a group do I need a group for customers as well?
      singulars
      1. PO
      1. USRyan Taylor
    2. COThe global permissions are for setting permissions on global functionalities such as accessing JIRA, administrative tasks, bulk changes and so on. You should use at least one group to designate the people who are allowed to access JIRA (normally the group JIRA_users, but I've seen instances where they had 3 different groups)
      singulars
      1. PO
      1. USFrancis Martens
    3. COSo you might have one group 'employees', one group 'customers' and provide these two groups permission to access JIRA. When a new employee starts, add her to the employees group. She will have access to JIRA and to all projects. When a new customer is added, add him to the customers group and to the specific projects where he should have access to - having the customer role.
      singulars
      1. PO
      1. USFrancis Martens
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload