Bug 2222979 - Repository details page shouldn't say 'enabled by default'
Summary: Repository details page shouldn't say 'enabled by default'
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.14.0
Assignee: Samir Jha
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-14 17:08 UTC by Jeremy Lenz
Modified: 2023-08-10 18:07 UTC (History)
4 users (show)

Fixed In Version: rubygem-katello-4.9.0.10-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of outdated text (78.25 KB, image/png)
2023-07-14 17:10 UTC, Jeremy Lenz
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36593 0 Normal New Repository details page shouldn't say 'enabled by default' 2023-07-19 11:47:32 UTC
Red Hat Issue Tracker SAT-18962 0 None None None 2023-07-14 17:12:49 UTC

Description Jeremy Lenz 2023-07-14 17:08:46 UTC
On the New Repository page, there are two places where we say "The repository will be enabled by default on..." This is no longer true since custom repositories are disabled by default, and was never 100% true for Red Hat repositories.

We also say the same thing in tooltips on the repository edit screen.

Should change the wording to "The repository will only be available ..." or something similar.

Comment 1 Jeremy Lenz 2023-07-14 17:08:50 UTC
Created from redmine issue https://projects.theforeman.org/issues/36593

Comment 2 Jeremy Lenz 2023-07-14 17:08:52 UTC
Upstream bug assigned to None

Comment 3 Jeremy Lenz 2023-07-14 17:10:25 UTC
Created attachment 1975834 [details]
screenshot of outdated text

Comment 4 Bryan Kearney 2023-08-02 20:03:24 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36593 has been resolved.


Note You need to log in before you can comment on or make changes to this bug.