Custom Field Number Defaulting value '0'

[Brad]

I created a custom field (number) and added it to Service Desk screen as mandatory. It defaults the value of '0' even though I have no default value set. Doesn't make sense to have a mandatory field I want the users to fill out when the system fills it out for me?

[Carlos Henrique Ughini]

Hello,

Thank you for reaching out to Atlassian Community!

Firstly, it would be nice if you could go to the custom field configurations and check if you set the default value in the appropriate context.

If you don't know how to go there, you can follow these steps:

1. Navigate to the Custom Fields page, locate the desired custom field and choose cog icon > Configure.
2. Locate the relevant context (there will usually only be one, named 'Default Configuration Scheme for ...') and click the Edit Default Value link in the right-hand column. The 'Set Custom Field Defaults' page will be displayed and will be particular to the custom field type.

Besides that, you can add a new context that allows you to configure a custom field differently for different combinations of issue types and projects.

To add a new context, please follow these steps:

1. Navigate to the Custom Fields page, locate the desired custom field and choose cog icon > Configure.
2. Click the Add new context link. The 'Add configuration scheme context' page will be displayed (see below).
   
   • Under 'Add configuration scheme context', enter a 'Label' and 'Description' for your new context — these are used for administrative purposes only and will not be shown to your end-users.
   • Under 'Choose applicable issue types', select the issue type(s) to which you want the default value and options to apply. You can select Any issue types if you wish.
   • Under 'Choose applicable contexts', select the project(s) to which you want the default value and options to apply. Note that this will apply to only issues with the selected issue type(s) as above.

It is important to know that a custom field can only have one context per JIRA project. So you cannot have multiple contexts for different issue types in the same project.

In addition to this, if you're interested in knowing more about configuring a custom field, we have a public documentation that contains more information about it!

• Configuring a custom field

We really hope this information helps you.

Best regards,
Carlos

[Brad]

Hey Carlos, appreciate your reply, from my previous comment and this attached picture you can see there is no value set for the default value. I don't want anything in this field so it requires the user to fill out when it gets to the relevant screen. The problem is that it is defaulting a value, so the user is never forced to enter one in. I need this value cleared so that the user had to put something in.

As for the context, I prefer it to be this way across all types and projects, so not sure adding a new context would help any?

[Brad]

Also, I'm trying to do this without buying any plugins, I know I can accomplish this task with the JSU Suite Utilities, but we've had issues in the past upgrading Jira / Confluence and these plugins no longer working. It also seems like this is a bug versus a feature. We are on version: 3.15.3

Let me know - thanks!

[Brad]

So I found where it was defaulting to '0' - I guess at some point when we made the Custom Field required globally (Field configurations) it automatically added it to each request type. The field was hidden since we couldn't figure out how remove (b/c it was required we know now), but when hidden it requires a default value on the Request types. I had to make the Custom Field optional in Field configurations, remove from the Field type.

There's still no way to make this required that I see without using a plugin, which stinks. The problem is for Service Desk tickets that come in from Email requests and not the Portal. It won't bring the ticket in from email if the field is required and not filled out, which how can you in email??? I need a validator to make this field required after it comes in during workflow change, but only plugins accomplish this.

I'll have to keep trying... thanks again