Log timestamps should be in UTC, regardless of the server/user location. This keeps the data consistent.
If a user in the US has logs which show 2020-12-01 13:25:42 and a user in the UK sees the same logs as 2020-12-01 18:25:42, that's a huge problem. Regardless of who is viewing a log or where they're located, the log should contain the same data. And by convention, the time should always be in UTC.
If you've ever had to deal with servers configured to a local timezone which uses daylight savings, you understand this need.
Setting the TZ to the server's timezone is confusing and setting the TZ to each user's local TZ is inconsistent. UTC is the industry standard, it should be used.
Patrick,
I agree that log timestamps should be in UTC.
For me this is more about metadata and the ability for bamboo UI to show dates/times of builds, deployments etc in a user defined timezone. They all should still be stored in UTC but frontend should be able to convert them to user's TZ. It can stay as UTC if user wants.
If timestamps are displayed with the timezone then there is no confusion. A user in the US East would see 2020-12-01 13:25:42 (EST) and someone it the UK 2020-12-0118:25:42 (GMT)
TBH I doubt it will ever be implemented considering the age of this ticket and Atlassian's last year announcement about its focus on cloud services.