Clarify outcome of "resolve threads in new issue" buttons in MRs
This is an actionable insight from the UX Department: MRs experience async critique research (insight).
What
The Resolve thread in new issue buttons in merge requests, present in multiple locations, are not clear in their outcomes:
- Will this button auto-resolve the unresolved threads?
- Does it create one issue for all threads? Or one issue for each thread?
Why
This lack of clarity makes users hesitate to use these buttons and difficult for users to understand what will happen.
How
Reword the button labels/tooltips to clarify the outcome of "resolve threads in new issue" buttons.
- From
Resolve all threads in new issuetoCreate issue to resolve all threads - From
Resolve this thread in a new issuetoCreate issue to resolve thread
Follow-up
Consider changing the terminology from unresolved thread to open thread:
- From
N unresolved threadstoN open threads - From
Unresolve threadtoRe-open thread - From
Jump to next unresolved threadtoJump to next open thread
Edited by Pedro Moreira da Silva


