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

Changing a field's settings in a field configuration affects ALL other field configurations

Chander Ahuja

It looks like when i change the "screens" for a field within my XYZ field configuration, it changes for all field configurations including the "Default field configuration" i.e. all field configuration changes look like they are Global changes...what am i doing wrong here

Accepted answers

All comments

Nic Brough -Adaptavist-

Screens are not part of a field configuration, they are completely separate things.

A field configuration tells a project/issuetype how to handle fields, in terms of rendering, visibility and mandatory/optional. These are grouped together in "field configuration schemes" which are then applied to projects.

A screen is a list of fields to be presented to the user when they are doing something with an issue, i.e. Create, edit, view or transition between status. Create, edit and view screens are controlled by the "issue type screen scheme"

I suspect that you are editing screens thinking that they are linked to the field config. You are not, there is no link, you are editing shared screens. If you want to change screens without affecting current ones, you'll need to create new ones and put them into issue type screen schemes

Ignacio Pulgar

+1: Very well explained.

Chander Ahuja

k i understand the difference between screens and fields - i have separate screens as well.

What i am encountering is shown in the two screenshots below. When i change the list of "screens" in one, the list changes in the other one as well, although other elements (required, renderer,...) don't seem to have that problem...as can be seen in screenshots below...

Let me know if that does not clarify the issue I am having.

---------

In Field Configuration A (created for my 3 projects)

SHARED BY 3 PROJECTS

The table below shows all fields configured in JIRA and their properties for ITI Story field configuration.

You can use this page to make fields required, hide/show fields and specify their description. You can also change the screens the field appears on by using the "Screens" link next to each field.

View all field configurations

Name

Screens

Actions

Acceptance Criteria REQUIRED[Wiki Style Renderer]

Enter UAT or other acceptance criteria that must be met before story can be DONE

------

And in Field Configuration B (which just happens to be the default one shared by all the other projects)

Get help!

View Field Configuration

SHARED BY 14 PROJECTS

The table below shows all fields configured in JIRA and their properties for Default Field Configuration.

You can use this page to make fields required, hide/show fields and specify their description. You can also change the screens the field appears on by using the "Screens" link next to each field.

View all field configurations

Name	Screens	Actions
Acceptance Criteria [Default Text Renderer] Enter UAT or other acceptance criteria that must be met before story can be DONE	ITI Create Story Issue Screen ITI View Story Issue Screen	Edit Hide Required Screens Renderers

Chander Ahuja

Please see my comments on your answer. Unfortunately, I posted them as an "answer" to myself... sad so you would have to go to the web page - your answer is not applicable to the issue I am having, i have provided some screen capture to show the problem better...

Nic Brough -Adaptavist-

No, you have not understood.

The screens are not related to the field configurations.

They are separate entities. When you use that link to go to screens, it takes you to the global list of screens. You're editing shared settings.

You need to consider these two facets separately.

Chander Ahuja

Ok - let me see if i got it this time. Taking an example...

For the custom field "Acceptance Criteria" shown in the screen capture, the list of Screens (2nd column) is a shared list - if i alter it in one field configuration, i should expect that all other configurations will show the updated list of Screens in the 2nd column.

continuing...In order that i have the field behave differently (required, show/hide etc.) i just set those attributes within the different field configurations as needed and that works just fine...

However, even if one of the field configurations (lets say the "Default..." one) has a screen where the field may be needed, the screen must be listed in that 2nd column.

Have i got it correct now ?

Thank you for your help.

Nic Brough -Adaptavist-

Ok, let's look again at this statement, in two parts:

>For the custom field "Acceptance Criteria" shown in the screen capture, the list of Screens (2nd column) is a shared list

Almost. I would use the word "global" rather than "shared", but yes, I think we're saying the same thing.

>if i alter it in one field configuration

This is where you are going wrong. The screens are NOT "in a field configuration". That link is nothing more than a shortcut to the screens.

Please have another read of the previous answer.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-core