Investigation - Inheritance behaviour across Namespaces
Problem
There is a lot of inconsistency in our inheritance. See: #338819 (comment 667830288)
Example: How various plan objects currently behave
- Labels from a parent
Namespace
are visible in a childNamespace
label list.- Labels from a child are not visible in a parent's label list but they can be used for filtering & board lists.
- Iterations from a parent
Namespace
are visible in a childNamespace
.- Iterations from a child are not visible in the parent's iteration list.
- Epics from a parent
Namespace
are visible in a childNamespace
issue picker.- Epics from a parent are not visible a child
Namespace
epic list.- When an issue from a child is assigned to an epic in a parent, the epic is visible when "group by" is enabled.
- Issues from a child can be assigned to milestones from a parent.
- Issues from a child are visible in a parent's issue list.
- Milestones from a parent are not visible in the child's Milestone list.
- Milestones from a child are visible in the parent's Milestone list.
- The Member of a child can view the child's work items within the parent
Namespace
Board and edit the work item from within this context even though they are not a Member of the parentNamespace
.- There are all sorts of additional inconsistencies when it comes to
Namespace
sharing (&5791).
Proposal
- Investigate the current state of inheritance of features and functionality across
instance/group/subgroup/project
. - Define and document general inheritance patterns for namespaces to follow going forward.
Edited by Nick Post