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; } } }

Create Issue error referencing a custom field that was deleted

Wayne Grebe

I am getting the following error when I submit a Create Issue (Jira OnDemand);

Error creating issue: Unable to find field 'customfield_10313'

This custom field was deleted, but for some reason is still being referenced. My guess is that the error is related to a Post Function that was created using the Jira Suite Utilities plugin. I did not update the Post Function before deleting the field, assuming that all references to that field would be purged.

What do I do now?

Thanks in advance, Wayne

Accepted answers

Nic Brough -Adaptavist-

Oh, yuck, I hate it when I do that. The short answer is to manually edit the workflow and look at the create transition, removing any offending post-functions. It might also be happening in a listener, so you'll need to check those as well if you've configured any.

One quick cheat for workflows - if you download a suspect one to xml, you can do simple text searches on it to see where 10313 is in use, then go back into Jira and remove the functions referring to it - this can be quicker than reading every single post-function, condition and validator...

All comments

Nic Brough -Adaptavist-

Wayne Grebe

Ok, I just reviewed the XML and the Post Function is in it, but it is not visible via the workflow edit.

- <function type="class">

<arg name="field.value">Unresolved</arg>

<arg name="class.name">com.googlecode.jsu.workflow.function.UpdateIssueCustomFieldPostFunction</arg>

<arg name="field.name">customfield_10313</arg>

</function>

Wayne Grebe

Thanks Nic. I tried editing the post function, but the refernce to the custom filed is no longer displayed. I assume it's not visible because the custom field referenced in the Post Function has been deleted. yet I am still receiveing an error, as if the Post Function still exists.

Of course, all this is assuming that this is what's causing the problenm in the first place.

Nic Brough -Adaptavist-

Bother, I was afraid of that - Jira can't display the broken post-functions (and hence the options to edit/delete them).

You've got two options:

1. Create a new workflow and migrate the project over to use it

2. (This one is risky and really desperately needs you to take a solid database backup before you try it). Add a new field of the same type and name. Do NOT put it on any screens, or give it options or defaults. Stop Jira, use SQL to change the new field's ID to 10313. Restart Jira, edit the functions out of your workflows and then delete the new field.

Megan Makowieck

I just recently did this and was able to quickly fix it buy creating a new transition and deleting the problem one. A lot easier than having to recreate the workflow.

Nic Brough -Adaptavist-

Doesn't always work though - it depends on the whether the damaged transition is still coherent enough to be referenced by the editor.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud