Multi-level Child Epics UI Accessible in Premium When Feature is Ultimate-Only

Summary

The Multi-level Child Epics feature UI is visible and appears to be available for Premium users, but when they attempt to use it, they receive an error message. This feature is only available in Ultimate, but the UI does not properly restrict or indicate this limitation, leading to confusion.

Steps to reproduce

  1. Use a GitLab.com group on Premium
  2. Create a top-level group
  3. Create an Epic called Epic 1 within the top-level group
  4. Create a second Epic called Epic 2, also within the top-level group
  5. During creation of Epic 2, modify its Parent field and select Epic 1
  6. Click Create epic on the creation screen of Epic 2
  7. Observe that you receive the error No matching work item found. Make sure that you are adding a valid work item ID

What is the current bug behavior?

Premium users can see and interact with the Parent field in the Epic UI, creating the impression that they can use it. When they try to add an Epic as a child of another, they receive an error message that doesn't indicate the actual issue is a tier limitation.

What is the expected correct behavior?

Either:

  1. The Parent Epic field should be hidden entirely for Premium users, OR
  2. The UI should indicate that this feature requires Ultimate
  3. If a Premium user attempts to use the feature, they should receive a clear error message stating it's an Ultimate feature

Implementation Guidance

We can make use of allowed_child_types as higlighted in #525856 (comment 2420058810) to ensure that adding child items is only possible when license permits it.

Relevant logs and/or screenshots

Screenshot_2025-03-19_at_9.35.08_AM

Output of checks

This bug happens on GitLab.com

Edited by Kushal Pandya