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

jira.issue.editable (false) - Edit option for selected Fields in status

Mateusz Janus_emo9ao

Hey Brothers and Sistser,

when my ticket goes to DONE I can "freeze" it using STATUS PROPERTIES

jira.issue.editable (false).

But I would like to "freeze" only few fields,
System:

- description

- summary

Custom:

custom_123

Any ideas how to achieve it?

Accepted answers

Evgenii

Hi, @Mateusz Janus

The jira.issue.editable property works as an all-or-nothing switch. Setting it to false on a status locks the entire issue, and there's no built-in way to specify which fields stay editable while others get frozen. Jira simply doesn't support per-field granularity through status properties.

There's a well-known workaround though. You keep jira.issue.editable set to false on your DONE status so the Edit button disappears. Then you add a self-transition on that status, something like "Update Fields", that loops back to DONE. Assign a custom screen to this transition containing only the fields you want people to change (description, summary, your custom_123). When someone clicks that transition button, they get a dialog with just those fields, make their edits, and the issue stays in DONE.

Users will need the Transition Issue permission in that project for this to work. The Edit button is gone, but the transition button replaces it for those specific fields. Not the prettiest solution, but it's the standard approach and works on both Cloud and Data Center.

All comments

Hector Florin

Hi @Mateusz Janus ,

I hope you're doing well.

I'm afraid that when it's used, it'll disable all fields in the work item.

However, if you just want to disable only certain fields, I think the best option is to use a separate Field Configuration for Done status and mark specific fields as read-only.
So, you'll need to do the following

Create a new Field Configuration
In that configuration:
- Set:
  - Summary → Read-only
  - Description → Read-only
  - custom_123 → Read-only
Create a Field Configuration Scheme
Associate it with the workflow status "Done"

Important!!
Field configurations apply per issue type — not per status automatically.

So you need to combine this with:

A separate workflow
Or a separate issue type
Or workflow conditions

You can also use an automation tool to try to prevent users to modified the values, but the inline updates are a bit tough to prevent. If you block the View screen and only allow the fields to be updated on Edit or Transition screens, then an automation tool validator can be used to lock certain fields from being updated.

I hope it helps.

Thank you.

Regards,
Hector

Evgenii

Hi, @Mateusz Janus

Marc -Devoteam-

Hi @Hector Florin

This is not possible, there is not option to set a field configuration to a workflow status.

Did you use AI for this answer?

Hector Florin

Hi @Marc -Devoteam-,
Yes, you are correct on both. I've investigated futher and tried to set it up in that way and I couldn't find an option.

Then, I've continued more research, and it now confirms that it's not possible doing it natively.

However, as mentioned in my previous note, if they use an edit or transition screens it can be prevented with a workflow validator, but as it is it doesn't seem to be possible, @Mateusz Janus , so, I apologizes for that part.

It seems @Evgenii has the answer a workaround as he described it.

Thanks,
Hector

Radek Dostál

Considering that anybody who has used Jira for 2 days should know and clearly see how field configuration schemes work.

@Hector Florin question - what is the point of answering questions on a community forum by relaying the question to an AI only to then copy paste an AI answer? Isn't that what OP could have done in the first place? What are you getting out of it other than diminishing the value of forums?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center