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

Screen and Issue layout

unknown

Here I can edit the fields for Issue type Task and Operation type - view

have a look:

I've added the screen to provide more info.

The problem is the following:

By adding the field Approvers (via the Configure Screen) I was expecting that I couldn't remove this field from the issue layout. But it not working like I was expecting.

Could you provide some info?

In fact my scope of the fields is not correct here:

So I renewed the script and noticed that the field Approvers is still there, but why is it so?

Two ways should work here (in my mind):

1. the field should disappear on the "Configure screen" after I delete it from the "Issue layout"

2. I should get some error message informing me that I can't delete the field on the "Issue layout" because I've chosen this field on the "Configure screen".

But none in this way was working at all.

Could you share your thoughts?

Accepted answers

unknown

Here is a great video on YouTube:

Definitive Beginners Guide to Screens | Crash Course

Here are all the answers to my questions here.

I should see it in the first place. It would save a lot of my time.

All comments

Marc -Devoteam-

Hi @[deleted]

There is a difference in Layout on project level and Screens.

On screens you decide which fields are on a certain screen and these can be used in screen schemes and a screen scheme can be used in an issue type screen scheme.

The layout option is there to provide project admins the choice to define which of the fields from the screen to show on the issue in their project

They are not related, in the config you can add any field from the system, but if it's not on the screens used in the project the field can't be used.

Check for infromarion on issue layouts here, https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-layout/

unknown

Hi @Marc -Devoteam-

thank you for the reply!

clicking on the task I am going to "activate" Issue Layout settings, but not the Operation View issue, is it so?

It is not the same (issue Layout settings and Operation - View issue)?

If this is not the same, how to "activate" the settings of Operation - View issue?

Kindly let me know.

I am reading the link you sent in the previous reply, thank you.

Marc -Devoteam-

Not this is not the same.

In a screen scheme you have 3 operations.

This means you can have a different screen for each operation.

This provides you to have a limited just need fields on creating an issue, have fields on the edit screen only to be filled after create an a view screen when fields can be used that you only want to show, but no editable.

Here you can find documentation on screens, screen schemes and issue type screen schemes.

manage-issue-screens

unknown

Unfortunately, I still don't get the differences between the Configure Screen and Issue Layout.

I've added the field Approvers again on the screen here:

To see what is going to change on Issue Layout. So the newly added field appears here:

Why is it so?

There should be some correlation between the Configure Screen and Issue Layout. I just can't get it(

For those who understand my problem here - kindly provide more info ^_^

unknown

Here is a great video on YouTube:

Definitive Beginners Guide to Screens | Crash Course

Here are all the answers to my questions here.

I should see it in the first place. It would save a lot of my time.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud