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

Description field required also if not included in the screen configuration

Emiliano Visioli_eb2tr1

Hi everyone,

following these instructions Default text for Description field on Jira Cloud (atlassian.com) I successfully implemented a template for a project where I need to customize the Description field content.

I made the same configuration for another project but in this case I've the follwing issue:

- The system field "Description" is still requested during the "Create" operation although I've removed it from the screen that I'm using related to this operation.

Where could I check to solve the issue? I also checked in the field configuration and "Description" is not related with my screen.

In the screenshot you can see:

screen configuration
screen schema configuration
issue type screen schema configuration
the project's screen setting
error on create operation

Thank you,

Emiliano

Accepted answers

Manoj Kumar Gangwar

Hi @Emiliano Visioli ,

Please check your workflow if there is any validator added on the create issue transition.

Marc -Devoteam-

Hi @Emiliano Visioli

You have to check the field configuration that is in the field configuration scheme, that is related to you project.

In the field configuration you can see that the field is marked as required.

If your new project doesn't require this, make a new Field Configuration Scheme, make a copy of the Field Configuration.

Associate the new Field Configuration with the new Field Configuration Scheme. Then associate this to your project and then adapt the Field Configuration to set the Description field to Optional

All comments

Manoj Kumar Gangwar

Hi @Emiliano Visioli ,

Please check your workflow if there is any validator added on the create issue transition.

Marc -Devoteam-

Hi @Emiliano Visioli

You have to check the field configuration that is in the field configuration scheme, that is related to you project.

In the field configuration you can see that the field is marked as required.

If your new project doesn't require this, make a new Field Configuration Scheme, make a copy of the Field Configuration.

Associate the new Field Configuration with the new Field Configuration Scheme. Then associate this to your project and then adapt the Field Configuration to set the Description field to Optional

Emiliano Visioli_eb2tr1

Thank you Marc, this was the issue. Once marked as optional, problem solved. I thought that as the field wasn't shown, this configuration wouldn't affect the process.

In my case i don't need to create a new field configuration as there is only one project that is using it.

Thank you again,

Emiliano

Emiliano Visioli_eb2tr1

Thank you Manoj, I checked but validation is ok in the workflow, the problem was related to the Required option as described above.

Thank you anyway, actually I haven't still check the validators in the workflow

Marc -Devoteam-

Hi @Emiliano Visioli

Even if the field is not on a screen, the field configuration is higher in rank than the screen.

So the Field Configuration, is the first point to look into in such cases

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server