Skip to content

Ensure internal lists are named at creation and encourage cleanup of obsolete lists #2674

Description

@filiperochalopes

User story

As a curator, I want internal lists and candidate sets to have a name when they are created so I can distinguish active worklists without relying on renaming later.

Use case

Create QA worklists, internal lists, or Required Class Mapping candidate sets, assign a name at creation, and remove old lists once they are no longer needed.

Requirements

  • Review every workflow that creates a persistent internal list/candidate set and confirm it provides a naming field at creation.
  • Add a naming field where it is currently missing, including QA-generated worklists.
  • Do not add post-creation rename functionality.
  • In the existing delete modal for internal lists and Required Class Mapping candidates, add a note below the title encouraging users to remove lists that have already been used and are not expected to be reused.
  • The note should explain that removing obsolete lists helps keep the database clean and the system sustainable.

Acceptance criteria

  • Every persistent internal list/candidate workflow can be named when created.
  • QA-generated worklists include a naming step before creation is finalized.
  • Existing lists remain non-renamable after creation.
  • The delete modal displays the cleanup recommendation for both internal lists and Required Class Mapping candidate sets.

Metadata

Metadata

Labels

signal/low-riskSafe to execute with minimal downsidestage/triagedAI triage complete — scored and classifiedtype/featureNew or improved functionality

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions