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

Custom Field : default value doesn't work

Ratom

Hi,

It's CMP: I have set default value for single selection Custom Field CategoryCS, but it doesn't work, no matter how issue got created value = None.

I set this value under Configure Custom Field/Default Configuration Scheme.

Is this a bug you think?

Thanks

Accepted answers

Trudy P Claspill

Hello @Ratom

Are you creating the issue in the Development project or the Security project? The context you have defined applies only to those two projects.

Have you checked the Create transition in the workflow that applies to the issue type you created to confirm there is not a Post Function overwriting your selection?

Have you confirmed that there is not an Automation Rule running after issue creation that could be overwriting your selection?

All comments

Trudy P Claspill

Hello @Ratom

Are you creating the issue in the Development project or the Security project? The context you have defined applies only to those two projects.

Have you checked the Create transition in the workflow that applies to the issue type you created to confirm there is not a Post Function overwriting your selection?

Have you confirmed that there is not an Automation Rule running after issue creation that could be overwriting your selection?

Ratom

Thanks Trudy, it's CMP, Software Development, Agile.

There is not automation. After disabling Global option and adding project one by one into the context it works, but can't take default option, for now it's OK. I will live with that, too many tricks

Petru Simion [Simitech Ltd.]

Hi @Ratom ,

Using fields requires coordinating multiple factors.

One is the field confguration, that specifies how the field is used by projects and issue types within those projects.

However that does not make the field visible or applicable unless you use it.

If you use it in screens associated with Create, Edit or View operations you will need to add those screen to a screen scheme, the screen scheme to a issue type screen scheme, together with the issue type(s) and the issue type screen scheme to one or more projects.

If you just use the field in a screen associated with a workflow transition, you need to add the feld to the transition screen, the workflow to a workflow scheme and the workflow scheme to one or more projects.

This kind of operations are time consuming when you want to analyse multiple fields.

If you are open to using apps, you can use Fields Dashboard for Jira, an app released by our company.

https://marketplace.atlassian.com/apps/1235965/fields-dashboard-for-jira?hosting=cloud&tab=overview

You can easily depict those relationships at a glance.

Regards,

Petru

In the schemes tab you can depict how fields used in Create, Edit and View screens are used in Projects.

Screenshot from 2024-12-27 15-56-53.png

In the Workflow tab yo ucan see how fields are used in projects.

Screenshot from 2024-12-27 16-12-36.png

Ratom

Thanks Petru and all,
Not sure about 3rd party.

After multiple real prod tests I figured out configuration which worked for me, I found that working with context menu you need to avoid using Global option, rather add project one by one.

Ratom

Shah_ Piyush

As per this community article.... the default value of the Custom field is not appea...

"Setting a default value will not apply the value to existing tickets."

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