I have a suspicion the commas are getting in the way of things. I don't KNOW if his is the case because it looks like you pasted a screenshot of Excel in here (which is fine, just doesn't tell me if Splunk sees those fields with commas or without).
Best solution is to save the CSV without commas in it. It looks like your search should work after that.
A way to test this? We can use rex in sed mode to remove the commas and see what happens then.
source="biz_Case_test_3.csv"
| rex mode=sed field="Automated Test Coverage" "s/,//g"
| rex mode=sed field="Feature Delivery" "s/,//g"
| eval total_benefit = "Automated Test Coverage" + "Feature Delivery“
If that works OK, then we know it's the problem. The best solution is to resave the CSV and re-ingest it without commas, but the above could be used in a pinch. There is way to automate removing commas during the input/parsing phase to make this happen on that incoming data if you can't save the data without commas initially, but easier if we don't have to.
So the rex will look for what's between the first two / characters, and substitute what's between the second two globally.
s substitute
/,/ whenever you see a comma, replace it with
// nothing ( = empty)
g globally, which just means don't stop after the first replacement in one string but keep doing them all.
