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

How to show some custom fields to admin and team leads but hide from all others?

Hizkeel Khan

Hi,

I hope everyone is doing well. I have created a custom field of client estimation but I don't want my team to see that at any point of time. Will admin and teams should be able to see it.

Is there any way to achieve this using Jira automation or screens? This custom should be visible to Admin all the time not to team at any time.

It's super important if someone can help me in this? I would prefer to use Jira native instead of using any third-party apps.

Accepted answers

Kuherrn Nagayaindran

Hi @Hizkeel Khan

I have not tested this out during the "View" issue operation but with Scriptrunner Behaviours, this can be done during "Create & Edit" issue operations. Demo is here.

EDIT 1: If you do have Scriptrunner and decide to go down this route, can you please reply here if it does work for all issue operations. Danke!

All comments

Ash Yadav

Hi @Hizkeel Khan

I don't believe field level permissions are possible in Cloud without a third-party plugin.

There are several threads discussing this in detail:

https://community.atlassian.com/t5/Jira-questions/hide-show-fields-depending-on-a-users-permissions/qaq-p/712544

https://community.atlassian.com/t5/Jira-questions/Hide-the-fields-based-on-a-project-role/qaq-p/1604527

Issue opened with Atlassian and suggested workarounds (including Cloud):

https://jira.atlassian.com/browse/JRASERVER-1330

This plugin seems to work well for most people:

https://marketplace.atlassian.com/apps/1226365/secure-custom-fields-for-jira-field-permission-security?hosting=cloud&tab=overview

Kind Regards,

Ash

Kuherrn Nagayaindran

Hi @Hizkeel Khan

I have not tested this out during the "View" issue operation but with Scriptrunner Behaviours, this can be done during "Create & Edit" issue operations. Demo is here.

EDIT 1: If you do have Scriptrunner and decide to go down this route, can you please reply here if it does work for all issue operations. Danke!

Hizkeel Khan

@Ash Yadav - Thank you for the answer. It solves the problem I was having but it still shows the field. It only hides the values in the field. Is there a way to hide the custom field completely?

I don't want users to see the field at all apart from those who have access. If they are seeing the field and value hidden then they will get curious.

Please let me know if something like that is possible?

Hizkeel Khan

@Kuherrn Nagayaindran - I have installed the script runner for Jira but it is not showing behavior field when I create any behavior. Any idea?

Without the behavior field how I am going to make any changes to any field?

Kuherrn Nagayaindran

Hi @Hizkeel Khan

I re-read your original post and realized that you preferred the utilization of "Jira native instead of using any third-party apps."

If so, I would steer you towards the usage of Issue Security Schemes. Now there are a few caveats to note:

Issue Security Schemes are scoped to their own individual respective project so should this "Client Estimation" client field appear in the entire project, then Issue Security Schemes would not be the right approach - instead look into this Secure Custom Fields (3rd party add-on). Also see this on why Atlassian did not implement it.
Should the "Client Estimation" custom field only appear in certain types of issue where other team members do not work on it (they do not interact it in any way shape or form), then this would be an appropriate implementation.

The reason why you do not see any "Behaviour" fields is because it has not been configured yet - you need to scope the action of the Behaviour (which project and which issue type within said project) and then write a custom Groovy/Java Script for it to work. Please see this video demonstration for detail. (NOTE: the video is for Jira D/C but behaves nearly identical for Jira Cloud)

Behaviours give you more control over fields in Jira. A field configuration customizes how fields behave, based on the issue operation screen they appear on. However, a behaviour in ScriptRunner allows you to take that field customization further, defining how fields behave for issues in a given project or issue context.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud