Bug 1425121
Summary: | [RFE] Sort smart class parameter overrides by resolution order | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Candace Sheremeta <cshereme> |
Component: | Smart Variables | Assignee: | Tomer Brisker <tbrisker> |
Status: | CLOSED ERRATA | QA Contact: | Ondřej Pražák <oprazak> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.3.0 | CC: | bbuckingham, cshereme, inecas, jcallaha, oprazak, orabin, riehecky, tbrisker |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 12:38:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Candace Sheremeta
2017-02-20 15:44:28 UTC
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. Verified. 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. https://access.redhat.com/errata/RHSA-2018:0336 |