Yeah, I've run across this as well. One of the scripts I've built does a fair amount of logging that gets uploaded later into the policy log. The log entries have tabs for indenting in certain places in order to create some visual "grouping" of related log items. When I run the script in Terminal, even if using sudo jamf runScript -script "script.sh" -path /path/to/script/, etc, I see the formatting show correctly. But when run out of a policy, it gets ignored in the log that I view in the JSS, just as you stated.
TBH, earlier versions of Casper even ignored line breaks, which made for some seriously ugly logs in the JSS - long run on lines - so at this point, I'm glad to have proper line breaks and just live with the fact that it doesn't respect some of the special formatting I've put into my scripts. It would be great if JAMF could make it respect them, but its not a deal breaker for me personally.
