Moving issue from one SD to another


I noticed that if you move an issue from one SD to another, the customer request type is set to "no match" even though we only use one request type for all our SD's which is mapped to the same issue type.

This is really irritating as it is easy to not notice this and customers wont get replies via mail or the portal if the customer request type is not filled in.

Is this a bug or am I doing something wrong?

1 answer

I am having strange "no match" problems within a single service desk.

I will come back and comment on this post if my search for a solution turns up anything useful.

Did you manage to get to the bottom of this? We are having the exact same issues now with "No match" being the default Customer request type.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

1,236 views 2 14
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you