Support includeDescendants and includeAscendants in group work items GraphQL query
- any performance concerns to be investigate?
- what about confidential issues from higher level groups ?
Also see &8776 (comment 1290803113)
I was thinking, for instance when user searches for parent work item to link to, we'd need to be able to fetch work items from current namespace(group or project) and ancestors? Maybe we would want to fetch work items from descendants as well if we think we should allow work items in descendant namespaces act as parent work items.
🤷
So short answer is perhaps in dropdowns, and potentially in work item lists when we consider swimlanes behaviour, ie grouping by some parent work items?
But I guess we would need product and UX to weigh in here on what would be the use cases where we may need to fetch work items from ancestor namespaces.
Edited by Donald Cook