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

Field configuration on a plan with multiple projects

Snorre Strand Asbjørnsen

I am working as a new administrator for a Plan that consist of 12 different projects all using their own issue type screen scheme and field configuration scheme. I want to create unity of fields where fields are unique to each specific Issue type. When connected with a parent from a specific project this is the field configuration scheme it will use in accordance with the Issue Type being created, viewed or edited.

Accepted answers

Trudy P Claspill

Hello @Snorre Strand Asbjørnsen

I'm not sure if I have understood what you are trying to do.

For Company Managed projects you set a Field Configuration Scheme.

Within the Field Configuration Scheme, Field Configurations are associated to Issue Type.

In that manner you can configure the Schemes used by the projects to associate the same Field Configuration with a given issue type in all projects. You would have to update the Field Configuration Scheme used by each project.

For Screens, a Screen is associated with an issue operation (Create, View, or Edit) in a Screen Scheme.

A Screen Scheme is associated to an Issue Type in and Issue Type Screen Scheme.

An Issue Type Screen Scheme is associated to a Project.

So, you can again set up specific screens to use for issue types across projects by modifying the Screen Schemes used in the Issue Type Screen Schemes associated with the projects.

However you made this statement:

When connected with a parent from a specific project this is the field configuration scheme it will use

You cannot base screens or field configurations for an issue type on the parent issue to which a given issue is connected.

All comments

Trudy P Claspill

Hello @Snorre Strand Asbjørnsen

I'm not sure if I have understood what you are trying to do.

For Company Managed projects you set a Field Configuration Scheme.

Within the Field Configuration Scheme, Field Configurations are associated to Issue Type.

For Screens, a Screen is associated with an issue operation (Create, View, or Edit) in a Screen Scheme.

A Screen Scheme is associated to an Issue Type in and Issue Type Screen Scheme.

An Issue Type Screen Scheme is associated to a Project.

So, you can again set up specific screens to use for issue types across projects by modifying the Screen Schemes used in the Issue Type Screen Schemes associated with the projects.

However you made this statement:

When connected with a parent from a specific project this is the field configuration scheme it will use

You cannot base screens or field configurations for an issue type on the parent issue to which a given issue is connected.

Snorre Strand Asbjørnsen

Hey, thank you for the quick response.

So if I wanted to create unique field layout of all issues based on the issue type would I just create separate screens for each issue type and put them into different screen schemes than put those screen schemes into issue type screen scheme which I than called all the screens schemes to each of the relevant issue types?

Snorre Strand Asbjørnsen

Follow-Up Question: If I change the issue type schemes for an issue type with a new one will this take away the information that was already in the issue?

Trudy P Claspill

There are multiple things to consider here, and we may not be using the terminology the same way.

A Field Configuration determines some features for fields that will may be used, such as if the field is always Required or is Optional, if it is Shown or Hidden.

A Screen is used to define the fields that will be available for an issue in its Create Issue dialog or in the View/Edit screen.

Each of these can ultimately be associated to issue types through Schemes. Each project will have Scheme(s) associated to it so that the Field Configurations and Screens are applied to the issue types in those projects.

If you want the issues types used in multiple projects to use the same settings defined in the Field Configurations and in the Screens, then I would recommend you use the same Scheme(s) for these in all the projects that need to be consistent.

In addition to those Schemes, within each project it is possible for the Project Administrator to adjust the Issue Fields Layout for the View/Edit display of issues within that project. The Layout applies to all issue types that use the same Screen Scheme. That Layout will apply only to that one project. However, the Layout could be copied to other projects that use the same Screen Scheme. But each project could still change their Layout at any time and end up out of synch with other projects.

Regarding your follow-up question: If you change the fields that are part of an issue type's scheme and remove fields then the data will remain in the database but will not be visible when viewing the issue. It would still be available through issue search.

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