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

Is it possible that the new custom fields do not appear on all Fields Configuration ?

Mélanie Liguet

Hi,

On jira cloud, I created specific Field Configuration, for very specific projects, I hide many fields to keep only those useful to the project.

But when I created a new custom field, it appears on all Field configuration.

Is it possible that the new custom fields do not appear on all Fields Configuration ?
I would like them appear only on Défault Field Configuration for example.

regards

Accepted answers

Tom Lister_fo1j4e

Hi @Mélanie Liguet

It make more sense to me to view the default field configuration as the base "class" and all other field configurations are just derived from that. That is custom field configurations are providing specific overrides to the default field configuration.

There isn't a way to restrict custom fields to any specific field configurations.

Available fields can be controlled by the screen configuration and custom field contexts.

All comments

Tom Lister_fo1j4e

Hi @Mélanie Liguet

There isn't a way to restrict custom fields to any specific field configurations.

Available fields can be controlled by the screen configuration and custom field contexts.

Mélanie Liguet

Hi,

Thank you for this quick response.
So, what is the point of having several Scheme field configurations?
might as well have a global field configuration Scheme and use screens and field contexts?

regards,

Tom Lister_fo1j4e

Hi @Mélanie Liguet

Field configs are useful as there is scope to customise multiple field behaviours using field configurations.

i.e.
A project is linked to a 'field configuration scheme'. And that scheme maps field configurations to issue types. This allows different issue types to to have different configs e.g. mandatory/optional. This level of detail wouldn't be possible with a global field configuration.

Custom field contexts can restrict which projects a field is available for. And to some extent control the content of drop down lists. But a context can only be added once to a project against selected issue types. So within a project, for a custom field, there can only be the default context and a custom context for that project. I've often had cases where different issue types in a project should have different options but it can't be implemented without scripts.

Screens and Issue type screen schemes can control the fields made available on the issue views. But they have to be consistent with the other schemes. e.g. if a field made mandatory in the field config is not in a screen it will error on submit.

All in all, screen and field setup is Jira is quite fragmented and needs planning before implementing. Team managed projects handle this in a more intuitive way because there are no concerns about usage outside the project.

Best

Tom

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud