feat: adding CCX support to gradebook API

[luisfelipec95]

Description

This PR updates the "View Gradebook" link in the CCX (Custom Courses for edX) coach dashboard to point to the writable Gradebook MFE when enabled, instead of defaulting solely to the legacy gradebook view.

Currently, CCX staff are directed to the legacy gradebook view, preventing them from accessing modern grade management capabilities. This change retrieves the WRITABLE_GRADEBOOK_URL from configuration helpers or settings and builds the MFE URL with the corresponding ccx_locator context whenever is_writable_gradebook_enabled evaluates to true.

Issue Reference

#37898

Changes Made

• Updated the dashboard view in lms/djangoapps/ccx/views.py:
  Fetched WRITABLE_GRADEBOOK_URL using configuration_helpers.get_value() with fallback to settings.WRITABLE_GRADEBOOK_URL.
• Checked is_writable_gradebook_enabled(ccx_locator) and updated context['gradebook_url'] to {writable_gradebook_url}/{str(ccx_locator)} when enabled.

[openedx-webhooks]

Thanks for the pull request, @luisfelipec95!

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

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.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

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.

[mphilbrick211]

Hi @luisfelipec95! Is this still in progress?

[luisfelipec95]

Hi @luisfelipec95! Is this still in progress?

Hi @mphilbrick211! Thanks for checking in. I created an issue outlining the justification and proposed approach and referenced this PR as a draft to support the discussion. I’m waiting for feedback there before moving this PR forward. Once the discussion concludes, I’ll either mark it ready for review or close it accordingly.

#37898