What is the difference between the "issue view" and a screen applied to the "view issue" operation?

[Samuel Geurts]

There are (at least) two ways to influence the shown fields when an issue is opened.

1. The screen that is applied "view issue" in the issue type screen scheme.

2. The issue view, reachable via the request type.

What is the difference between those sections?
How should I use them?

Some fields only are available in the issue view.
Some fields are added to the screen but are not visibile when an issue is opened.
Some fields are added to the issue view but are not visible when an issue is opened.

Of course there is logic behind this. Could someone explain it to me?

[Joseph Chung Yin · Accepted solution]

@Samuel Geurts -

I agreed with other's suggestions.  In general, the screens configuration of your JSM project (Create Issue, Edit Issue, and View Issue) provides a list of fields control - Project settings >> Screens.

On the other hand, Project settings >> Request Types' Issue View is focus on the fields layout when one accesses the issue via the project UI.  By default, if a field is not populated, then it will not be displayed.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @Samuel Geurts

Great question!

Actually, there is a bit of a difference.

The "Issue view" is connected to only one request type and overrides the Screen of the Issue Type (to a certain extent, that's where @Nic Brough -Adaptavist- 's explanation comes into play ).

You can create issues in a Service Project without providing a request type. That's where the "classic" configuration comes into play.

The "issue view" will be different for one and the same issue type, if it's used with several request types.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

There's no difference, the two phrases refer to the "view" "screen" (a "screen" is an ordered list of fields to present when the issue is rendered in the full view, create, or edit mode)

The issue view screen shows a list of all the fields you have configured to appear on it.  However, Jira rearranges a lot of the fields, mainly the system fields, so that they appear in their own related sections.  The view screen definition ignores the ordering of fields.

In a lot of cases, if a field is empty, it will not be shown, even if it is listed in the screen.