Skip to content

Uploading Gradeable JSON defaults to peer grading even when it is set to false #12151

@nikapadia

Description

@nikapadia

Describe the bug
When uploaded a Gradeable JSON, the rubric components are automatically being defaulted to peer grading even when the value for peer_component is set to false.

Expected behavior
The rubric component should not have peer grading enabled.

To Reproduce
Steps to reproduce the behavior:

  1. Upload gradeable with peer_component set to false
  2. Head to Rubric tab
  3. See error

Configuration

  • OS: Ubuntu 22.04 LTS
  • Browser: Firefox

Screenshots
N/A

Additional context
JSON I have been using and seeing the issue on.

{
    "title": "Status Update 11\/07\/2025",
    "type": "Electronic File",
    "id": "StatusUpdate7",
    "instructions_url": "",
    "syllabus_bucket": "lab",
    "autograding_config_path": "\/var\/local\/submitty\/courses\/f25\/csci1700\/config_upload\/StatusUpdate_v01",
    "bulk_upload": false,
    "ta_grading": true,
    "dates": {
        "ta_view_start_date": "2025-09-25 21:46:43",
        "grade_start_date": "2025-11-09 23:59:59",
        "grade_due_date": "2025-11-13 23:59:59",
        "grade_released_date": "9998-01-01 00:00:00",
        "team_lock_date": "2025-09-26 15:59:59",
        "submission_open_date": "2025-11-07 15:59:59",
        "submission_due_date": "2025-11-07 23:59:59",
        "grade_inquiry_start_date": "2025-10-11 23:59:59",
        "grade_inquiry_due_date": "2025-10-17 23:59:59",
        "has_due_date": true,
        "has_release_date": true,
        "late_submission_allowed": true,
        "late_days": 2
    },
    "rubric": [
        {
            "title": "Status Update Grade",
            "ta_comment": "",
            "student_comment": "",
            "lower_clamp": 0,
            "default": 0,
            "max_value": 10,
            "upper_clamp": 10,
            "text": true,
            "peer_component": false,
            "page": 0,
            "is_itempool_linked": true,
            "itempool": "",
            "marks": [
                {
                    "points": 0,
                    "title": "No Credit",
                    "publish": false
                },
                {
                    "points": 10,
                    "title": "Full credit.",
                    "publish": false
                },
                {
                    "points": 4,
                    "title": "Thorough \"This Week\" section. Good job.",
                    "publish": false
                },
                {
                    "points": 4,
                    "title": "Thorough \"Next Week\" section. Good job.",
                    "publish": false
                },
                {
                    "points": 1,
                    "title": "Complete \"Blockers\" section. This field must be filled out but may contain \"No blockers to report\" if there are no technical issues preventing you from making progress.",
                    "publish": false
                },
                {
                    "points": 1,
                    "title": "Complete \"Links\" section. This field must be filled out but may contain \"No links to submit\" if you have no open-source contributions to report. If links are reported, they must be to valid user generated open-source contributions",
                    "publish": false
                },
                {
                    "points": 2,
                    "title": "\"This Week\" requires greater detail.",
                    "publish": false
                },
                {
                    "points": 2,
                    "title": "\"Next Week\" requires greater detail.",
                    "publish": false
                }
            ]
        }
    ]
}

Metadata

Metadata

Assignees

Labels

Awaiting TriageBrand New Issue - not yet reviewed & prioritized by the Submitty Project Managersbug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions