You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We began getting error "An internal server error occurred when requesting resource" for our Barchart gadget instances. Online conversation suggested doing a reindex, but that didn't help.
In the Jira log we found this error:
No custom field for customfield_13413. This should not happen. Data is likely to be corrupt.
However, custom field 13413 no longer existed -- if we went to configure a different custom field and then changed the URL to have 13413 instead, it was not found.
We queried the customfield table directly in the database and 13413 was still in that table, and we learned it was part of an unrelated plugin (Risk Register) which we had disabled. We re-enabled Risk Register and Barcharts started working again.
Is there any explanation for why Barcharts would require the presence of a custom field created by an unrelated plugin? Is there some action that can be taken to decouple it so that the other plugin can be disabled again?
You have already identified the problem. For a proper fix you can contact the vendor and they will surely recommend something.
Just out of curiosity what is the name of your custom field?
I suspect you might have to get rid of the entries directly in the database which is not always fun but since you are on server it is still doable.
It appears straight forward to me, but I might be missing something. The plugin created a custom field in it's own tables in the database, the Barchart gadget instances use that custom field but can't read it because Jira without that plugin enabled can't read the table for the plugin, and an error is produced.
The solution is to replace that custom field on all projects/screens/issues/filters/etc that use that field with a field that is available to Jira without the plugin installed. Cheers!