I'm working with restrict access conditions on assignments in 2.9.
It appears that while Restrict access/conditional availability for assignment visibility is fine, it is only checking the conditions where users are explicitly stated to assemble the participants list. This creates a situation where submitted assignments are not accessible to teachers for grading. Here's an example:
Create an assignment.
Set Restrict access on the assignment OR on the summary of the block where the assignment exists.
Create two access conditions such that one student gets access prior to the other students:
Student must match any of the following
Student must match all of the following
Date from 1 Sept 2015 00:00
User profile field Email address is equal to email@example.com
Date from 4 Sept 2015 00:00
I've tested with email address, name and ID conditions with the same results. As expected, the visibility of the assignment or content in the block becomes available only to the student who is included in the conditions once the first date is met. Once the OR date condition is fulfilled, the remaining students are able to see and submit the work; however, if there is a condition to limit based on a user profile field the assignment is never updated with the correct participant information.
This essentially creates assignment submissions that are inaccessible to the teacher for view or grading. Notice when viewing the assignment Grading summary page the Participants number will not change from 1 unless the student profile condition is removed or a condition is added to the OR date to specifically include the other students.
For example, changing the second condition to the condition below will result in the participant count of the assignment updating when it becomes available on Sept 4:
Date from 4 Sept 2014 00:00
User profile field Email address is not equal to firstname.lastname@example.org
I'm happy to add this to tracker as a bug, but I just wanted a few other eyes on it to verify first.