Reword "blocking merge requests" to "merge request dependencies" and consider intra-project use case
Problem to solve
Blocking merge requests or specify merge request order/dependencies is a major step towards supporting cross project merge requests. We should make sure that this use case is supported clearly.
Proposal
UX refinement
- Rename the feature to: Cross-project Merge Request Dependencies
- Rename the field label to: Cross-project dependencies
- Rename the field placeholder to:
Enter merge request URLs or references (e.g. path/to/project!merge_request_id)
- Add help copy below the field:
List merge requests from other projects that must be merged before this one may be merged.
Behavior
The primary motivation for this feature is to allow cross-project merge requests, do we need to allow merge request dependencies within the same project? And could this in fact create workflow problems by encouraging people to chain merge requests after each other?
Edited by Pedro Moreira da Silva