Regression in App Values page, Group name not showing with just one question

[leodotcloud]

Rancher Server Setup

• Rancher version: v2.6.5

Describe the bug An app with just one question in questions.yml doesn't show the group name in the UI.

To Reproduce Create a custom app with just one question in questions.yml

questions:
# Image configuration
- variable: imagePullSecrets
  default: ""
  description: "Secret name to pull image from Registry"
  type: secret
  label: Image Pull Secrets
  group: "Container Images"

Result The group name is not shown in the UI.

Expected Result

Screenshots

Additional context Adding a second question with a different group name resolves the problem.

[shizhiliuyu]

I found that v2.6.3 multiple groups also show only one problem

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[leodotcloud]

not stale

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[leodotcloud]

not stale

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[leodotcloud]

not stale

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[leodotcloud]

not stale

[rak-phillip]

Transferring to dashboard repo for triage.

@nwmac @gaktive

[lindhe]

I'm also experiencing this issue. Running Rancher v2.7.6.