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

Set particular custom field read only

Liwei E

Hi There,

I am currently administrating a JIRA project. and i have added several cutome fields. and now there is a require for restricting editing on certain fields during the lifecycle of an issue, or in another word, once some of the custom fields have been created, they should be disabled from editing for all users.

I am thinking there would be two way of doing these,

make the field read only, but seems the read-only text field is not design for this scenario, any other suggestions?
do some user permission setting, but seems there is no permission setting for view only.

Could you guys suggest a solution or workaround doing this?

Thanks in advance.

Liwei

Accepted answers

Nic Brough -Adaptavist-

Hang on, there's a whole lot of totally unneccesary code being thrown around here.

Peter's original answer is correct, as is Henning's follow up.

Put the field on the CREATE and VIEW screens. Do not put it on the EDIT screen.

The user can then add data to the field when it is created. They will not be able to change it again. Click-to-edit is disabled for fields that are not on the edit screen. If you need to change it later in the process, you can put it on a transition screen.

All comments

Peter Van de Voorde

Hi Liwei,

If you only add those field on the issue create screen and don't add those fields to the edit screen in or any screens you use during your workflow they should not be editable after doing an issue creation.

Best regards,

Peter

Bhushan Nagaraj4

Hi Liwei,

You would need to develop your own custom field to achieve this functionality.

Thank you

Bhushan

AlaA

Hey Liwei,

I think that should be possible using Behavious plugin, as it allows you to make certain fields to be read-only.

You can download the plugin here:

https://marketplace.atlassian.com/plugins/com.onresolve.jira.plugin.Behaviours

Similar discussion was in the following Answers:

https://answers.atlassian.com/questions/113437/how-to-set-some-fields-as-read-only-after-submit-an-issue

I hope that helps.

Cheers,

Bharadwaj Jannu

check

https://answers.atlassian.com/questions/113043/making-custom-field-read-only

https://answers.atlassian.com/questions/169296/how-to-make-a-user-customfield-read-only-through-javascript-on-create-screen

Henning Tietgens

Besides using a plugin the normal way to archive this is to remove the field from the edit screen and add a transition to the corresponding workflow with a transition screen which contains the field. Access to the transition can be controlled through workflow conditions.

Henning

Liwei E

Cheers~~Plugins, i love it. but i am not the system admin, and current there is no plan for inviting any plugins in our company JIRA support team

Liwei E

Thanks Henning~~ i think the transition control is a good idea, but the default tranisiton conditions provided by JIRA is really limited. But i will try your advices.

Liwei E

Thanks Peter.

But if i create an isolated edit screen or view screen, the fields would be viewed during the workflow lifecycle.

I would really like the fields to be viewed and also non-editable.

Liwei E

Yes, i currently trying to use some scripts to work around make the 'click to edit' link to be hidden

Bhushan Nagaraj4

Why not write your own custom field that is editable by selected project roles or groups?

RambanamP

you can hide/show field to specific group by using following scritp, chenage custom field id, group name as per your requirement

&lt;script type="text/javascript"&gt;  
jQuery(document).ready(function($) {
	JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e,context) {	
		hideFieldForGroup();    
	});
		hideFieldForGroup();
function hideFieldForGroup(){
        var user=getCurrentUserName();		
		var statusText=$('#status-val').text();	
		var status=$.trim(statusText);
		if(isUserInGroup(user,'Developers') &amp;&amp; status=='In Progress'){			
			$("#customfield_10571").closest('div.field-group').hide();
		}else if(isUserInGroup(user,'Users') &amp;&amp; status=='Open') {
			AJS.$("#customfield_10571").closest('div.field-group').show();
		}

}
function getCurrentUserName()
{
var user;
     AJS.$.ajax({
        url: "/rest/gadget/1.0/currentUser",
        type: 'get',
        dataType: 'json',
        async: false,
        success: function(data) {
            user = data.username;
        }
     });
     return user;
}
  
  
function getGroups(user)
{
var groups;
     AJS.$.ajax({
        url: "/rest/api/2/user?username="+user+"&amp;expand=groups",
        type: 'get',
        dataType: 'json',
        async: false,
        success: function(data) {
            groups = data.groups.items;
        }
     });
     return groups;
}
function isUserInGroup(user, group){
    var groups = getGroups(user);
    for (i = 0; i &lt; groups.length; i++){
         if (groups[i].name == group){
              return true;
         }
    }
    return false;
}
    
 });

&lt;/script&gt;

Liwei E

oh, really? we can directly use the jQuery libray? is this default supportive by JIRA?

RambanamP

yes, jquery plugin will be included in jira, you can use AJS(Atlassian JavaScript) frame work also

check this

https://developer.atlassian.com/display/AUI/Getting+Started+with+AUI

Nic Brough -Adaptavist-

Hang on, there's a whole lot of totally unneccesary code being thrown around here.

Peter's original answer is correct, as is Henning's follow up.

Put the field on the CREATE and VIEW screens. Do not put it on the EDIT screen.

Liwei E

But the fields still needs to be viewed during the flow, and with my understanding of JIRA, if the certain fields can be viewed, it also means the fields can be modified.

AlaA

I'm sorry to hear that.

Let's wait and check if there are any users who can suggest some better workarounds which might work on your side.

Cheers.

Henning Tietgens

What do you mean with "during the flow"? If a field is editable on the view screen depends on if the field is on the edit screen.

If you add the field to a transition screen it's editable in this transition (independend from the view/edit editability). A transition could be "protected" by a condition.

Peter Van de Voorde

Hi Liwei,

If the fields are only viewable on the view screen (the screen associated with the view issue action in your Screen Scheme) and not on any other screen (except the screen associated with the Create issue action in your screen scheme) they can not be edited.

Best regards,

Peter

Sam Huawey

Funny. Where are you going to put this script? At least you need to have access to Jira working directory (to modify vm templates). And merge your changes each time Jira upgrades. Not really a good way to my opinion.

Flash_Sheridan

“This app has been archived”

sushanta

Hi Team,
We have a requirement to make editable only 2 custom filed from edit screen out of 30 for a specific group only i.e project developer role can edit 2 fields only.Is it possible using Behaviour (Adaptavist script runner) ?
Regards,
Sushanta

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration