Details
-
Bug
-
Resolution: Fixed
-
Low
-
3.13
-
3.13
-
Description
UserCFType returns a User object, but the value doesn't map to a JIRA user. You get the following fairly regularly in the logs:
2008-08-15 14:42:07,580 http-8090-Processor4 WARN [issue.customfields.impl.AbstractSingleFieldType] Value stored in database is invalid com.atlassian.jira.issue.customfields.impl.FieldValidationException: User 'betty' was not found in the system at com.atlassian.jira.issue.customfields.converters.UserConverter.getUser(UserConverter.java:41) at com.atlassian.jira.issue.customfields.impl.UserCFType.getSingularObjectFromString(UserCFType.java:59) at com.atlassian.jira.issue.customfields.impl.StringCFType.getObjectFromDbValue(StringCFType.java:25) at com.atlassian.jira.issue.customfields.impl.AbstractSingleFieldType.getValueFromIssue(AbstractSingleFieldType.java:87) at com.atlassian.jira.issue.fields.CustomFieldImpl.getValue(CustomFieldImpl.java:266) at com.atlassian.jira.issue.index.indexers.impl.DefaultCustomFieldIndexer.addIndex(DefaultCustomFieldIndexer.java:50) ...
Attachments
Issue Links
- is duplicated by
-
JRASERVER-17260 FieldValidationException: Not a valid URL should not log stack trace and should log offending issue
- Closed
- is related to
-
JRASERVER-15430 The User Custom Field should handle users being deleted.
- Closed