You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have the same problem reported by https://confluence.atlassian.com/jirakb/requests-not-visible-in-the-jira-service-management-customer-portal-777026993.html, that is, when I change the issue type of a issue, the field request type is left empty (although only one request type is associated with the new issue type) and some fields cannot see by the customer.
As a solution I followed the Atlassian guide https://confluence.atlassian.com/jirakb/automatically-set-customer-request-type-when-issue-is-moved-or-created-via-jira-1026039858.html but when I try creating an issue as well as changing the issue type, the automated rule rises the following error: "The chosen request type doesn't exist in this issue's project. Check if the request type has been deleted from the project." See the following image with the rule and both errors.
Hello, to everyone who might stumble upon the same problem, I solved this by looking at the language configuration.
For my part, I had this error message because my project's default language was french but my user language was english. My initial request type was in french, but I created the automation in english, using the english translation of the request type. That is why the message said that the request type didn't exist in the project. It was looking for the french request type, and not for the english one, even though eveything seemed to be in english.