Master Row : 1, Sheet Name : Test Cases, errorMessage : Error while creating issue : errors":{}}]

[Nerusu Hemanjali]

Facing above error while improting issues.Unable to understand what caused the error

[Niranjan]

Hi @Nerusu Hemanjali 

You may need to check the Zephyr log for more information. There could be different reasons like validators on the workflow, excel issue.

Check if there are any mandatory fields for test issue type creation. If so make them optional and try the import again

[Nerusu Hemanjali]

Hi Niranjan

Can you mention steps how to make mandatory fields optional

[Niranjan]

Hi,

Try to create a test issue type manually and identify the required fields. You can make them option in the field configuration. Also check the workflow of the test issue type. If you any validators (fields required), remove them and try again.

[Nerusu Hemanjali]

I tried manual part also. The below issue popped up when I tried with/without fix version  field in configure field

Affects versions: Affects versions is required.

[Niranjan]

There is another system field called "Affects Version/s" in JIRA. It seems that field is mandatory in your project. You can try making it optional in your field configuration or you can add it to your issue type create screen

[Nerusu Hemanjali]

I dont see affect version in configure field only fix version is present.

[Niranjan]

Kindly check again. It is "Affects Version/s". It is a system field and will be available on all JIRA instances. Check if your workflow. If there is a validator in your create issue transition where this field is made required.

[Nerusu Hemanjali]

I can see only these field.kindly can you send the shots where i can check the affect version field.In our workflow I dont see that affect version is given mandatory

[Niranjan]

Hi,

In your project summary page, you will have "Field configuration" under a Field configuration scheme. You should look at the field configuration if the field is mandatory. If so, kindly make it optional and try again. The screenshot that you have will show the fields that are available on the screen. 

[Nerusu Hemanjali]

Hi niranjan,

Thanks for the help as field configuration is only being to operable for administrators I was not able to operate all configurations.Thanks for support

[Niranjan]

OK. You may need to reach out to your jira-admin and get this sorted

[Sergiy Mokriev]

Please explain why I cannot have the fields required and importable at the same time?

[Nic Brough -Adaptavist-]

You can have fields required and importable.  You just need to provide data for every issue being imported in a required field.  Because it is required.

[Sergiy Mokriev]

Hi Nic, thank you for the response. Actually from the above conversation I understood that the fields should be optional to be imported. Nevertheless I face the problem with the importer - I'm importing the test case from the excel and get the error that Account is required regardless that it is definitely set in Excel. Let me show you some screenshots:

1. The excel file 

2. The mapping

3. The result I get once the Import button is clicked

As you can see the Account exists in all the rows of the excel file, but for some reason Importer doesn't see them. And hence according to the above conversation I decided that the fields should be optional to have ability to import them.

Could you please provide any ideas how this problem can be fixed?