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

Restricting edition of a custom field

ashleyg

I want a custom field called 'Root Cause' exactly similar to Components field( which comes by default in jira) of Labels type but only admin should be able to add/modify values to it, others should only be able to select the possible options that come as drop down suggestion. I tried with Jira security plugin but using that i found that thsi field doesn't appear as part of som e tranmsition screen for anybody else other than admin for whom we have set security scheme. Actually field security scheme only gives two options "Allow all" or " deny all". Please help me on this.

Accepted answers

All comments

Nic Brough -Adaptavist-

It sounds like you just need a simple multi-select custom field. Administrators determine the list of options on those, users can put them in. You don't need to think about security or plugins to do that.

ashleyg

Actually it should be multiselect field but it should be of type labels exactly similar to like components...so that once such a label option is selected for this field it should be navigable on the view screen

ashleyg

Hi Nic,

I would want to have this custom field in some transition screen say for eg closing of isssue wherein this field should appear for all on that transition screen but then other user only able to select value from there but Project admin ( not jira admin who can add default values to custom field under custom field configuration as drop down options) can also add new values to it and then submit the closing screen. This can't be achieved by multiselect field as they don't give option like labels and need to be modified through custom field configuration which can be done only by jira admin or jira system admin.

Joe Pitt

JIRA doesn't allow project admins to update field configurations.

Vijay Khacharia

This answer might help you. The code in the description makes a multi-select field behave Components field, auto fill on typing.

https://answers.atlassian.com/questions/43534/can-i-have-multi-select-custom-field-behave-like-components-versions-fields

ashleyg

Hi Vijay,

I tried out this on one of my multiselect custom fields but it doesn't produce any effective result. I replaced the custom_field id with that of mine in the code and also added the correct java script code under description of my field but failed to notice any changes.

Could you please tell me the entire process.

Vijay Khacharia

Hi,

Here is what I did. Create a custom field of type "Select List (multiple choices)". Added the script below in description of the field.

&lt;script type="text/javascript"&gt;
 
(function($){
    new AJS.MultiSelect({
        element: $("#customfield_14250"),
        itemAttrDisplayed: "label",
        errorMessage: AJS.params.multiselectComponentsError
    });
})(AJS.$);
 
&lt;/script&gt;

Note that you need to change the customfield_14250 for your customfield ID.

The field acts as autofill on the screen afterwards.

Hope this helps.

Regards,

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud