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
We are using Service Management project for almost a year, but we encountering an error that I cannot resolve and now also cannot update my request type.
We are seeing this error when loading a settings page of the servicemanagement project:
On the details screen we see that the customer request type is causing the issue.
Also on the request type screen to edit the fields we see a error with that field. But we cannot change anything to get rid of the error. Also there is not a preset value for this field to be set:
Also I searched the custom field in settings, but cannot set a default value for it.
So, I'm out of options. The system needs this field, but doesnt let me set the default/preset value.
I'm trying to understand how the CRT was added to the request type form. The CRT is already defined by the Request type itself. So having it on the form within the RT itself is redundant and problematic. I assume this problem only exist on a single request type? Can you check other request types for the appearance of the CRT within the form? I'm missing something here and need to figure it out.
ok. what admin level are you? I wonder if you are a project admin and the associated screen scheme is shared with other projects. Can you look at the screen associated with the issuetype associated with the Maintenance Task request type? I suspect that the Request type field has been added to the screen and then added to the form. As an Org admin I can add to the screen then add/remove from the form. I also note that your image shows that the required box is checked. This is what ultimately is causing the misconfiguration. Do you have a hidden field that is required without a default value set. And as you noted you cannot set a default for it. So the solution is to get it off of your for all together. Now we just have to figure out how to make that happen. If you or not an organization admin you might want to reach out to this individual to discuss what you are experiencing.