Custom Fields Not Visible on Create Screen and CSV Import Mapping

Question

Issue Summary:

While performing a bulk CSV import in Jira, I am unable to map several custom fields because those fields are not available in the Import Mapping screen.

Investigation Done:

* Verified that the missing fields are created as Jira custom fields.
* Verified that the fields are associated with the project context.
* Verified that the fields are added to the project's screen configuration.
* Checked the Screen Scheme and Issue Type Screen Scheme mappings.
* Confirmed that the fields are available on the configured screen.

Observation:

The Jira CSV Import Mapping screen only displays fields that are available on the Issue Create screen.

The custom fields that are missing from the import mapping are also not appearing when manually creating a Jira issue, even though they are configured on the project's screen.

Expected Behavior:

* All configured custom fields should be visible on the Issue Create screen.
* The same fields should be available in the CSV Import Mapping screen.
* Users should be able to map CSV columns to those custom fields during bulk import.

Actual Behavior:

* Several custom fields are not visible on the Issue Create screen.
* The same fields are not available in the CSV Import Mapping screen.
* As a result, CSV data cannot be imported into those fields.

Impact:

Bulk issue import cannot be completed successfully because required custom field values cannot be mapped during import.

Request:

Please investigate why the configured custom fields are not appearing on the Issue Create screen despite being present in the screen configuration and verify whether any Field Configuration, Field Context, Issue Type, or Screen Scheme settings are preventing the fields from being displayed.

Trudy P Claspill · Answer

Hello @siddhesh B Lad

Be advised that this is a user community. We are users (and vendors and partners) with access to our own subscriptions to Atlassian products. We don't have access to the instance you are using. We cannot directly connect and investigate your issue.

We can ask you questions and offer advice to you about how to investigate the problem.

As @Germán Morales indicated there are up to three different screens that can be defined; one for each operation - Create, View, Edit.

When you add fields to the Field Configuration that does not automatically add them to the screens. You need to modify the actual screen used in the Create operation.

To identify which screen that is go to the Space Settings for the space into which you are trying to import the issues.

Expand Work Items and select Screens.

On the right you will see groups of issue types (1) associated with Screen Schemes (2). Click the expansion arrow (3) next to the screen scheme name to expand the list of operations and see the screen associated with each. In the example below I already did that for the second screen scheme that contains the Bug issue type.

You can click the screen name link for the Create operation to be taken directly to the configuration for that screen. And there you can add the missing fields.

Arkadiusz Wroblewski · Answer

Hello @siddhesh B Lad

@Germán Morales  is right about checking the Create screen. For any kind of Imports thats from where Field Configuration often comes from.

If the field is already on there but still missing, use Jira’s "Find your field" tool. Open a manual creation window, click the three dots at the top right, and search for the field. Jira will tell you exactly what's hiding it.

If that doesn't flag anything, it often means the field is set to "Hidden" in your Field Configuration, or its global context doesn't include this project and issue type.

Best,

Arkadiusz🤠

Germán Morales · Answer

Hi @siddhesh B Lad, you've checked almost everything; the part that usually hides this is the screen scheme itself. It doesn't hold one screen, it holds three, one each for Create, Edit and View. Whatever screen you verified the fields on is almost certainly the Edit or View one, and Create is pointing somewhere else.

Open Settings, Issues, Screen schemes, find the one your project uses, and look only at what's tied to Create issue. That's the screen that needs your fields. Two traps live right next to this: the issue type you're importing can resolve to a different screen scheme through the Issue Type Screen Scheme, and the field's context can be limited to issue types that don't include the one you're creating. Either one hides a field on Create while it sits perfectly happily on some other screen.

Sort out the Create screen for that issue type and the CSV importer sorts itself out, it only ever offers what Create offers.