Task Prioritisation Recommender Service

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.

[rashi-agrawal29]

Description

This PR introduces a Task Prioritization API that recommends and ranks student tasks across all enrolled units based on a weighted priority scoring model.

The service aggregates all incomplete tasks for the authenticated student and computes a priority score using three factors:

Deadline urgency (based on days remaining)
Estimated effort (currently derived from task weighting; placeholder for future AI integration)
Workload (based on number of incomplete tasks and average target grade across units)

Tasks are then sorted in descending order of priority and returned via a new API endpoint:

GET /api/tasks/recommended

This feature enables a unified, cross-unit task recommendation system for the student dashboard.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The feature was tested using the following approaches:

• Manual API testing using curl
• Validation of task retrieval across multiple enrolled units
• Verification of priority score calculations (deadline, effort, workload)
• Sorting validation to ensure tasks are returned in descending priority order

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes

If you have any questions, please contact @macite or @jakerenzella.

[Niethin69]

Hey @rashi-agrawal29, I've opened #102 as a stacked PR that addresses some review-stage issues I found while testing locally (status filter, N+1, nil edge cases) and adds test coverage. I went with a separate stacked PR, but your authorship on this PR stays untouched, credited you in mine. Happy to walk through the changes before either PR is reviewed.