Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,383
Community Members
 
Community Events
176
Community Groups

Multi-Level Cascading Select - CSV import throws an exception

We are trialing the Multi-Level Cascading Select plugin, and when importing options, the plugin throws an exception. Our CSV is structured as per the example. In the "Confirm to proceed with the import", all options are correct, so the CSV seems to have been read in correctly.

However, when clicking Import, the following exception is thrown. Some of the options from the CSV are imported correctly, but the majority are missing:

java.lang.NullPointerException
java.lang.NullPointerException
	at com.sourcesense.jira.plugin.webwork.ImportOptionsFromCsvAction.handleImportedValue(ImportOptionsFromCsvAction.java:183) [?:?]
	at com.sourcesense.jira.plugin.webwork.ImportOptionsFromCsvAction.doImportOptionsConfirm(ImportOptionsFromCsvAction.java:154) [?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_102]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_102]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_102]
	at java.lang.reflect.Method.invoke(Method.java:498) [?:1.8.0_102]

Any ideas about what may be going wrong?

2 answers

1 accepted

0 votes
Answer accepted

 

Hi @samilempinen we are happy to give you help.

We would need the following information:

- Version of Jira;

- Version of the MLCS plugin;

- Current MLCS configuration;

- The CSV file you are trying to import;

- Have you tried reindexing?

We are waiting for feedback.

 

 

Best regards

- Jira Server is at 7.10.2,

- MLCS is at 5.0.5,

- What do you mean by MLCS configuration?

 

The CSV is confidential, so I would need to mock the data somehow. I will try reindexing next.

Hi @samilempinen ,

Thanks for this informations.

Could you create a support ticket for this problem?

We will be happy to help you.

We would need an example of configuration for check if there is any particular character that blocks the import process.

 

We are waiting for the ticket so we can proceed to the resolution of the problem.

 

Best regards

Thanks for your kind offer!

However, I was able to troubleshoot this myself. I opened the offending data CSV and found that some entries contained dual separators (i.e. holes in the data), such as

Level1;Level2;;Level4

I fixed those and the import was successful.

If anything, the error message could be a little more informative. Thanks! 

Hi @samilempinen 

We are happy that you have solved the problem.
In the next releases we will review the error messages during the check CSV file.

 

Thank you

Rob Horan Community Leader Sep 30, 2019

HI @Gianluca Cristiano ,

I have had problems importing a CSV to populate a multi-level select list. I got 500 errors immediately,  every time.

I also have an unrelated question about this plugin, posted elsewhere - IF you have a moment :)

I'm having summary field mapping error, which I don't know how to map the summary field. Can anyone help me fixing this issue? @Gianluca Cristiano 

This is because of the bugs they have in older version and it got resolved in app update. 

Thanks. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events