Issue Operations & Automations: View issue vs. Edit issue Screens?

[Tommy Augustine]

Hi Everyone,

I think I have an easy one for anybody who is pretty pro with Issue Operations & Screens:

If I have a Custom Labels Field  name "Package Version," and I add it to the View screen but NOT the Edit Screen, then:

1. Will this make the field viewable and not editable by users?

2. If #1 is a true statement, then Will backend API Automations still be able to set the field on backend?

Thanks in Advance!

[Trudy Claspill · Accepted solution]

Based on my experimentation just now:

Concerning #1

If the field is on a View operation screen and not on an Edit operation screen then:

1. It will be visible when it has a value, and not editable.

2. If it has no value it will be not be visible if it is in the Context fields section, but will be visible if it is in the Description fields section.

Concerning #2

In the above state, Automation Rules were still able to edit the issue, at least when the Actor of the Automation Rule was "Automation for Jira".

[Tommy Augustine]

You're a rockstar for experimenting, to be sure!

[Stefan Salzl]

Hi @Tommy Augustine ,

the screen refers to your action regarding an issue. 

So to say: No, this doesn‘t affect if a field can be edited or not.

If a field is added to the „create“ screen it means that it will apper in the mask when you create an issue. If it is not in the create screen you could not edit or add value to the field when creating an issue.

The view issue refers to when you open an already existing issue. The field will then only be available in this mask when the field is part of the view screen.

Now regarding the edit screen:
As the issue is not really opened in an edit mode in cloud i can‘t see any sense of the edit screen. Issues/fields are edited in the view screen as fsr as I got it.

Hope this was helpful.

Best
Stefan

[Tommy Augustine]

Thank you