Subissues
Description
- Subissues, similar to related issues #2001 (closed).
- Re-design the visual design so that it is consistent with the rest of the issue page.
- Buttons to add a related issue and a subissue.
- Button to add a blocking issue for the future (not in scope).
- Move the combo box of the
Create a merge request
inline with the other buttons. - The Related issues and Subissues section are displayed only when there is at least one of them.
- In the mockup, there are no related issues, so the section is not shown.
- When you click one of the
Add
buttons, the associated section appears (if not already appearing), and the mouse cursor goes to the empty box. - The only way to add a subissue is pasting it in the box.
- Note that there is no way to view parent issues in the UI.
- If you have permissions to edit both Issue A and Issue B, then you can make A a subissue of B or B subissue of A. If you don't have permissions to edit both, either of these actions will not be allowed.
- If you add the same subissue, nothing happens. (Same as #2001 (closed).)
- You are allowed to make A a parent of B and B a parent of A. There is nothing preventing this. So you can have a circular loop. That is fine.
- When you add A as a subissue to B, then on B, there is a system note that says:
Victor Wu @victorwu added A as a subissue 2 mins ago.
- Note that there is no system note on A.
- When you remove A as a subissue from B, then on B, there is a system note that says:
Victor Wu @victorwu removed A as subissue 2 mins ago.
- Note that there is no system note on A.
- When all the subissues of a parent issue are closed, the parent issue is automatically closed.
- In this mockup, there is one related issue.
Related merge requests and branches
This design can be extended to include related merge requests and related branches in an issue. Furthermore, we may want to explore tabs, i.e. https://gitlab.com/gitlab-org/gitlab-ee/issues/2036#note_35978406
Edited by Victor Wu