Stop attributing system events to users in merge requests
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
In the MRs, for some actions that are performed by the system, such as drop/cancel an MR from a train, are attributed to users. This leaves the users misinformed and in most instances very confused and thinking what did they do to make the train drop the MR. This is one event that I as an author of this issue am aware of, there might be more.
Screenshot from a gitaly MR: gitaly!2680 (merged)
Intended users
All personas interacting with MRs would be affected.
User experience goal
The activity log should correctly communicate to users if an event was performed by the system.
Proposal
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Free
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Yes, with grouppipeline execution.
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.