Feature #18813
closedSort smart class parameter overrides by resolution order
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1425121
How would you like to achieve this? (List the functional requirements here)
Functional Requirements:
Putting highest priority matches at the top of the list should help clarify the way in which they will be parsed. This provides a visual representation of the logic to be used as well as a predictable way to locate existing matchers.
Technical Requirements:
Display the parameter matches sorted by resolution order, then alphabetical by matcher value.
For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Testing:
1) Add matchers for a parameter using all of the listed facts.
2) verify the matchers display in the listed resolution order
3) re-arange the resolution order
4) verify the matchers display in the new listed resolution order
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4360 added
Updated by Anonymous over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset ffdcc07de68aeb32eab44f7df67b2103d1f4f1a7.
Updated by Ohad Levy over 7 years ago
- Translation missing: en.field_release set to 209