Skip to content

Conversation

@deborahgu
Copy link
Member

It is possible to be overly enthusiastic about how many retirement partner reports are reset at once, in such a way that the system struggles to handle how many have been reset. This allows you to revert that change.

FIXES: APER-4177

Description

Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be
linked here.

Useful information to include:

  • Which edX user roles will this change impact? Common user roles are "Learner", "Course Author",
    "Developer", and "Operator".
  • Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).
  • Provide links to the description of corresponding configuration changes. Remember to correctly annotate these
    changes.

Supporting information

Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.

Testing instructions

Please provide detailed step-by-step instructions for testing this change.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Include anything else that will help reviewers and consumers understand the change.

  • Does this change depend on other changes elsewhere?
  • Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
  • If your database migration can't be rolled back easily.

It is possible to be overly enthusiastic  about how many retirement
partner reports are reset at once, in such a way that the system
struggles to  handle how many have been reset. This allows you to revert
that change.

FIXES: APER-4177
@deborahgu deborahgu requested a review from a team as a code owner October 23, 2025 21:01
Comment on lines 194 to 197
message_bit = "one user was"
else:
message_bit = "%s users were" % rows_updated
self.message_user(request, "%s successfully reset." % message_bit)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to clarify, should the message be the same for both reset_state_false and reset_state_true?

@deborahgu deborahgu enabled auto-merge (squash) October 24, 2025 16:46
@deborahgu deborahgu merged commit 3dc96a9 into openedx:master Oct 24, 2025
48 checks passed
@deborahgu deborahgu deleted the dkaplan1/APER-4177_prod-retirement-partner-report-reset_toggle branch October 24, 2025 17:07
deborahgu added a commit to edx/edx-platform that referenced this pull request Oct 24, 2025
openedx#37539)

* feat: allows a reversion of the  retirement partner report reset toggle

This allows you to set retirement partner report statuses to True as well as to False. One sample use case: if an overly large number of retirement partner reports have their status reset to false, the partner report queue can struggle to deal with the large queue.

FIXES: APER-4177
haftamuk pushed a commit to haftamuk/edx-platform that referenced this pull request Nov 3, 2025
openedx#37539)

* feat: allows a reversion of the  retirement partner report reset toggle

This allows you to set retirement partner report statuses to True as well as to False. One sample use case: if an overly large number of retirement partner reports have their status reset to false, the partner report queue can struggle to deal with the large queue.

FIXES: APER-4177
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants