#1: I can reproduce this, but only for custom fields. I’ll put this into bugs.
#2: Throughout the program, custom fields—whatever their format—are treated as information only. I would not expect a total, any more than I would for text, date, or image custom fields.
2# numbers in the summary screen are added. You can see the total at the bottom of the page. So it would be nice to have a total also in custom report.
What summary screen are you referring to? Whichever it is, that coding is built into the main program. There is no such coding built into a custom report. Standard number fields are added in reports because they are foreseeable. Custom fields are not.
I’m going to move this into ideas. Mostly because I’m working on yet another version of custom reports which incorporates a lot of feedback from current iteration. Hopefully the upcoming implementation of custom reports will be final one.