usergroup > issuetype

[Ronald Kopecky]

hi community

In my project I have many different issuetypes. now I need a usergroup, with only persmissions to insert and edit issues in a specify issuetype.

I search a work around or a simple manual for this.

thx and best regards

Ronald

[Nic Brough -Adaptavist-]

There is no way to stop people creating issues based on the issue type.  The permissions are done at a project level.

You can use workflow properties to prevent editing though, so if you gave your "protected" issues another workflow, you could say things like jira.permission.edit.group = "only people in bob's group".

Your options for blocking create issue are more complex - you either need to modify the UI with something like Behaviours (which won't block people doing it via REST, import, app, or the bloody-minded ones like me who happily hack the javascript) or you can write an impossible validator for the create transition.  A simple "user not in group X" validator can block create, but it's pretty ugly for the users, because they only get blocked after they've entered the issue, and they then lose everything they've entered when they flop to an issue type they can create, and have to start again.

[Ronald Kopecky]

Hi Nic

I don't want to stop people to create a issue. I will reduce the editing on a issuetype.

I hopped, there is a solution based on permission schemas.

[Nic Brough -Adaptavist-]

I'm afraid you can only limit the ability to create issues in permissions.

[Ronald Kopecky]

thx

Is there a other way to restrict the access/view to a issuetype?

[Nic Brough -Adaptavist-]

Yes, as I described already, there are issue-security and workflow properties.

But the only things you can do with create are using Scriptrunner's Behaviours or botching something into a workflow that's ugly for your people (you can put a validator on the create issue transition that prevents them creating, but that returns them to a screen where they could lose all the data they've just entered, so it is less than ideal)