Sort of, we generally maintain a 1:1 relationship from the Job to the release, essentially it’s looking for any changes to the releases dates.
In the circumstance that there are multi release against a singular job, it will be scheduled to the earliest release date as the linq query behaves like a sql query doing min(OrderRel.NeedBy) syntax.
Sure you could tinker with the query to filter out any closed releases, that way the job sync to next open release. From an operation flow perspective not entirely sure how sound it would be thought.