Fix for view based priority sorting jelly #66
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong
In Jenkins - starting from version 2.264 - it was not possible to add or make changes to priority sorter for "Jobs included in a view".
Format of data in a json was not handled properly.
What has been done
Structure of elements in UI was wrong. The part of the UI responsible for filtering based on regular expression was placed inside views selector.
How to test
The test will result in "Oops!" page while using Priority Sorter plugin in version 4.0 and will work fine with the fixed version.
It has been tested and works fine on Jenkins 2.263.4 and 2.277.2