Add functionality like git blame in Mia Merge Tool

[KarissaBrummell]

Which area of this project could be most improved?

Console

Description

We would like to request additional change metadata be surfaced within the native Mia Merge Tool to provide reviewers with better context during merge operations.

Today, the merge experience displays the configuration differences but does not indicate:

• Who made each change (author/user)
• When the change was made (timestamp)
• What the change was part of (revision name or change note)

As a result, engineers frequently have to leave the Merge Tool and manually search commit history to understand the changes they are reviewing. This slows deployments, increases cognitive load, and makes troubleshooting more difficult during code reviews and production incidents.

Requested Functionality: For each configuration change shown in the Merge Tool, display:

• Author (user who last modified the change)
• Timestamp of the change
• Associated commit message or change note

The metadata should be presented in a way that is easy to scan while reviewing changes.

Business Value: Providing this context directly within the Merge Tool would:

• Reduce the need to manually investigate commit history
• Speed up merge reviews and deployment workflows
• Improve reviewer confidence when evaluating changes
• Make it easier to understand the origin and intent of configuration changes during troubleshooting and incident response

This enhancement would significantly improve the day-to-day usability of the Merge Tool for teams managing configuration changes in Mia. Thank you all!

[albertotessarotto]

Thank you for sharing this feedback.
Bringing those metadata would be helpful to speedup and improve the review workflow.
We cannot commit on it at this moment, but we'll log it in our product backlog for consideration as we plan future evolution of the tool.
We appreciate your time for sharing your idea with us!