How would you like to achieve this? (List the functional requirements here)
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.
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.
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
Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Could this happen for Sat 6.3?
Did you get the sales team involved in this request and do they have any additional input?
No interaction with Sales folks
List any affected packages or components.
-> smart class parameters template
Would you be able to assist in testing this functionality if implemented?
I do not have a test Sat6 server.
Would ordering the matchers on page load according to the order be enough for your use case, or do you expect the order to change dynamically if you change the order field or a matcher type?
The first option should be fairly easy to accomplish, the second would be much more complex and not likely to occur in the 6.3 timeline.
> Would ordering the matchers on page load according to the order be enough for
your use case?
Yes this would be sufficient.
Created redmine issue http://projects.theforeman.org/issues/18813 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18813 has been resolved.
6.3.0 snap 12
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.