Question about read only & masking fields within a issue type for a project

[srikrishnap]

The requirement we want to hide sub-task for bunch of users ( business users) for different issue types . They should have only read only access. In jira as I understand it is all or nothing permissions.

Basically Business users will browse the product catalog and look at sprints. If they want to look at an issue(user story) they should see all fields in read only & sub-task field hidden. 

How to accomplish this ? 

[srikrishnap]

• Thanks Nic. What do u mean by behavior module in Sr? Can u explain a bit?. We have script runner plugin. We are thinking to avoid if it will have performance impact. 

[Nic Brough -Adaptavist-]

Behaviours injects (conditional) javascript into pages, so there will be a performance impact, although it is usually negligible, especially for simple tweaks.

See https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

[Nic Brough -Adaptavist-]

Your observation that "it is all or nothing permissions" is right.  If you can see an issue, you can see all of it, there's no way to hide bits of it.

You can hide whole issues with issue security schemes, but that is still all-or-nothing, it does not go down to a field level.  Sub-tasks inherit their visibility from their parent issues as well.

[srikrishnap]

We want something at a field level. Do we need to explore through Script Runner plugin. ?Can this be achieved through JQL ?

[Nic Brough -Adaptavist-]

Not with JQL, that's for finding issues.

You could use the Behaviours module in SR to hide bits of an issue, but it's a client side trick, so the data is still visible in the html and the user can bypass it if they know a bit about javascript.   There is also no way to hide the fields outside the issue view/edit - people can always see them in the issue navigator and other reports.