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

rights for a user to only create certain issue types

Andre van der Elst

Is it possible to configure jira to allow certain issue types only for some users/groups ?

For example, I would like to create a group of users that can only create 'tasks' or 'improvements' , while other users should be able to create all issue types.

Accepted answers

Andre van der Elst

I found the discussion on this issue buried somewhere on jira.atlassian.com.

https://jira.atlassian.com/browse/JRA-5865

The issue seems to be popular, but since Atlassian fears it will make Jira more complex they deemed this a 'wont fix' issue.

I don't think it will make things any more complex than they already are, but they took 5 years to turn down the first request for this functionality, I won't even recommend my customer to request this feature again.

All comments

Anni R

Hi,

You can configure permission scheme for you project as you want. There you can edit permissions by project permissions, comments permissions and issue permissions (create, edit, move).

In permission scheme you can't configure what issue type someone can create, but with issue type screen scheme you can activate those issues for you project what you want.

http://confluence.atlassian.com/display/JIRA042/Managing+Project+Permissions

Andre van der Elst

I see, so as a workaround I could create a project several times, say 'projectname-bugs' , 'projectname-tasks' , 'projectname-improvements' etc. and then create permission schemes and screen schemes accordingly.

I'm not fond of the workaround, but I'll check with my manager if this is an acceptable solution. BTW, If anyone from Atlassian is reading this and knows if this feature is considered for a future version please let me know.

Jim Birch

If you are interested in an improvement go to jira.atlassian.com and search for relevant issue(s). If you find it you can vote it and add a comment. There may be useful discussion. If it's not there, create it.

https://jira.atlassian.com/secure/IssueNavigator.jspa

Andre van der Elst

I found the discussion on this issue buried somewhere on jira.atlassian.com.

https://jira.atlassian.com/browse/JRA-5865

The issue seems to be popular, but since Atlassian fears it will make Jira more complex they deemed this a 'wont fix' issue.