List of feature flags not showing up in project UI

Summary

~SaaS GitLab Premium customer has a project where the list of feature flags is showing up in the UI. There is a count indicating 23 feature flags. Upon inspecting DevTools, the Console has an error message TypeError: Right side of assignment cannot be destructured - utils.js:44. More details in Relevant logs and/or screenshots.

Another project own by the customer is showing up the feature flags just fine.

The URLs of the projects are found in this internal Zendesk ticket.

Steps to reproduce

Unable to reproduce so far.

Example Project

What is the current bug behavior?

List of feature flags should show up for all projects.

What is the expected correct behavior?

List of feature flags does not show up for some projects.

Relevant logs and/or screenshots

Inspecting DevTools Console give the following error:

TypeError: Right side of assignment cannot be destructured
parameters — utils.js:44
(anonymous function) — utils.js:57
strategyBadgeText
(anonymous function) — feature_flags_table.vue:1:3602
be — vue.runtime.esm.js:2646
(anonymous function) — feature_flags_table.vue:1:3358
be — vue.runtime.esm.js:2646
(anonymous function) — feature_flags_table.vue:1:867
(anonymous function) — vue.runtime.esm.js:3569
r — vue.runtime.esm.js:4081
(anonymous function) — vue.runtime.esm.js:4495
fn — vue.runtime.esm.js:4484
(anonymous function) — vue.runtime.esm.js:4088
init — vue.runtime.esm.js:3137
(anonymous function) — vue.runtime.esm.js:6022
d — vue.runtime.esm.js:5969
(anonymous function) — vue.runtime.esm.js:6260
E — vue.runtime.esm.js:6363
(anonymous function) — vue.runtime.esm.js:6526
(anonymous function) — vue.runtime.esm.js:3963
r — vue.runtime.esm.js:4081
(anonymous function) — vue.runtime.esm.js:4495
(anonymous function) — vue.runtime.esm.js:4570
ln — vue.runtime.esm.js:4326
(anonymous function) — vue.runtime.esm.js:1989
Jt — 

Output of checks

This bug happens on GitLab.com

Possible fixes

Workaround

1. Try to set up feature flags on another project.
2. Vladimir Shushlin, @vshushlin: as another workaround, I think deleting all feature flags using API and re-creating them should help. The root cause of this is invalid feature flag configuration which users somehow achieved, so simply dropping all feature flags should help.