The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow validators error message did not display when trying to import issues from csv

starrr
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2022

I set a workflow validator to verify if the customfield's value is null. What I expected is to display the error message I set when the workflow validator fails during csv import, but the result is a fixed NullPointerException. Is there any solution to display the error message when the workflow validator fails during csv import?

2022-08-12 11:09:05,059 ERROR - Fatal error during import
java.lang.NullPointerException
	at com.atlassian.jira.plugins.importer.imports.bulkcreate.engine.BulkCreateDataImporter.doImportIssues(BulkCreateDataImporter.java:235)

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 12, 2022

Hello @starrr,

Thank you for reaching out.

Indeed, the message received from the CSV import client when a specific field value is required from a validator or a field configuration is too vague. We created the following feature request to improve this message when importing issues from a CSV file:

Improve error message for issue creation via CSV import when there's a required field 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

That being said, I believe the message returned in your case is different from the one reported in the Feature request. Can you please confirm if that error only reproduces when you add a value to the custom field? 

Although the validator logic of your scenario and the one mentioned in the feature request should be the same, I see that your scenario is slightly different from the one described in the feature request (Field null x Field required), so I would like to confirm that the error message you are facing is strictly related to the validator or may relate to a different error in your CSV import, or even if the message difference is caused by the platform difference (Cloud vs Server).

Let us know if you have any questions.