IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41282

Import Issues from CSV only works for choice fields that are configured for global issue types

      1. Create a custom field with a choice type. I tested with the Checkboxes and the Select List (single choice) type fields. I tested this issue with a Text Field type (multi line), and it didn't work.
      2. Set the field up to use only certain Issue Types. Just make sure that the type you choose also has the same type included in your CSV file. My field type utilized the Bug Issue Type. I tested with one, two, and three different types chosen at once. I reproduced each time.
      3. Have a CSV file with all the necessary fields to achieve an import cleanly. Just make sure there's a column for the custom field you just created.
      4. Map the fields.
      5. Instead of choosing the "Begin Import" button, you can choose "Validate".
      6. When you do, you should receive an error like this one:
        Cannot add custom field value: null
        The value [ {null=CustomValue} ] can't be added to the Custom Field [ CustomField ]. The value [ {null=CustomValue} ] can't be found or is in the incorrect format
        

      Workaround:
      Instead of choosing an Issue Type for the field configuration scheme when you configure the field, choose "Any issue type".

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-41282

            Import Issues from CSV only works for choice fields that are configured for global issue types

                1. Create a custom field with a choice type. I tested with the Checkboxes and the Select List (single choice) type fields. I tested this issue with a Text Field type (multi line), and it didn't work.
                2. Set the field up to use only certain Issue Types. Just make sure that the type you choose also has the same type included in your CSV file. My field type utilized the Bug Issue Type. I tested with one, two, and three different types chosen at once. I reproduced each time.
                3. Have a CSV file with all the necessary fields to achieve an import cleanly. Just make sure there's a column for the custom field you just created.
                4. Map the fields.
                5. Instead of choosing the "Begin Import" button, you can choose "Validate".
                6. When you do, you should receive an error like this one:
                  Cannot add custom field value: null
                  The value [ {null=CustomValue} ] can't be added to the Custom Field [ CustomField ]. The value [ {null=CustomValue} ] can't be found or is in the incorrect format
                  

                Workaround:
                Instead of choosing an Issue Type for the field configuration scheme when you configure the field, choose "Any issue type".

                        Unassigned Unassigned
                        kgrier kitkat (Inactive)
                        Votes:
                        58 Vote for this issue
                        Watchers:
                        42 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            kgrier kitkat (Inactive)
                            Affected customers:
                            58 This affects my team
                            Watchers:
                            42 Start watching this issue

                              Created:
                              Updated: