The service desk side will not allow multiple selections, only if a single option is chosen. Changing these works in the non-service desk view of the same field. Is anyone aware of this issue and/or a specific workaround for it? There are no " Field has single value Validator " validators in this workflow. Browser: Google Chrome

Yep, definitely been doing that in parallel, wanted to check here to make sure we weren't overlooking anything too obvious

Well, I'm stumped. I think you may have to call in the big guns and actually open a support ticket with Atlassian to take a closer look at your logs and and browser logs.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Service Desk "multiselect" Custom Field does not allow multiple selections

msheffey

The service desk side will not allow multiple selections, only if a single option is chosen.
Changing these works in the non-service desk view of the same field.

2020_05_20_16_23_33_Service_Desk -.png

Is anyone aware of this issue and/or a specific workaround for it?

There are no " Field has single value Validator " validators in this workflow.

Browser: Google Chrome

Accepted answers

All comments

Nic Brough -Adaptavist-

The browser is irrelevant, the question is what you have added to the transition to validate the field content. Could you explain what you have done there?

msheffey

I added browser there because some other questions posted in this community get asked that. Example: https://community.atlassian.com/t5/Jira-questions/Checkboxes-problem-I-can-t-select-multiple-options-on-JIRA/qaq-p/1152269

We don't have any validations for that custom field on transition. Worth mentioning this is happening for any multiselect fields in our service desk, not specifically that field.

msheffey

We don't have any validations for that custom field on transition. Worth mentioning this is happening for any multiselect fields in our service desk, not specifically that field.

msheffey

This may help as well. We see this on the console on page load (and we don't see this on request types where we don't have multiselects.

image (5).png

Nic Brough -Adaptavist-

You are not looking at the right thing. You need to look at the validators or code that you have put in that is generating that "please provide a valid value"

Harshil gupta_r2m4q2

Can you look at the field configuration and check if those fields are made mandatory there. Also check if any scriptrunnr behaviour has been created for the project where these fields have been made mandatory

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

custom-field

jira-service-desk

jira-service-desk-server

multi-select