java.lang.RuntimeException

Exception while trying to create a customField with the following parameters: CustomFieldMetadata[fieldName=sd.origin.customfield.default.name,fieldDescription=sd.origin.customfield.desc,fieldType=com.atlassian.servicedesk:vp-origin,fieldSearcher=com.atlassian.servicedesk:vp-origin-searcher,issueTypes={-1}]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web53835

  • via Atlassian JIRA by David Currie [Atlassian], 1 year ago
    Exception while trying to create a customField with the following parameters: CustomFieldMetadata[fieldName=sd.origin.customfield.default.name,fieldDescription=sd.origin.customfield.desc,fieldType=com.atlassian.servicedesk:vp-origin,fieldSearcher=com.atlassian.servicedesk:vp-origin-searcher,issueTypes={-1}]
  • via Atlassian JIRA by David Currie [Atlassian], 1 year ago
    Exception while trying to create a customField with the following parameters: CustomFieldMetadata[fieldName=sd.origin.customfield.default.name,fieldDescription=sd.origin.customfield.desc,fieldType=com.atlassian.servicedesk:vp-origin,fieldSearcher=com.atlassian.servicedesk:vp-origin-searcher,issueTypes={-1}]
  • via Atlassian JIRA by Bradley Baetz, 1 year ago
    Invalid parameters while trying to create new branch test1 for plan TEST-TEST. Error: branchName: [This name is already used in a branch or plan.]
  • Stack trace

    • java.lang.RuntimeException: Exception while trying to create a customField with the following parameters: CustomFieldMetadata[fieldName=sd.origin.customfield.default.name,fieldDescription=sd.origin.customfield.desc,fieldType=com.atlassian.servicedesk:vp-origin,fieldSearcher=com.atlassian.servicedesk:vp-origin-searcher,issueTypes={-1}] at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:66) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:32) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:60) at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160) at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79) at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:84) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:819) at com.atlassian.plugin.manager.DefaultPluginManager.scanForNewPlugins(DefaultPluginManager.java:523) at com.atlassian.plugin.manager.DefaultPluginManager.installPlugins(DefaultPluginManager.java:426) at com.atlassian.jira.plugin.JiraPluginManager.installPlugins(JiraPluginManager.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.