Actions
Bug #12347
closedHandle 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.
Actions