Actions
Bug #12347
closed
Handle errata status with Library vs current environment
Status:
Closed
Priority:
High
Assignee:
Category:
Errata Management
Target version:
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Description
Currently the errata only looks at all applicable errata, and does not handle 'installable errata'
Some users may only care about installable errata, and it may be useful to query based on installable errata status.
So it may make sense to have two different errata statuses:
installable errata
applicable errata
each with security/non_security/none states
And the user could decide (via a setting) whether or not to use each one to build the global status.
Updated by Justin Sherrill about 9 years ago
- Blocks Feature #11435: Host Unification Tracker added
Updated by Eric Helms about 9 years ago
- Translation missing: en.field_release set to 86
- Triaged changed from No to Yes
Updated by Justin Sherrill almost 9 years ago
- Priority changed from Normal to High
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release changed from 86 to 143
Updated by Justin Sherrill over 8 years ago
- Translation missing: en.field_release changed from 143 to 114
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Justin Sherrill
- Translation missing: en.field_release deleted (
114) - Pull request https://github.com/Katello/katello/pull/6368 added
Updated by
Updated by Justin Sherrill over 8 years ago
- Translation missing: en.field_release set to 188
Updated by Justin Sherrill over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|a75565df0b98c64efe33874f0544034071e6b1c6.
Actions