Skip to content

Community library status changes don't update date_updated #6414

Open

Description

@rtibbles

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

  • Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
  • Confirm that you’ve read the guidelines in your comment.

Overview

Two community library status changes use QuerySet.update(), which doesn't update auto_now fields, so the affected submissions keep their old date_updated. The notifications filters and the submission list's default ordering both use date_updated, so those status changes are missing from recent notifications and sorted in the wrong place.

Complexity: Low
Target branch: hotfixes

Context

The Change

  • Both status changes should also set date_updated to the time of the change.

Acceptance Criteria

General

  • After a submission is superseded, its date_updated is the time it was superseded.
  • After a live submission is moved back to approved by mark_live, its date_updated is the time of that change.

Testing

  • Both criteria have regression tests.

AI usage

I scoped the audit. Claude Code found these by reading the code and drafted this issue.

Activity

  1. added theissue type on Nov 15, 2026
  2. added
    good first issueSelf-contained, straightforward, low-complexity
    help wantedOpen source contributors welcome
    on Nov 15, 2026
  3. learning-equality-bot commented on Nov 15, 2026

    @learning-equality-bot
    Contributor

    Hi! 👋

    This issue is available for contribution and supports self-assignment. Here's how to get started:

    • Comment /assign to assign yourself to this issue
    • You can have up to 2 issues assigned at a time across all community repos
    • Dropping an issue has a 7-day cooldown before the slot opens up
    • Link your pull request to this issue when you submit it

    📖 Read the Contributing guidelines before starting.

    Are you preparing for Google Summer of Code? See our GSoC guidelines.

  4. LightCreator1007 commented on Nov 16, 2026

    @LightCreator1007
    Contributor

    /assign

  5. learning-equality-bot commented on Nov 16, 2026

    @learning-equality-bot
    Contributor

    Hi! 👋

    You can't be assigned to this issue right now because you've reached the 2-issue limit.

    Your current assignments:

    Once a slot opens up, come back and comment /assign again. 😊

    Are you preparing for Google Summer of Code? See our GSoC guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DEV: backendgood first issueSelf-contained, straightforward, low-complexityhelp wantedOpen source contributors welcome

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions