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
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
I'll look into that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Edit Screen won't help you if it is a transition screen you are using in this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I want the user to see the Summary.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While that's a good argument, personal experience and the experience of others has sometimes led to the opposite conclusion. You'll have to trust me on this. I'm inclined to leave the field updatable, however, because the IT members who field the sub-tasks would never update the Summary. Flying fingers might wreak havoc on the field, but not likely, and with little consequence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.