You have data in the field that the code cannot handle properly when it indexes the issue.
Go to the list of custom fields and work out which one is numbered 12000 (hover over "edit" and look at the urls which will tell you "id=12000" at some point).
Now go into the issue and edit it, blanking the field out or putting simple clean data in it.
Wow! @Nic Brough -Adaptavist- I learned something new. @Parsa goorani just has then 2 new problems. 1) has to be done manually over many issues. 2) the original values will be lost.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Parsa goorani ,
uuhh - to be honest, I recommend to contact Atlassian Support. Eventually something is broken in your DB.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Parsa goorani ,
in addition to Nic's excellent solution, I recommend following, because this can happen again and then it will cost time, again:
This will be all scripted, of cause. Can be reused later. If you need help, let us know.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.