feat: add instructor task for async batch enrollment

[BryanttV]

Description

This PR introduces asynchronous support for Batch Enrollment/Unenrollment in the Instructor Dashboard. The goal is to address scalability limitations of the current synchronous process, which is prone to timeouts when handling large groups of learners.

Motivation

Currently, batch enrollment/unenrollment is only available in synchronous mode. For large enroll/unenroll lists, this process may time out, causing failures and reliability issues. With this change, instructors can optionally select an async mode, which processes enrolls/unenrolls in the background, avoids timeouts, and provides better progress tracking and notifications.

Implementation Details

• Added a new checkbox "Process asynchronously" in the Batch Enrollment UI (unchecked by default).

• If async mode is selected:

  • An Instructor Task is created to handle enrollment/unenrollment asynchronously using a Celery task.
  • A message is displayed in the UI confirming that the async process has started, and that an email will be sent once it finishes.
  • Task progress can be tracked in Instructor Dashboard > Pending Tasks.
  • Once complete, a CSV report with the enrollment/unenrollment results is generated and uploaded to Instructor Dashboard > Data Download.
  • An email notification is sent to the instructor with a direct link to download the report.

• If async mode is not selected, the current synchronous behavior remains unchanged.

Screenshots

Before	After

Tooltip

Informative user message

Body email

CSV report

CSV content

Testing instructions

Using a Tutor environment:

1. Mount edx-platform with the changes from this PR. I recommend using tutor local.

2. Build the openedx image with tutor images build openedx.

3. Create a course.

4. Create some users (recommended: +100).

5. Navigate to Instructor Dashboard > Membership > Batch Enrollment.

6. Add the usernames or emails in the text area.

7. Check the Process asynchronously checkbox.

8. You should see an info message in the interface indicating that the process has started.

9. When the process finishes:

   • A CSV report will be available in the Data Download tab of the Instructor Dashboard.
   • An email will be sent to the user who initiated the process.

Deadline

None

Other Information

I found a bug introduced in this PR. The user used in the create_manual_enrollment_audit method should be the request.user, not the identified_user.

https://github.com/openedx/edx-platform/blob/405282c17efcdb19f578ed553f728c9218a271a4/lms/djangoapps/instructor/views/api.py#L896-L898

I also fixed that bug in the current PR.

[openedx-webhooks]

Thanks for the pull request, @BryanttV!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[efortish]

We can use something like this to create the users:

from django.contrib.auth.models import User
from common.djangoapps.student.models import UserProfile
from common.djangoapps.student.models import CourseEnrollment
from opaque_keys.edx.keys import CourseKey

course_key = CourseKey.from_string("course-v1:test+12+2025")
password = "test123"
amount = 100

for i in range(amount):
    username = f"user{i}"
    email = f"user{i}@example.com"
    user = User.objects.filter(username=username).first()

    if not user:
        user = User.objects.create_user(username=username, email=email, password=password)
        print(f"User created: {username}")
    else:
        print(f"User already exists: {username}")

    try:
        user_profile = user.profile
    except User.profile.RelatedObjectDoesNotExist:
        user_profile = UserProfile.objects.create(user=user, name=username)
        print(f"Profile created: {username}")

    if not CourseEnrollment.objects.filter(user=user, course_id=course_key).exists():
        CourseEnrollment.enroll(user, course_key)
        print(f"{username} enrolled successfully")
    else:
        print(f"{username} is already enrolled")
```

[efortish]

Hi @BryanttV

I tried the new feature and it is working as expected, thank you so much for your contribution.

Can we add a detail test suit for this new feature?

[mphilbrick211]

hi @BryanttV! Bumping this for you.

[BryanttV]

Thanks for your review @efortish! I will be working on implementing the unit tests.
And thanks for the ping @mphilbrick211!

[mphilbrick211]

@BryanttV @mariajgrimaldi hi there! is this still in progress?

[mphilbrick211]

@BryanttV @mariajgrimaldi hi there! is this still in progress?

Final ping on this one, @BryanttV!

[MaferMazu]

@mphilbrick211, in my understanding, @BryanttV would continue with this PR.

@BryanttV, could you update the PR so it can receive a proper review? ✨

[BryanttV]

Hi @MaferMazu, thanks for the review! I've addressed your comments. Could you take another look?

[MaferMazu]

@BryanttV thanks for addressing my comments.
✅ All looks good! I only have one comment left based on a Gemini suggestion ( #37216 (comment)), after solving that we can merge this. Thanks again.

[MaferMazu]

@BryanttV thanks for addressing my comments! This looks good to me! After the tests pass, we are good to merge! Thanks for this change 🙌

[BryanttV]

Hi @MaferMazu! The checks passed 💯 Can we proceed with the merge?