cascading database select lists in service desk

[Arianna Fabbri]

 last version of kepler plugin is able to render cascading database select lists in service desk customer portal??

thank you

[Maria Cirtog]

Hello Arianna,

The last version of the database custom field plugin supports the rendering of database custom fields as select lists in the Service Desk portal.

However, in Service Desk portal the database custom fields are rendered as single select lists with autocomplete, no matter the configuration of the field from Kepler parameters. Also the dynamic fields are limited, there are supported the fields of the form customfield_xxxxx present in the screen and from the system fields only currentuser is supported for now.

Regards,

Maria

[launay sebastien]

Hello Maria,

I see your comment regarding the new version of Database Custom Field.

I currently facing a problem using the Database Customer Field version v. 3.0.11 with JSD 2.5.9 version and

JIRA  core 6.4.7.

The single select lists return nothing using the the Service Desk portal during issue creation, however in the agent view this is working.

is it possible that you provide to us the version of DB Custom Field which Take in account eh Servuce Desk Portal?

Thanks in advance for your reply

[Arianna Fabbri]

Hi @Ben De Pauw,

thank you for your support.

I tried and it works.

What is not still working is the multiselect on the last cascading list. This on the customer portal of service desk is shown as single value select list even if in Kepler database custom field configuration I have selected "allow multiple values".

Any ideas?

Thank you

Arianna Fabbri

[BenP]

Hi Arianna, 

Yes, this is possible by using multiple DBCF custom fields (not the child fields), pulling their select list data from jiradb / external DBs. You can use the value of one dbcf customfield in the WHERE clause of the next custom field, implementing cascade functionality. 

I think there is (still) a limitation that all the fields need to be present on the same screen, for the inter-field dependencies to work.

See "What types of custom field are supported" on Dynamic Query (SQL) for documentation & samples.

Let me know if you need any additional help with this. 

Good luck,

Ben

[RVal]

Did you mean Kepler Database Custom Field? Can you elaborate what you mean by cascading select? Do you want to have multiple select lists where choice in first select defines options available in second select ?

As far as I know DB Custom Field only supports one child field where it copies result of selection or autocomplete from the original DB Custom Field.

I have plugin version 3.0.1