Thanks for you fast fix Magnus. I have a good and a bad message about it though
The good one: It seems to work, the jobs are found in the views and priorities are assigned as configured.
The bad one: It seems to be a real performance hog at least with our quite large installation.:-/ Jenkins UI was unusable after some time, after downgrading everything is back to normal.
Some facts: We have about 10000 Jobs, more than 20 views refering most of the jobs via regex pattern. So I could imagine that there are long lists of jobs being iterated while computing priorities.
Would it be a better approach for us to configure job priority directly on the job? That would be not a big deal because most of them are generated from template?
Should I open a new JIRA ticket? Or reopen this one?