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

Can we restrict access for a custom field in JIRA to certain user/group?

MSundaram

We have a custom field - "severity" for which we have values 1,2,3 ,4 [ 1 is the top most priority issue]

Is there a way that only a "qa_leads" group can raise severity-1 issue and for other groups/users either this value should be invisible or disabled?

Accepted answers

Alexey Matveev

You would need an add-on for it like Power Scripts or ScriptRunner.

In Power Scripts you could use Live Fields. You can find more info here:

https://confluence.cprime.io/display/TR/Restrict+a+select+list+to+not+show+certain+values

Thomas Schlegel

Hi,

there is no security on field level in Jira.

A possible workaround:

remove the field from the create and edit screen, leave it on the view-screen
(with such a configuration, noone is able to edit this field)
create workflow transitions on every status "set severity1". The transition should have the same status as target where it came from.
set the field with a postfunction to "1" within this transition
set a workflow condition, so that only users of group "qa_leads" can see this transition
create more workflow transitions with values 2, 3 and 4 - but don't set a condition, so that every user can set values 2, 3 and 4

All comments

Alexey Matveev

You would need an add-on for it like Power Scripts or ScriptRunner.

In Power Scripts you could use Live Fields. You can find more info here:

https://confluence.cprime.io/display/TR/Restrict+a+select+list+to+not+show+certain+values

Thomas Schlegel

Hi,

there is no security on field level in Jira.

A possible workaround:

remove the field from the create and edit screen, leave it on the view-screen
(with such a configuration, noone is able to edit this field)
create workflow transitions on every status "set severity1". The transition should have the same status as target where it came from.
set the field with a postfunction to "1" within this transition
set a workflow condition, so that only users of group "qa_leads" can see this transition
create more workflow transitions with values 2, 3 and 4 - but don't set a condition, so that every user can set values 2, 3 and 4

Nic Brough -Adaptavist-

A slight variation would be to only have two transitions, 1 for "set to 1" and another that goes to a screen with the drop-down, and has a validator on it for "when 1 selected, only pass if user in qa_lead group"

MSundaram

Thanks.. It works.. But i was looking for a solution from a 'free' add-on..

MSundaram

Thanks.. Let me try this approach..

Welcome!

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

Quick Links

Find more posts tagged with

jira