Buzz: Questions & Answers

Individual student Extension for grouped students does not work

Follow
Answered
When I have students grouped and apply a due date for that group, I cannot change an individual students due date from that group if that student needs a retry or extension. It will not apply. How can I fix this?

Comments (4)

Sort by
Steven Martins
  • Agilix team member

Hello,

Teachers can modify due dates for individuals by using the Grade editor. Note that this feature works only in Range courses as Continuous courses have suggested due dates and no hard deadlines.

To do this:

  1. Select the desired activity from the Gradebook screen to open the Grade editor.
  2. If the activity has a due date, it will appear under the student's name in the left panel. Click the Due date.
  3. Change the Due date field.
  4. Save.

Also within the Grade editor, selecting the Allow retry button will grant the student a retry. Allowing retries on activities with an expired due date prompts you to modify the due date for that student.

If these steps/features don't seem to be working for you, could you please provide me with the student's enrollment ID and the activity ID for me to investigate what is causing your reported behavior?

0 Comment actions Permalink
Steven Martins
  • Agilix team member

Hey,

Thank you so much for that video! I was able to view the behavior you are experiencing and the steps taken. As of now, when I navigate to that same page shown in your video, the due date is showing as the newly modified date. Have you tried refreshing your browser after updating the score? I couldn't replicate this behavior in my test course.

I also noticed from the URL in your browser that HTTP (not secure) was used to access your school's site. Do you know if this is always the case when navigating to your school's site? Buzz should be served over HTTPS (secure).

I wanted to mention that this is a public forum; if you don't want your information viewed by the public, it would be better to reach out to the authorized support contact within your organization to submit a ticket to Agilix Support.

0 Comment actions Permalink
Steven Martins
  • Agilix team member

Thanks again for the video! After further investigation, I've found that Buzz prioritizes the due date set by the grouping, over the due date set for an individual enrollment. This is admittingly a bit confusing as I'd expect that if there is custom due date for a specific enrollment that it would override the due date set by the student's grouping. Unfortunately, we don't currently have a feasible way of fixing this. I sincerely apologize for the confusion and unexpected behavior.

Here are the current workarounds:

  1. If the student does not pertain to any grouping, the steps mentioned above will work as expected to change the due date for that particular student enrollment.

  2. Another option could be to have a group specifically to adjust student due dates. The majority of the class could be under one group for the normal class due dates. The second group could be the exception group with the new due date. If each student needs a different due date, additional groups would need to be created for each exception (See both example screenshots below).

Regarding the HTTP (not secure), I believe that you may just need to edit your bookmark to include HTTPS (secure). See if this link works instead: https://pacyber.lms.lincolnlearningsolutions.org. If so, I would highly recommend checking out Google's documentation on how to edit Chrome bookmarks and replacing the URL from your bookmark with this new link.

Again I sincerely apologize for the inconvenience. I hope this information helps out.

0 Comment actions Permalink

Steven, thank you for your response.

I will continue to use the workarounds for it.

Hopefully Buzz can fix this in a future update somehow? I realize it is hard to know there is an issue until it is in practice.

I look forward to learning new features of BUZZ and incorporating them in my classroom.

 

0 Comment actions Permalink
Please sign in to leave a comment.