Discussion Checkpoints Layout Change in Modules Student View

Question

Hello,

I'm writing to see if anyone else has noticed this change in Canvas and can explain when and why it happened. I can't find anything in the release notes about it, and Canvas support says it is "intended."

Checkpoints in student view previously displayed directly below and slightly indented from the discussion forum, as shown below (taken from Canvas's Sneak Peek video).

However, we're now seeing the checkpoints appear on the same line but far off to the right, as pictured below. With requirements turned on, the requirement circle appears in between the two. We find this layout confusing, especially with the arrows seemingly coming down from the item above, which is no longer the discussion forum. We also think they could be easily missed if students are zoomed in (an accessibility issue), as everything else lines up along the left side.

Does anyone have any insight into this?

Thank you in advance!

dbrace · Answer

You are welcome, @ajrodenborn, and thank you for posting it. Doing your posted encouraged me to try to duplicate it (which meant it was not an isolated occurance) and then also report. I am sorry that you had the experience that you did.

-Doug

ajrodenborn · Answer

Thank you! I truly thought this could not have been intended, but the support person I spoke with claimed it was. Thank you for also following up on it!

dbrace · Answer

I just received this message:

=====

This is NAME from Canvas Support and I have reviewed your case. I'm sorry to hear that Discussion checkpoint dates appear at the far right side of the Modules page for students and this can be seen while in Student View.

I did some digging and found that this same issue was previously reported to our engineers and they are currently doing an investigation. This is not the intended behavior of the discussion checkpoint dates in the Modules page and we are currently looking for a solution. I will attach this case to our tracker so you will be notified when we deploy a fix to this issue. I'm sorry for the inconvenience.