View epic tree in epic

added to epic &644

changed milestone to %11.10

added GitLab Ultimate Plan [DEPRECATED] backend direction epics frontend internal customer + 1 deleted label

changed milestone to %11.11

added [deprecated] Accepting merge requests label

I'm adding GraphQL as we'd like to try using our GraphQL API for this! We will need to add groups and epics to this, for which we might want to create separate MRs / issues.

added GraphQL label

mentioned in issue #10778 (closed)

assigned to @digitalmoksha

removed [deprecated] Accepting merge requests label

changed weight to 5

changed the description

assigned to @annabeldunstone

added customer label

assigned to @kushalpandya

mentioned in issue gitlab-org/frontend/release-kickoffs#2 (closed)

mentioned in merge request !10999 (merged)

@digitalmoksha I've opened !10999 (merged) with initial frontend changes to add Tree tab within the Epic page. But we'd need some API help in the MR so that a single call returns list of Epics and their child Issues in a object tree. Feel free to push your backend changes to same MR.

added 1 deleted label

@kushalpandya Cool, thanks!

added depth label

@digitalmoksha and I discussed regarding tree structure that API needs to have and realized that it would be better to have async loading of child nodes whenever a parent node is expanded (similar to Groups Dashboard where we fetch child groups only when a given group is expanded).

Reasoning for doing so is to avoid lookup overhead that might happen when we're querying child epics for N levels of depth because Epic IDs are only unique within a group (eg; Group A can have epic with ID 1 and Group B which is a child of Group A can also have epic with ID 1).

@annabeldunstone What do you think on tree nodes being expanded async?

@kushalpandya That sounds good; I just have one question/reservation- will it be pretty snappy fetching the child epics/issues? I only ask because the sub-groups are almost unusably slow when you expand the parent groups.

added workflowin dev label and removed 1 deleted label

added missed-deliverable missed:11.11 labels

@ebrinkman FYI - this is going to miss the freeze for 11.11.

@digitalmoksha @kushalpandya - is there any reason this can't be behind a feature flag? It could still be picked into 11.11 after the freeze in that case.

(It is kind of already behind two feature flags, GraphQL and epics. But those are quite blunt instruments to disable this )

@smcgivern It would be pretty easy to gate the backend, but the frontend would have to (I think) leave in the original functionality (of listing epics and issues) - the new code removes that and moves it all into the new tree structure. Since @kushalpandya is traveling right now and will be at Contribute, I'm not sure that's possible or desirable.

Definitely we wouldn't want to disable the GraphQL and Epic feature flags

Good call, thanks for the confirmation

Sort of glad this won't be shipped until dragging and dropping is also complete.

This MR removes the ability to reorder items until https://gitlab.com/gitlab-org/gitlab-ee/issues/9367 is complete, and that might have a negative effect on users' workflows.

changed milestone to %12.0

removed workflowin dev label

added workflowin review label

mentioned in issue gl-retrospectives/plan#28 (closed)

mentioned in epic &711 (closed)

mentioned in issue #5419 (closed)

marked this issue as related to #11691 (closed)

mentioned in merge request !13246 (merged)

mentioned in merge request !13248 (merged)

mentioned in issue #9367 (closed)

mentioned in issue #11824 (closed)

closed via merge request !13246 (merged)

mentioned in commit bbf18a95

reopened

closed via merge request !13248 (merged)

mentioned in commit c25fa802

reopened

closed via merge request !10999 (merged)

mentioned in commit a3218bf4

mentioned in merge request gitlab-com/www-gitlab-com!23143 (merged)

changed milestone to %12.1

mentioned in issue #12484

mentioned in issue #12887 (closed)

mentioned in issue #12888 (closed)

added devopsplan label

added Enterprise Edition label

mentioned in issue gitlab-design#497 (closed)

marked this issue as related to gitlab-design#497 (closed)

mentioned in epic &1720

mentioned in issue #31447

marked this issue as related to #31447

mentioned in merge request gitlab-com/www-gitlab-com!30245 (merged)

added Technical Writing documentation labels

assigned to @rdickenson

Update on this: drag and drop has been merged so we're ready to turn the feature flag for this back on. We'll turn it on for gitlab-org today, and look for feedback over the next week or so before turning it on for everyone.