Summary field becomes non‑editable on issue view but still editable in Plans view (Jira Advanced Roa

[sankara Kalagadandu]

We are trying to make the Summary field non‑editable for a specific Issue Type (Work Type).

Here’s what we tried:

1. Removed the Summary field from the Edit screen

   • This correctly makes the Summary field non‑editable on the Issue View screen.
   • ✔️ Works as expected.

2. Added workflow property:

   jira.permission.edit.denied = summary

   • This also works in the Issue View screen.
   • ❌ But it does not prevent editing in Plans (Advanced Roadmaps).

In Plans → List View or Timeline, users can still click and edit the Summary.

Question:

Is there a way to make the Summary field truly read‑only for certain issue types including in Plans (Advanced Roadmaps)?

[Tomislav Tobijas]

Yeah... @sankara Kalagadandu Plans do not follow edit restrictions/edit screens (I believe the same applies to workflow properties), and I'm not sure if there's any particular workaround for this 😕

Here's a feature request (more like a bug if you ask me) for it: JRACLOUD-87630: Restrict field editing in Plan based on configured Edit Screen 

[Marc -Devoteam-]

Hi @Tomislav Tobijas 

I don't see this as a feature, as in Plans you can make non-propagated changes.

Changes made in a plan need to be confirmed.

[Tomislav Tobijas]

@sankara Kalagadandu question - I just tested this 👇

However, I did get the opposite result in my case. You CAN edit (and save) the summary even if you don't have it on the edit screen. Basically, what that ticket I linked before says.

I also used 

key	Value
jira.permission.edit.denied	*leave empty

property on "In progress" status, and then tried to save changes, but that didn't let me save them and threw an error/warning, as you can see in the vid above.

[sankara Kalagadandu]

@Tomislav Tobijas , I tried same, it didn't work in plans.

[Tomislav Tobijas]

@sankara Kalagadandu would be great if you could share (screenshots/video) of what exactly you're experiencing + screenshots of configs.

However, as this is a public forum, and if you cannot share some details, you could reach out to official support staff, and they can maybe confirm this or guide you to a specific direction.

[Trudy Claspill]

Hello @sankara Kalagadandu 

When you were testing through Plans did you commit your changes back to the issue, or only change he value in the Plan?

[sankara Kalagadandu]

Yes, but it didn't work

[Marc -Devoteam-]

Hi @sankara Kalagadandu 

On Plan you can make changes, but this is mockup this is not save, did you try to commit the changes that you made via the PLan.

Do they propagate, as mentioned also by @Trudy Claspill