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

Put NA in Branch column instead of - #12484

Open
nwmac opened this issue Nov 4, 2024 · 0 comments · May be fixed by #12497
Open

Put NA in Branch column instead of - #12484

nwmac opened this issue Nov 4, 2024 · 0 comments · May be fixed by #12497
Assignees
Labels
area/apps JIRA kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@nwmac
Copy link
Member

nwmac commented Nov 4, 2024

Right now, when the user has added OCI based repository, in the Repositories page, the Branch column shows as . It is better to show NA instead of or as deemed appropriate by the UI team.

Acceptance criteria

  • The branch column for OCI type Repository should show NA instead of -.
@nwmac nwmac added this to the v2.11.0 milestone Nov 4, 2024
@nwmac nwmac added the area/apps label Nov 4, 2024
@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed area/apps labels Nov 4, 2024
@nwmac nwmac added JIRA qa-environment-needed Label for features that require special environments beyond just installing rancher area/apps and removed qa-environment-needed Label for features that require special environments beyond just installing rancher labels Nov 4, 2024
@momesgin momesgin self-assigned this Nov 4, 2024
@momesgin momesgin linked a pull request Nov 5, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/apps JIRA kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants