Revert ng-model changes from #381

[eclarizio]

After some deliberation, we decided it doesn't really make sense to change the ng-model designation since "values" doesn't make sense for a non sorted field that doesn't actually have a list of multiple values. Instead, the ng-model changes will be reverted and we will ensure the back end passes through the "default_value" properly for dynamic non sorted fields. That PR can be found here

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1698586

/cc @himdel

[miq-bot]

Checked commit eclarizio@09420c5 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. 👍

[himdel]

Backported to hammer:

commit 95b6155a6de1be81203df61ff2b1bd70a44a8f18 (HEAD -> hammer, upstream/hammer)
Author: Martin Hradil <himdel@seznam.cz>
Date:   Thu Apr 11 21:29:29 2019 +0000

    Merge pull request #382 from eclarizio/quick_bz_fix
    
    Revert ng-model changes from #381
    
    (cherry picked from commit 7c13a67aa52823c7e83ac629402cb619dddc5d3f)

@miq-bot add_label hammer/backported
@miq-bot remove_label hammer/yes

(Cc @simaishi)