How do i make a field readonly based on transition status in jira cloud

[Syed Nawaz]

I have a field called "service" it need to be read-only only during when story moves from validation to done state , how to achieve this in jira cloud , i can easily solve this jira data center(behaviour) , But in jira cloud am finding challenges . please help me on this ?

[Andrei Cuzuioc _ScriptRunner_]

Hi @Syed Nawaz ! 

Behaviours feature is now supported on Transition View in Jira Software on Cloud. You can check the details of this first release, supported fields as well as demo videos here.

Best regards,

Andrei

[Syed Nawaz]

@John Funk To make a Field readonly why do i need to go to screens, basically the field is editable starting from open to validation and its get readonly only while done or close stage , if i remove the field from edit screen , how will the user  see the data, why is this simple thing complicated in jira cloud , which was easier in jira DC .Since we are in migration from data center to cloud , its very difficult to go and remove individual field from screen , Unfortunately this will not solve the issue ?

[Syed Nawaz]

Hi @John Funk I have tried but its not working , and behaviours in jira cloud work only on create issue and issue view , please go through the requirement  i need to achieve that during transition from validation to done status, if you say its work in jira cloud behaviour provide me a sample script of behavior, please provide a valuable solution Thanks in advance

[John Funk]

Hi Syed,

You would need to the use the Behaviour app in Jira Cloud also. 

[John Funk]

I don't use that app, so you would need to contact the vendor directly for assistance.

Your other option is to not include the field on the Edit screen. Then create a transition screen and add the field to it. Add the transition screen to each transition in your workflow. For those steps in the workflow that do are open to all persons, then there would be no Condition. 

But for the steps that require it, then add a self looping transition to the status, add the screen to that transition, and then add a condition to the same transition to limit who can execute it and therefore, it limits who can update the field. 

[John Funk]

Please reply in line here to my original answer so that readers can follow the thread easier. 

And it is very easy to remove a field from a screen. You simply remove it. They can still see the values with the View screen. But you will need to create both of those screens if you have not already. You can simply copy one, rename it and remove the field. 

The users can populate the field as it moves through the workflow. If it is populated at create then they can see it and change it as they move through the workflow. But it will be locked down at the steps you choose.