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; } } }

JIRA Newbie Admin Question

David Kiellar

My company is evaluating JIRA. I have used it in the past as a user, but never an admin. I am just evaluating it at the moment but have some questions on how to set it up. So here is my scenario.

We have different programs that we want to use this. So for that I know each program would be a project. So I create the projects, say ProgramA, ProgramB, and ProgramC. So I got that far. I am confused as how to set up users and groups and project roles.

Here is my situation.

Each program will have an Admin, Program Manager, and users, maybe a few others. Would these be the project roles?

So say I have UserA. He is a user for ProgramA. I want it so he can only see ProgramA items. UserB is a Program Manager on ProgramA and ProgramB, so he should see both. UserC is a user on ProgramC only.

How do I set this up. I am confused about the groups/roles/etc. Every program will have the same tasks. Also, how do I set up permissions for each group, do I do that by the project roles? Example, users can only create issues, but program managers can create issues, close issues, etc. Admins can do everything.

Please help. Thank you

Accepted answers

Jobin Kuruvilla [Adaptavist]

Start by reading this :

https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

You will be using groups/roles etc in the permission scheme. If you have different people using different projects (or programs as you call it), add them in to the project roles and use the roles in the permissions. If there are groups, like the jira-administrators, which has access to all projects, you can use it in permission scheme directly.

You can also define new roles and/or define which groups will have default access for each roles.

All comments

Jobin Kuruvilla [Adaptavist]

Start by reading this :

https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

You can also define new roles and/or define which groups will have default access for each roles.

David Kiellar

I guess i am just confused between groups and roles and how they apply to different aspects of JIRA

David Kiellar

So if i have a group called ProjectA_Users which has UserA and UserB in it. Should I have a role called ProjectA_Users? Or do I just add the group to the project?

David Kiellar

Ok, let me give it a try. Thanks for the help. I will probably be back with more questions.

Walt Fles1

Hi Dave (is this the DK from the PEAK of my career I think it is?)

First of all, you have to set up an issue type scheme for the project(s).

You use the issue type screen scheme.

You create your screens (view, edit/create) and associate these screens with an issue type in the issue type screen scheme.

Then you associate the issue type screen scheme to the project.

David Kiellar

Do I create a view,edit, resolve screen for each issue type?

Walt Fles1

you can share them, or have separate view and edit/create (1 for both) screens.

It depends if want each view to be different, i.e.:

If in view only you have fields which you dont want displayed on edit/create, or you dont want

users to modify but are for display only.

David Kiellar

So for Business opportunities I want the create screen to basically have three fields, Title, description, and status. the edit screen would only allow for a status change, the other fields would not be editable.