-
Suggestion
-
Resolution: Fixed
-
13
-
Hi all,
I'm excited to share that in Bitbucket Server 7.1 we shipped Push log feature that allows admins to see the history of all push events in a repository.
You can find more information in the Bitbucket Server 7.1 release notes and Push log docs.
Please, don't hesitate to leave feedback on the feature in the comments. This will help us to priorities further development.
Anton Genkin
Product Manager Bitbucket Server
Original message
As and administrator, I would like to be able to have push events moved to a higher priority so I do not have to set my audit log capture to low in order to get these events.
Since Git allows users to specify what they wish in their .gitconfig file for user name, it is at the Stash authentication level for push events that we consider the audit point for determining who is responsible for a set of changes. If you push it, even if you don't author it, you are considered the owner of the changes. The audit log feature for Stash does allow us to capture this information so we can tie the push of particular commits to the Stash authenticated user. The push events, however are classified as low priority so unless we are missing something, we need to set the audit log level to low. This would then capture many events that we are not interested in. From our standpoint and the need for more stringent audit trails, we feel that push events should be classified at more than a 'low' priority.
- is incorporated by
-
- Closed
-
- Closed
- is related to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[BSERV-4587] Increase priority of push events for Audit Log
Hi all,
Thank you so much for your votes and comments on this suggestion.
We are beginning greater research on the topic of advanced auditing and would love to hear from you.
We intend to better understand:
- What information you need to log and keep about your Atlassian applications and environments
- What are the questions you need to answer, or specific insights your are looking for when auditing logs
Responses can be in regard to recording product usage, information that needs to be tracked for internal policies (i.e. security) or compliance standards (i.e. SOC2 or SOX)
What’s involved in the research:
- Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.
- After scheduling, you'll receive a calendar invite with a video-conference link.
- During the research, we'll start with a general chat to get to know you and your company, then try to understand better your auditing needs and even explore some prototypes.
- As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 days of completing your session.
If you're interested in taking part, please send me an email at rbattaglin@atlassian.com
and I'll get in touch. We can't guarantee that all interested parties will be selected but we appreciate your interest in helping us to make auditing in our products satisfy more advanced use cases.
We look forward to meeting you!
Cheers,
Renan Battaglin
Server and Data Center Team
Please raise priority for both push/pull events, we've more than 50 teams requesting for it in our organisation
Thomas Ferrell
added a comment - Up voting this! I also would like to have more visibility into the actual person who pushed a set of commits.
Thomas Ferrell
added a comment - Up voting this! I also would like to have more visibility into the actual person who pushed a set of commits.
Hi all,
I'm excited to share that in Bitbucket Server 7.1 we shipped Push log feature that allows admins to see the history of all push events in a repository.
You can find more information in the Bitbucket Server 7.1 release notes and Push log docs.
Please, don't hesitate to leave feedback on the feature in the comments. This will help us to priorities further development.
Anton Genkin
Product Manager Bitbucket Server