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

How to have different field configurations within a project?

George Bettley

Hi community,

I have a Project "Service Requests" and within that project I have different Issue types.

Different Issue Types have different custom fields assigned to them. For some of the Issue types I want to have required fields that vary between types.

I have tried creating Field Configuration schemes and associating Issue Types to that, however in my Project all Issue Types are linked to the default.

Is it possible to use multiple Field Configuration schemes in one Project? If so, how do you set this up?

Accepted answers

All comments

Mohamed BENZIANE

Hi,

In your field configuration scheme you cap map field configuration to an issue type, you can have different field configuration in you field configuration scheme.

Can you make sur the you project is using the correct Field Configuration scheme.

https://support.atlassian.com/jira-cloud-administration/docs/associate-field-behavior-with-an-issue-type/

George Bettley

Thanks Mohammed. So I've completed those steps before however in the Project I can only seem to choose one field configuration scheme, which is default. I want different configurations for different issue types within one Project. Is this possible please? Screenshot 2021-01-25 at 11.56.42.png Screenshot 2021-01-25 at 11.58.34.png

Nic Brough -Adaptavist-

You are confusing "field configurations" with "field configuration schemes" (a very easy mistake to make, I've never thought it was clear)

A "field configuration" is a list of all the fields, with flags to set their behaviour.
A "field configuration scheme" is a list of all the issue types, which tells a project which "field configuration" to use for each issue type in it

You only need one field configuration scheme, but that scheme can point to many field configurations.

The minimal example is you create two field configurations; let's call them "FC - bugs" and "FC - everything else". Set the flags you need for your different acting fields in those two. Then create a field configuratin scheme (FCS), and tell it "by default, use 'FC - everything else' but for Bugs, use 'FC - bugs'". Associate that with your project, and you'll find most of your issues behave in one way, and bugs are different.

George Bettley

Thank you! That makes total sense, have finally worked it out. Appreciate it

Noga Shemer

The thread helped, thanks

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management