How can you disable a custom field if you are already logged on to the ticket?

[Lenzsér Adrienn]

Hello team!

There is a custom field - the severity field - whose function we envisioned in such a way that if it is logged on the ticket, its value cannot be changed. Is there such a solution?

Thanks!
Adrienne

[Lenzsér Adrienn]

Hello @Hariharan Iyer !

Thanks for the quick response!

The value of the severity field is required at the To do -> In Progress transition. So this field will be permanently filled. Compared to this, the log field should no longer be modifiable after filling it out. So I want to disable logging for further transitions. Can this be solved?

Thank you,
Adrienne

[Hariharan Iyer]

Hi @Lenzsér Adrienn ,

I'm not sure I understood correctly, so let me paraphrase here:

1. Severity will have a value, but that value should not be modifiable

2. Log will be empty initially, but once it's filled it should not change.

Both are possible. For log, you can construct the rule as in the image I added. For severity, the rule would be similar, but the condition would be 

{{fieldChange.fromString}} does not equal {{fieldChange.toString}}

[Hariharan Iyer]

Hi Adrienne,

This is not directly possible at present if the field was not populated on create, but rather set later (or if your project is team-managed). However you can configure an automation rule so that the value is set back to the previous value. The automation rule below depicts how you would do that for the "Due Date" field as a sample.

In the last step, the new value for the field is again the smart value {{fieldChange.fromString}}

You can also add a comment to the ticket when this is done that mentions why the field value was set back (as another step in the rule).

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

For a company-managed project, if you remove the field from the edit screen, people will not be able to change it after it was populated on create.