Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

"customer request type" field throwing error

Poornima Rajamani
Poornima Rajamani Sep 20, 2023

Scenario: After a ticket received, wanted to move the ticket to another category, facing issue on "customer request type".

currently, after moving the ticket from one category to other, though it is saved. we see the "customer request type" having error as shown in the attachement.

example: moved the "incident" to "support" ticket but it did not change as expected.

it is not automatically changing, we are forced to change it manually from the dropdown.

Please let me know how to correct itjira ticket for request type error.png

Answer
Watch
Like Be the first to like this
100 views

1 answer

0 votes
Joseph Chung Yin
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Sep 20, 2023

@Poornima Rajamani -

Welcome to the community.  When you move an issue from one issue type to another issue type, then the original data associated with the issue get carried over.  

In this case, you don't have the request type defined for the target issue type properly, thus it displayed the problem.  You can address it by creating a valid request type for the targeted issue type to resolve the problem.

What is the request type that you have to use when conducting the manual process?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events

See all events