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

Limit "create issue" permission

Tanner Wortham

I'd like to give our users free reign to create tasks under user stories, but I don't want them to create user stories themselves. In the permission scheme, there's only one permission: create issue. I can think of at least one hack to solve the problem, but I thought I'd ask the group their suggestions.

Accepted answers

Henning Tietgens

Not nice but a possible solution: You can add a validator to the Create transition that rejects a try to create an issue if the validation is negative. The user is able to select the issue type but gets an error message after clicking on create.

Another possibility may be a Javascript to remove the issuetypes from the selection. But that's nothing I can help with... :-)

Henning

All comments

Henning Tietgens

Another possibility may be a Javascript to remove the issuetypes from the selection. But that's nothing I can help with... :-)

Henning

Mark Bednarski

Same here weh have 8 different issue types and public should only be able to create tickets of 3 different types the other ones should be only internally created.

Thanks
Mark

Mark Bednarski

This is similar to this question:

https://answers.atlassian.com/questions/44402/issue-security-allow-only-certain-user-groups-to-create-view-certain-issue-types

We have the same problem here we have 8 different issue types and public should only be able to create tickets of 3 different types the other ones should be only internally created.

A validator is not nice as the user get the feeling his ticket was "rejected" adn make another choice.

Thanks
Mark

Joe Pitt

We work around this by putting the types you want to limit creation of in different projects. You can link issues across projects. Not a perfect solution. People have wanted issue level permissions pretty much from day one but it still isn't there. I don't expect it soon.

Mark Bednarski

Agree with you having a poxy project could do the job, but is not as nice as an integrated way.

Tanner Wortham

The validator route is what i was considering as well, Henning. This just seemed like a common bit of functionality that I had hoped would have a more elegant solution or that I was overlooking in the core product.

RambanamP

check following issue

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

sub-task