You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When using the plan configuration to look at build plan audit logs, or using the deploy project audit log, I'm curious why the timestamp displays without the year? Is there a reason for that? We have plans that have been in use for many years and it's hard to go back through the history when trying to troubleshoot errors.
That is indeed a good observation, thank you for pointing that out.
I've opened an improvement request to adjust this: https://jira.atlassian.com/browse/BAM-20753.
I'm assuming that you need this information now and you won't be able to wait for this improvement. With that in mind, I suggest you check the Bamboo audit_log table (as a workaround). That table holds the plans, deployment audit logs and more.
This is an example of a query that could be used in Postgres to get the plan related audit logs:
to_timestamp(TRUNC( CAST(msg_time_stamp AS bigint)/1000)) human_timestamp,
lower(entity_type) like lower('Plan')
and entity_id like 'PLAN-KEY'
order by msg_time_stamp desc
I hope that helps.
Thank you so much @Daniel Santos
The majority of our users don't have access to the audit_log table, so it will be great when the component can show the year. In the meantime, our system administrators have been helping me out.
Hopefully this is a quick and easy fix :)