Yes a Job can be in multiple views but the lookup order is well defined by a "first match" approach, I really wanted to get away from "forcing" the user to add a property to all Jobs. I like the view-way since it is reusing an already defined grouping and existing ui from doing the grouping and it also makes it possible to let admins control the grouping/priority even if users can create the Jobs.

I do not know if this is common way but we are heavily using Job names to automatically group Jobs into views and then the priority of a Job automatically follows.

I can however see benefits of the JobProperty way as well, I already (still) support setting the priority directly on the Jobs so maybe allowing Grouping this way as well is possible.

If you hear any opinions from your user group don't hesitate to share - I'm all ears.