Creating a Service Management fails with error: Time to resolution field is not a valid number
Symptoms
- Creating a Service Management or trying to enable an existing project as a Service Management project fails with error
- The following or similar trace appears in the
atlassian-greenhopper.log:
2015-02-03 23:24:17,245 | WARN | ajp-bio-8080-exec-15 | admin | 1404x16591x1 | 1k25a55 | 10.128.68.195 | /rest/servicedesk/1/servicedesk | [internal.feature.gettingstarted.GettingStartedQueueCreationService]| Error with validation when creating default queue: 'com.atlassian.servicedesk.internal.feature.queue.QueueValidationFailure' with [FieldError(jql,Value '30m' for the 'Time to resolution' field is not a valid number.)] |
2015-02-03 23:24:17,250 | ERROR | ajp-bio-8080-exec-15 | admin | 1404x16591x1 | 1k25a55 | 10.128.68.195 | /rest/servicedesk/1/servicedesk | [common.error.jersey.ThrowableExceptionMapper]| Uncaught exception thrown by REST service: None.get |
java.util.NoSuchElementException: None.get
at scala.None$.get(Option.scala:313)
at scala.None$.get(Option.scala:311)
at com.atlassian.servicedesk.internal.feature.gettingstarted.GettingStartedReportCreationService.createDefaultReports(GettingStartedReportCreationService.scala:36)Cause
There is an existing custom field 'Time to resolution' of a type different from that created by Service Management.
Resolution
Rename the custom 'Time to resolution' customfield. (To differentiate this from the 'Time to resolution' field created by Service Management, that of Servicedesk would usually be locked, and of type SLA Customfield).
Last modified on Nov 23, 2020
Powered by Confluence and Scroll Viewport.