Can Summary (or any field) be made read-only on a transition screen?

[Phil Bustin]

Not urgent, but it would be nice.  I suspect the answer is 'No'.  BTW, I seem to have difficulty adding tags to Questions I post.

[John Funk · Accepted solution]

Hi Phil,

Should the Summary field be able to edit for everyone after the issue is created, and you just don't want them to update the field on the transition screen? 

[Phil Bustin]

Please see my answer to Trudy below.  The Summary field happens in this workflow to be used strictly to indicate the function of the issue (a sub-task).

[John Funk]

The user should review all of that before clicking on the status change. You should not be presenting so many fields in a transition field to make sure they are looking at them. 

[Phil Bustin]

Please see my response to a similar answer by Trudy.

[Nihat · Accepted solution]

Hi @Phil Bustin ,

Yes you can do this with "Scriptrunner-Behaviours". You can find the detail information from the following link:
behaviours-api 

example:

getFieldById("summary").setReadOnly(true)

Kind Regards,
Nihat

[Phil Bustin]

Perhaps we'll get ScriptRunner some day.

[Trudy Claspill · Accepted solution]

Can you clarify your requirement?

Are you presenting a screen that includes fields during the transition, and you want to prevent editing of the fields at that time? If so, if you don't want fields edited during the transition then don't put those fields on the transition screen.

What problem are you trying to solve by putting fields on a transition screen when you don't want the fields to be edited?

[Phil Bustin]

In a transition screen, I want the all the fields you see in the screenshot below to be viewed by the Assignee because they provide important context, but the only field I want editable is the Required field 'Resolution Description'.

Transition screen:

[Trudy Claspill]

Is the user able to edit those fields before they start the transition?

If they are able to edit the fields before they start the transition, then why do the fields need to be locked while they are making the transition?

[Phil Bustin]

I somehow never looked at the view screen; always just went right for the transition.

The Assignee can update some of the fields in the view screen, and some not.  I don't understand why that is.

While I understand the logic of allowing updates in the view screen and then removing them from the transition screen, I personally have needed context reminders when I transition issues.  Maybe I have a short memory, but I've seen others express the same wish.  It happens often enough that one is drawn away from completing a transition, and needs some reminders when returning to the task.    

So for now, I'll consider removing updatable fields from the transition screen.  If we get ScriptRunner (and we might), I'll likely make some fields read-only in the transition, if ScriptRunner works.

[John Funk]

In Cloud it is not obvious that you are in the Edit screen or View screen. More or less when you open an issue you are in the Edit screen (or the default screen if a separate Edit screen does not exist, but it is still in Edit mode). If a field is on the Edit screen then then you will be able to modify the value. If it is not on the Edit screen but is on the View screen (again, assuming there is a separate one) then the user will be able to see the field and it's value, but will not be able to modify it. You cannot dynamically change this for a field - but that's what ScriptRunner Behaviours is about. 

[Phil Bustin]

I remember seeing an Edit function over on the right--maybe an ellipsis.  I don't remember the circumstance under which I saw the Edit function.  Hopefully you can tell me what I saw.

I know I have an Edit screen for a certain issue type, and when I open the issue, I can update fields, so that must be the Edit screen.  How would I be able to see the View screen?  Or is it that Assignees would automatically view the Edit screen, and everyone else the View screen?

[John Funk]

That might have been the old issue view. But in the new issue view that doesn't exist to my knowledge. And, no, the screen doesn't behave different depending on the user - fields are either editable for everyone or not. The Behaviours app is the only one that I am aware of that might provide that functionality for certain fields.