[馃帹 Design] MVC 1 - Child issues from a different hierarchy
馃敭 Context
MVC one scope as defined in the epic:
- From within an epic, paste a URL for an issue in another group that you have access to make it a child.
- We shouldn't worry about searching/autocomplete. There could be performance concerns with this workflow and customer feedback is that this is not their preferred path to create parent/child relationships.
- For this initial iteration, we don't need to worry about adding epics from another group but we will want to fast follow with this.
- Most of the focus for this MVC will be to figure out how to present
User doesn't have permission to view other group's epic
to the user in a way that is meaningful.
- Feedback that I have gotten from customers is that the epic/issue name is confidential in itself so we'll need to redact that in all places where it could show up for someone that does not have access to that group/project.
- Text display in the Issue sidebar where the parent Epic is displayed should be redacted if the user does not have access to that Epic.
- All child issues should continue to be considered in date calculations regardless of the project they belong to.
- We should allow a user to change the parent epic, but they cannot change it back to the originally redacted epic if they don't have access to it.
- We should allow a user to remove an issue, but they cannot add back a redacted issue if they don't have access to it.
- When viewing an epic some issues may be in a project you don't have access to, we should redact the issue name.
- When viewing an epic in a roadmap issues may be in a project you don't have access to, we should include those issues in the calculations for percent complete
馃彈 Proposal
#367302[CROSS_GROUP_ISSUE_EPIC_WIDGET_FLOW.png]
Epic viewThe user can paste a link from an issue in another group/project into the epic tree and add it to the current group's epic tree view.
-
馃毇 If the user does not have access to the other project:- The user can paste a link to a cross-group issue, but if they do not have access to it they will get a validation educating them to such when they try to
add
- If an issue the user doesn't have access to is added to the epic tree view, the user does not see the issue "card" displayed
- The user sees the count of items + health status count update to reflect issues they may not have access to (current behavior)
- On hover of the item or health status count, the user sees a popover with the counts as well as an info alert educating them on the fact that their count may reflect items they do not have access to
- The user can paste a link to a cross-group issue, but if they do not have access to it they will get a validation educating them to such when they try to
-
馃憗 If the user has access to the other project:- The user can paste the URL for the cross-group issue and
add
it - The cross-group issue is displayed within the epic tree view as normal. The only change is that the breadcrumbs point to the group & project the issue originates from as this is different than the current
- The user can paste the URL for the cross-group issue and
#367302[CROSS_GROUP_ISSUES_ISSUE_VIEW.png]
Issue view- If the user does not have access to the other group, they see education in the
Epic
section of the sidebar with:- A
Warning icon
- Copy that reads something like
You don鈥檛 have permission to view this epic
- If the user tries to edit, a small popover (similar style to thee
lock
andconfidential
one) appears with copy likeYou do not have permission to view the currently assigned epic and will not be able to choose it again if you reassign it.
The user can confirm they want to edit anyway or cancel. - The user can not click the epic to navigate to it as they do not have access
- A
Edited by Alexis Ginsberg