Community
Q&A
Jira
Questions
Put permissions on who can create user story issues?

Put permissions on who can create user story issues?

Is it possible to put permission controls on who can create 'epic' and 'user story' type issues?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes

Not really. A user in a project can either create issues (of any type) or they can not. You can play some tricks with fields to block them, or other javascript tricks to try to supress it in a browser (javascript is easy to bypass and won't work if they use REST etc).

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I think this a major gap in authorization control

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I think it's a minor issue, but one that increased in severity when Epic and Story became special issue types in the Agile plugin.

Atlassian have stated they won't fix it though (sorry, I don't have my bookmarks to hand), on the grounds that it's not a serious problem and not many of us voted for it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Put permissions on who can create user story issues?

1 answer

Comments for this post are closed

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events