Merge request list row design
Problem and proposal
- We are working to harmonize and give intentional designs for how issues, mrs, and epics are viewed in various places. This includes lists views (including related list views and board cards). The design work has been done in gitlab-design#83 (closed).
- This issue is to implement the designs as applicable to merge request lists, for the project lists and the group lists.
Description
- The label collapsing behavior is out of scope. Labels are always expanded.
- Implement designs from gitlab-design#83 (closed) for all project MR lists, group MR lists, and dashboard MR lists.
- Breakpoint
>1200px
- Breakpoint
>992px
- Breakpoint
>768px
- Breakpoint
>0px
- Items, states, and tooltips
-
☝ Note that the issue list design spec has multiple implementation notes that also apply to other states and designs.
- Breakpoint
- The list layout acts like a table. If there is no milestone or due date or assignee, the column is not shown. If a field is present on one of the MRs, but not on another, it should be shown as “empty”.
- Information to display:
- Status (open/merged/closed)
- We've changed the closed merge request status icon: a circle with a dash. We also need to change this icon in the mobile view of a merge request detail page. We believe this is the only additional place to change the icon but we should search the codebase for any other instances.
- The “open merge request” icon only appears in the “All” tab. The “closed merge request” and “merged” icons appear in the “Closed“, “Merged”, and “All” tabs.
- Title (link to the MR)
- Target branch
- Path and ID
- Created timestamp
- Author
- Updated timestamp
- Upvotes
- Comments
- Labels (ignore the collapsed styling in the mock-up, the labels always appear expanded)
- Milestone
- Estimate
- Assignee
- Health: items left to allow merge AND pipeline status
- Status (open/merged/closed)
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.
Edited by 🤖 GitLab Bot 🤖