Using a field in a form does not increment the project count in the custom fields list.

[Chris Garstin]

When I add fields to a form that is used in a Jira Service Management request type, the field does not appear to increment the "number of projects" column in the custom fields list in administration.

1. Create a new custom field. In the custom fields list it will show that no projects are using the field.

2. Create a form and add the custom field to the form.

3. Go back to the custom fields list in Jira administration. It will still not show that the custom field is being used in the project.

This is problematic since it risks a field being removed until the incorrect assumption that it is not being used.

Is anyone aware of a work-around?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Fields in forms are not issue fields, they are contained in the form.

[Chris Garstin]

You can link form fields to Jira fields in the back end. This creates a dependency. I appreciate that the logic to determine if this "is being used by a project" may be complicated, but effectively the field is now being used and should increment the counter.

If, for example, you use a field in a JSM portal request type without a form, it DOES reflect in the custom fields list. This shouldn't be any different.

[Nic Brough -Adaptavist-]

Yes, but the issue fields you link to are issue fields.  You can see those listed in the custom field list and check their context, but you'll also need to look at the screens and field configurations to see if they are actually presented to the users in the project.

The fields in a form are not issue fields and do not exist outside the form you have put them on.

[Chris Garstin]

Not sure how the point is being missed here.

I know that form fields are only present in the form.

I know that the linked fields are issues fields, separate from the form fields.

What I'm trying to say is IF you link a form field to an issue field, it should then indicate in the custom fields list that the field is now used in the given project. This would be the same as the existing behaviour where adding an issue field to a screen will result in the project showing on the custom fields list (because the field is in use).

Since it does not do this, it runs the risk of removing custom fields that look unused, but are actually linked to a form.