Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When opening Catalog tab in Backstage UI, "component" field in 'Kind' dropdown disappears after selecting other fields #1153

Open
y-first opened this issue Feb 1, 2024 · 9 comments
Labels
jira kind/bug Something isn't working status/triage

Comments

@y-first
Copy link

y-first commented Feb 1, 2024

Describe the bug

The Catalog tab's "Kind" dropdown menu has a default value of "component". When anything else in the "Kind" dropdown menu is selected, the "component" value disappears.

Expected Behavior

component value will not disappear after selecting other fields.

What are the steps to reproduce this bug?

  1. Deploy backstage with orchestrator plugin using Helm chart here on a cluster
  2. Sign in to Backstage application.
  3. Navigate to Catalog tab.
  4. Select different value than "component" in the "Kind" dropdown menu.

Versions of software used and environment

Showcase image used: quay.io/janus-idp/backstage-showcase:pr-896

@y-first y-first added kind/bug Something isn't working status/triage labels Feb 1, 2024
@github-actions github-actions bot added the jira label Feb 1, 2024
@pkliczewski
Copy link

@christophe-f who can help with this bug?

@rtaniwa
Copy link

rtaniwa commented Mar 4, 2024

@y-first @pkliczewski I am a bit confused why this is in the plugin repo as a bug, as it really is the core backstage isn't it? That being said, unless I am misunderstanding the issue, I don't see this behaviour when using the janus showcase app. is this an issue with vanilla backstage (as if so, we should be opening up these issues in the upstream) or an issue with RHDH?

@y-first
Copy link
Author

y-first commented Mar 6, 2024

@rtaniwa @pkliczewski I just tested this using the rhdh-chart here, and saw that the issue reproduces:
Screenshot from 2024-03-06 16-29-18

So this looks like some default value in backstage.

@rtaniwa
Copy link

rtaniwa commented Mar 6, 2024

@invincibleJai @PatAKnight might this be related to RBAC defaults?

@invincibleJai
Copy link
Member

Thanks @y-first for reporting the issue

The Catalog tab's "Kind" dropdown menu has a default value of "component". When anything else in the "Kind" dropdown menu is selected, the "component" value disappears.

kind and type are connected, based on what the user selected in the kind , type gets updated and based on the selection can see the result on the list

so am a bit confused here when you said When anything else in the "Kind" dropdown menu is selected, the "component" value disappears. if you select something else then "component" disappears from the kind dropdown values itself or?

Deploy backstage with orchestrator plugin using Helm chart here on a cluster

is it happening with the orchestrator plugin enabled or otherwise as well?

@masayag
Copy link
Contributor

masayag commented Apr 11, 2024

so am a bit confused here when you said When anything else in the "Kind" dropdown menu is selected, the "component" value disappears. if you select something else then "component" disappears from the kind dropdown values itself or?

@invincibleJai it seems like an issue with updating the drop-down list elements in the catalog.
In this image when the drop-down list is opened for the first time, there are no components in the catalog.
However, the entry component is shown in that list with a lowercase.
Selection_175

After picking another item from that list, this list is refreshed, and the component that was there disappears:
Selection_176

That happens with janus-idp and RHDH images. Haven't checked with a vanilla backstage.

@invincibleJai
Copy link
Member

@masayag thanks for explanation and this could be same behaviour with vanilla backstage , can you pls check and confirm?

@ciiay
Copy link
Contributor

ciiay commented May 15, 2024

Hi @y-first I have tested the Backstage app from rhdh-chart and not able to reproduce the issue. Can you give it another try and see if the issue still exists?
Here's the version information I tested with:

RHDH Version: 1.1.0
Backstage Version: 1.23.3

@masayag
Copy link
Contributor

masayag commented May 29, 2024

@invincibleJai the issue appears also in vanilla backstage.
image

@ciiay this should reproduce when there aren't any components registered in RHDH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira kind/bug Something isn't working status/triage
Projects
None yet
Development

No branches or pull requests

6 participants