Multi level cascade field

[Холбоева Ирина]

Hi! Can't add second level to the Multi level cascade field after update version of Jira.
When you click on the "configure" button in the first level of the field, an error appears. 

And the page is called "Invalid Custom Field".  

What could be the problem and how to solve it?

[Emanuele Picariello]

Hi @Холбоева Ирина,

Are you using the last version of the MLCS plugin?

What version of Jira are you using?

This problem was resolved with the last release version.

If you still encounter problems regarding the plugin.

Please contact the support.

https://marketplace.atlassian.com/apps/5008/multi-level-cascading-select?hosting=server&tab=support

Regard,

Emanuele Picariello

[Prepev Yura]

Hi @Emanuele Picariello 
Version of Jira - v8.13.7
Version of the MLCS plugin - 6.0.16

[Emanuele Picariello]

Hi @Prepev Yura

Could you send me your URL while you are clicking on the link Configure?

Also, I suggest you open a ticket to our support https://marketplace.atlassian.com/apps/5008/multi-level-cascading-select?hosting=server&tab=support

Regards,

Emanuele Picariello

[Prepev Yura]

@Emanuele Picariello 

/secure/admin/ConfigureMultiLevelCascadingSelectOptions!default.jspa?atl_token=_lin&fieldConfigId=62812&customFieldId=52222&parentOptionId=113225

[Emanuele Picariello]

Hi @Prepev Yura @Холбоева Ирина

Could you use this version and let me know if the error still appears?

I have uploaded it on this ticket:

https://sourcesense.atlassian.net/browse/MLCS-669

Regards,

Emanuele Picariello

[aas]

Hi @Emanuele Picariello I have the same problem

Getting ERROR! =[

here's the URL
https://base_url/secure/admin/ConfigureMultiLevelCascadingSelectOptions!default.jspa?atl_token=_lin&fieldConfigId=21310&customFieldId=19220&parentOptionId=136224

In atlassian-jira.log I have error

STA PER PARTIRE l'errore

VALUE: 36224

But if I try to configure another option with url

https://base_url/secure/admin/ConfigureMultiLevelCascadingSelectOptions!default.jspa?atl_token=_lin&fieldConfigId=21310&customFieldId=19220&parentOptionId=111924

Everything is fine

I suppose that velocity multi-level-cascading-select-admin-options.vm gets the query string from url I posted above and tries to get parentOptionId but in first case calculates fails, in second everything is ok, but why?

jira version      - v8.13.27

plugin version - 6.1.0