Limit available jira fields when linking form fields to jira fields

[Philip Kroos - TEAM XALT]

Dear community,

I'm wondering if it's possible to limit the fields that can be selected when you configure a form and want to link a form field to a jira field:

The problem is that we are using over 1000 custom fields with very similar names and users sometimes map the wrong field in the form.

It is possible to select every field to be linked to, even fields that are not associated with the project where the form is configured.

Is there a way to limit the selection?

[Marc - Devoteam]

Hi @Philip Kroos - TEAM XALT 

there are no options to limit this, all available fields are shown.

What concerns me more is that you have over a 1000 custom fields and with the same name.

I would be more strict and have a naming convention or set multiple contexts on a custom field.

[Manoj Gangwar]

Hi @Philip Kroos - TEAM XALT 

You can link only one field at a time and the best resolution is to rename the fields with unique names by adding some prefix or suffix.

If there are multiple fields with a similar name then it causes lots of confusion also if you are using the fields in the automation rule then it will not work properly.