[Teak and Ulmo]: Completion checkmark(green tick) disappears on refresh for randomized Problem Bank XBlock

Site Operators Site Operations Help
1

Hello everyone,

I’m encountering an inconsistent completion indicator(green tick mark disappearing in unit sidebar and course outline page of LMS) issue using the new React-based content libraries - beta version (not legacy) with the Problem Bank XBlock in the following Open edX versions:

  • Teak: Checked in Tutor 20.0.3 and 20.0.5

  • Ulmo: Checked in Tutor 21.0.0

Steps to reproduce:

  1. Create and publish a content library with 5 problems.

  2. In a course, add Problem Bank XBlocks.

  3. Configure different randomization settings in separate Problem Bank XBlocks taking problems from above library:

    Scenario 1: Show 4 out of 5 problems
    → At LMS side, Student completes the 4 problems → green check mark appears on the click of Next/Previous button→ check mark remains → refresh page → check mark disappears and never reappears (In sidebar as well as in course home page).

    Scenario 2: Show 5 out of 5 problems (no randomization)
    → At LMS side, Student completes all 5 → green check mark appears and persists after refresh and navigation (In sidebar as well as in course home page).

    Scenario 3: Show 1 out of 5 problems
    → At LMS side, Student completes the 1 problem → green check mark appears → refresh page → check mark disappears and never reappears (In sidebar as well as in course home page).

Questions:

  • Is this a known issue with the Problem Bank XBlock of the completion API in Teak/Ulmo?

  • Issue seems to be populating from back-end side. So, any recommended workarounds or fixes?

Thank you for any insights or pointers!

1 Like
2

Hi @braden or @kmccormick - could I get your :eyes: on this question?

3

Thanks for the report @meet1.

Could this be related to fix: apply library_content transformer to all ItemBankMixin xblocks by MaferMazu · Pull Request #37830 · openedx/openedx-platform · GitHub ? @braden if so, would you have time to re-review and backport that?

1 Like
4

@kmccormick Yes, I should be able to give it another look soon, but I was really hoping someone else could give it a second set of eyes as well. It seems like an important fix.

5

Hi @kmccormick,

Thanks for the quick reply!

I checked PR #37830—it fixes grades in legacy libraries by applying the transformer to ItemBankMixin blocks. My issue is different: the completion checkmark disappears on refresh only for randomized (subset) Problem Bank XBlocks in the new React libraries, while full display works fine. It’s about completion persistence, not grading.

Thanks!

6

@meet1 Got it. I’ve opened an issue on openedx-platform and will try to investigate soon. Completion checkmark disappears on refresh for Problem Bank · Issue #38027 · openedx/openedx-platform · GitHub.

1 Like
7

Thanks @kmccormick. Really appreciate your help and support!

8

Follow-up: Completion checkmark still disappearing for Problem Bank XBlocks

Hi @kmccormick,

I hope you’re doing well.

I’m reaching out again regarding this issue where the completion checkmark (green tick) disappears on refresh for randomized Problem Bank XBlocks in Teak/Ulmo. The problem still persists even after the GitHub issue (#38027) was created.

This is causing a significant impact on our learners’ experience, and I would really appreciate your help in prioritizing and resolving this.

Could you please look into it at the earliest? Your assistance on this would mean a lot.

Thank you so much!

9

Thanks for your patience @meet1 . Our early testing indicates that we have just fixed this on the master branch, and we’re backporting it to Ulmo right now. I’ll keep this thread updated as we merge that backport and publish an Ulmo patch release, which should happen this week or next.

1 Like
10

Thanks for the updates @kmccormick!

Yes, please let me know once that PR is reviewed and merged.

11

This is now merged into the release/ulmo branch: fix: apply library_content transformer to all ItemBankMixin xblocks · openedx/openedx-platform@c5ab9b3 · GitHub

It’ll be included in the release/ulmo.3 tag, but even before ulmo.3 is out, you can try pointing your version to that commit.