-
Suggestion
-
Resolution: Fixed
-
None
Problem
It is very common that deployments and plans last for more than a year. When that happens it becomes hard (some times impossible)to determine in which year the logs message was generated if you just use the Bamboo UI.
Suggested solution
Add the year part of the timestamp in the UI.
Workaround
Get this information from the audit_log table.
[BAM-20753] Timestamps in audit logs entries should show the year
Fix Version/s | Original: 6.10.5 [ 90700 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
Fix Version/s | New: 7.0.0 [ 89610 ] | |
Fix Version/s | New: 6.10.5 [ 90700 ] |
Remote Link |
New:
This issue links to "+core+ Dogfooding › Test Git Branch Detection › feature- |
Status | Original: Gathering Interest [ 11772 ] | New: In Progress [ 3 ] |
Assignee | New: Marcin Gardias [ mgardias ] |
Description |
Original:
h3. Problem
It is very common that deployments and plans last for more than a year. When that happens it becomes hard (some times impossible)to determine in which year the logs message was generated if you just use the Bamboo UI. h3. Suggested solution Add the year part of the timestamp in the UI. |
New:
h3. Problem
It is very common that deployments and plans last for more than a year. When that happens it becomes hard (some times impossible)to determine in which year the logs message was generated if you just use the Bamboo UI. h3. Suggested solution Add the year part of the timestamp in the UI. h3. Workaround Get this information from the *audit_log* table. |
We only have about 10 people with access to the Bamboo audit logs and over 4,000 people who depend on using the audit log within the build plan to see their changes. While troubleshooting, being able to see when a plan was created and how long ago the most recent changes were made is a very helpful tool. We have plans that are more than 5 year old and trying to figure out the audit log is quite a mystery.
Thanks!
Miranda