Promote issue to epic in grandparent group doesn't work

Summary

All our company's products are structured in a group with subgroups per product. Inside each product's subgroup are multiple repositories. What we want to do is to have all epics defined at the top-level group, but when we promote issues from the nested repositories they end up in their parent group and there is no option to select grandparent group. We are using the /promote command in the issues.

Structure

graph TD;
  Company-->product1;
  Company-->product2;
  Company-->product3;
  Company-->product..n;

  product1-->repo1_1;
  product1-->repo..1_n;

  product2-->repo2_1;
  product2-->repo..2_n;

  product3-->repo3_1;
  product3-->repo3_n;

  product..n-->repon_1;
  product..n-->repo_n_m;

Steps to reproduce

1. Create issue in nested group repository.
2. Use the /promote command.
3. The issue will be converted to epic in the parent group. No way to select grandparent.

What is the current bug behavior?

No option to select grandparent groups with the /promote command.

What is the expected correct behavior?

A dropdown with all available grandparent groups.