Extended Field Values that are nil produce an error
If an extended field is not used by a tracker but is enabled in the issue overview, then an error is produced because the value of that field is nil
I appended a possible patch as file
#2 Updated by Alexander Kuznecov almost 5 years ago
Ivo, thanks for patch!
I have faced with same issue - got problem on custom queries with displayed columns that had nil value
Works for me on 2.6.0
For all people faced same problem - patch provided by Ivo is for code from SVN, not from download link