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

Why is Summary writable in a sub-task transition, and how can I make it read-only?

Phil Bustin_7fmhjs

My automation copied it to the sub-task. I tried the following in the only two statuses in the workflow, but it didn't work. that didn't surprise me, because the context of the Community post I found it in was for a status, and that made no sense to me, because you can't update a field in a status:

Property Key = jira.issue.editable

Property Value = false

Accepted answers

Bastian Stehmann

Hi @Phil Bustin ,

So you have a screen, that is added to the transition, where you can edit the fields, right?

Why not just remove the summary from that screen, then it won't be editable anymore.

Juan Carlos Vera

In the Screen Squeme, ad a different Screen for "Edit this type of issue" and remove the summary from this Screen.

Then you can´t modify the summary field

All comments

Bastian Stehmann

Hi @Phil Bustin ,

So you have a screen, that is added to the transition, where you can edit the fields, right?

Why not just remove the summary from that screen, then it won't be editable anymore.

Juan Carlos Vera

In the Screen Squeme, ad a different Screen for "Edit this type of issue" and remove the summary from this Screen.

Then you can´t modify the summary field

Phil Bustin_7fmhjs

I'll look into that.

Phil Bustin_7fmhjs

I want the user to see the Summary.

Bastian Stehmann

If a field is on the transition screen, it can be edited. Maybe you can change that with an app like scriptrunner, but I'm not sure actually.

But shouldn't the user know, which issue he transitions?

Bastian Stehmann

Edit Screen won't help you if it is a transition screen you are using in this case.

Nic Brough -Adaptavist-

The edit and transition screens only show the fields the user is supposed to be able to edit.

I don't think anyone needs to see the whole issue they've just read and decided to edit/transition in front of them on the update screen, they only made that decision a few seconds ago and can probably remember why they're changing it.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud