Hello Jira Community, I am a Jira Server Admin and have been adding/modifying custom fields for many times. This morning I created a new custom field (single-select), and applied it to one single issue type in one Jira project with two options, "Available", "Development Required". While I set "Available" as the default value, I still get None as the default value on Jira edit screen. I have set default values many times before, so I don't think I made any mistakes in the process. Since this is a brand new custom field, there shouldn't be any automation rules, post-functions, or ScriptRunner scripts are involved either. Could anyone advise on what might be going wrong? Any suggestions on where to double-check would be much appreciated! Version: Jira Data Center 9.12.6 Best, Becky

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

Default Custom Field No Populated

Becky Yu

Hello Jira Community,

I am a Jira Server Admin and have been adding/modifying custom fields for many times. This morning I created a new custom field (single-select), and applied it to one single issue type in one Jira project with two options, "Available", "Development Required". While I set "Available" as the default value, I still get None as the default value on Jira edit screen.

Screenshot 2024-07-10 111643.png

Screenshot 2024-07-10 111715.png

I have set default values many times before, so I don't think I made any mistakes in the process. Since this is a brand new custom field, there shouldn't be any automation rules, post-functions, or ScriptRunner scripts are involved either.

Could anyone advise on what might be going wrong? Any suggestions on where to double-check would be much appreciated!

Version: Jira Data Center 9.12.6

Best,

Becky

Accepted answers

John Funk

Hi Becky,

Default values apply to the Create action only - not the Edit function.

All comments

John Funk

Hi Becky,

Default values apply to the Create action only - not the Edit function.

Yong Yang

Hi John, could we set this field as mandatory so that the default value is always there regardless of Create/Edit actions? Maybe this is the solution. What do you think?

Thanks,

YY哥

John Funk

Yes, you could do that. But it won't affect issues that have already been created. It will only apply to next issues that created from that point forward.

John Funk

You could add a Field Required Validator to various points in your workflow - then the user would have to supply then to move the card forward for existing issues.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira

jira-data-center

data-center

default-value