Communication channel to learn about breakages as they happen, or likely breaking changes?

Jump to solution
PaulNagami
Community Contributor

I just had a student inform me that they could not reply to other students in a discussion that I set up in advance over the summer. I saw that threaded replies had been turned off without my knowledge, turned them back on, and announced the bug to the class with my apologies.

Last month, I also ran into a major breakage of pre-made Announcements and had to remake all of my announcements this term. I found out only when they announcements were not being sent, and the only way I got more info was by visiting these forums after the breakage happened.

Is there a communication channel by which instructors can be informed of these breakages when they happen, or warned of changes that are likely to render their existing course materials inaccessible? Do we need to keep relying on side channels?

Labels (1)
0 Likes
1 Solution

@PaulNagami ...

Thank you for your response, and I apologize that my response wasn't satisfactory.  I'm a fellow Canvas user like yourself, and I don't work for Instructure.  (I work for a college in Michigan.)  I can understand when things don't work the way that you and I expect them to.  I've had some of my own experiences with this, so I hear what you are saying.

Thanks also for providing that link to the known issue for the announcements.  I had not seen that one.  In looking at the documented issue, there is a note in the light blue box:

"This case was unable to be reproduced. If behavior persists, please submit a new support case."

Have you had the opportunity to submit a ticket to Canvas Support (Canvas Help Desk) so that you can get this issue logged?  I know I mentioned this in my first response, but I wasn't sure if this was something you had already tried or not.  That is what I recommend.  That way, you'd be notified if/when any new resolutions are found.

Again, apologies if my earlier response wasn't what you were hoping for.  Take care...

View solution in original post