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.

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

[John Funk · Accepted solution]

Hi Becky,

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

[YY Brother]

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. 

[Becky Yu]

Hello John Funk,

Thanks for your answer! I admit I was confused and didn't notice that it worked out with the create actions.

We sometimes use ScriptRunner Behavior to set default values on the edit screen - sorry I mixed them up