Resolve UX inconsistencies between AI features in the MR for GA release
Problem
Currently, the MR AI features "Fill in merge request template" and "Summarize code changes" are overlapped, and it could generate some confusion the way it is when release to GA.
Before we move these to GA, we need to find a way to integrate these features into our application following UX guidelines.
| MR creating page |
|---|
![]() |
Proposal
Actions that impact the content in the rich text editor should be directly in the toolbar.
- We could merge these 2 features together in the toolbar “Ai actions”
- When the user creates a merge request on push the merge request summary will be added to the description box automatically as a placeholder (using variables for templates)
Edited by Alex Fracazo
