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; } } }

create linked issue creates "Invalid customer request value"

JJ_wwrfbp

When I create a linked issue (More>Create linked issue) from Service Desk and click "Create" the "Customer Request Type" field appears. In it it says, "No Match" and has an error message "Invalid customer request value".

I don't want users to have to set this value over and over. How do I get it to just copy the value from the original ticket I was looking at when I selected "Create linked issue" in the first place?

Accepted answers

All comments

Jack Brickey

Hi JJ, I was testing this in my cloud instances and in fact the request type is carried over. I assume the original issue has a request type? One more question, is the issue type the same for both?

JJ_wwrfbp

I'm not using the cloud version.

Thanks, Jack. I forgot to mention that I'm moving the ticket from one Service Desk project to another Service Desk project when I see the error. When I move to Jira Software I do not get the error message.

And, yes, the original issue does have a request type and when the create linked issue screen pops up I select an issue type. And I'm made sure that the issue type and request type of the original ticket exists in the project I'm creating the linked issue in too.

JJ_wwrfbp

Help. This bug makes it appear that users should NOT be creating linked issues or moving them since it's buggy. What's the solution?

unknown

I am facing the same problem (JSD 4.6.1, server). When I create an issue in Project A I can perfectly fine create an issue without setting the request type. But when I am viewing an issue in Project B and try to create a linked issue in Project A, I get the same error message. Both projects are JSD projects.

On another installation running JSD 4.7.1, data center, I do not have the problem.

Francisco Gomez Balastegui

Same error on Jira 4.20.14

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server

issue-link