nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a workaround for inability to create or edit tickets after upgrading to JIRA 6.0?

bmamlin

We just upgraded from JIRA 5.2 to JIRA 6.0 and now any attempt to create or edit a ticket fails with this exception:

java.lang.ClassCastException: com.atlassian.jira.user.BridgedDirectoryUser cannot be cast to java.lang.String

Any ideas of how to fix or troubleshoot this error? We've created a support request, but thinking someone might have an idea here as well.

UPDATE:

Looking at the first part of the stacktrace:

java.lang.ClassCastException: com.atlassian.jira.user.BridgedDirectoryUser cannot be cast to java.lang.String
	at com.atlassian.jira.issue.customfields.impl.MultiUserCFType.putInvalidUsersAtFront(MultiUserCFType.java:291)
	at com.atlassian.jira.issue.customfields.impl.MultiUserCFType.getStringValueFromCustomFieldParams(MultiUserCFType.java:201)
	at com.atlassian.jira.issue.customfields.CustomFieldUtils.buildParams(CustomFieldUtils.java:382)
	at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.getEditHtml(CustomFieldTypeModuleDescriptorImpl.java:157)
	at com.atlassian.jira.issue.fields.CustomFieldImpl.getEditHtml(CustomFieldImpl.java:975)
	at com.atlassian.jira.issue.fields.screen.AbstractFieldScreenLayoutItem.getEditHtml(AbstractFieldScreenLayoutItem.java:78)
	at com.atlassian.jira.issue.fields.screen.FieldScreenRenderLayoutItemImpl.getEditHtml(FieldScreenRenderLayoutItemImpl.java:62)
	at com.atlassian.jira.issue.fields.rest.FieldHtmlFactoryImpl.getEditFields(FieldHtmlFactoryImpl.java:151)

It looks like this error has something to do with custom fields and/or invalid users. The only other hit other than this question when Googling BridgedDirectoryUser is JRA-32514, which states that a multi-user custom field (in JRA-32514 it's a "Participant" custom field) is the cause of the problem... but we don't have a multi-user custom field. :-/

Still searching for an answer.

Accepted answers

Ramiro P

Hi Burke, just in case have you tried disabling all the plugins? Sometimes when you do an upgrade plugins aren't compatible with the new version and may cause this.

All comments

Ramiro P

Hi Burke, just in case have you tried disabling all the plugins? Sometimes when you do an upgrade plugins aren't compatible with the new version and may cause this.

Harry Chan5

Besides disabling plugins, have you tried a re-index? Have you tried the integrity checker?

bmamlin

Bingo! We don't really use any plugins besides Greenhopper, but looking back I discovered a Watcher plugin that I thought had come distributed with JIRA, but appears to be a remnant from earlier. Disabling that plugin & re-indexing did the trick. Thanks!

bmamlin

Thanks. I first tried re-indexing and it failed with the same exception. Then I realized the watcher plugin was a remnant, disabled it, went back & re-ran the index and it succeeded. It looks like things are working now. Thanks!

Norbert

I have the same problem, which plugin did you disable?

Jim Birch

In our case it was the Watcher field plugin (which allow watchers to be added on the issues create/edit page). There is a new version that resolves my problem, try updating any plugins first, then go to support.

Norbert

Thanks

Meanwhile I disabled all plugins -> everything was ok
then I enabled it one after another!

I also used the watcher field plugin, but I'm pretty sure I updated it before updating to jira 6!

Nic Brough -Adaptavist-

The watcher field plugin is mentioned several times above, and it's the one that caused it for us when I was testing an upgrade. Start with that one. It's possible it could be caused by others though, so you may want to work through any other plugins you've got in your system.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

user-directory