Make it possible to view a deleted Entity's history

Open
#2,328 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
backend, frontend

Research direction

The payload names no files. Start from the deleted-entities filtered list and the existing entity detail view, and check what the restore action currently exposes. Done means a deleted entity (and, per the issue, a submission) can open a read-only detail page that marks it as deleted and shows create, edit, and delete dates and the deleter. The design for the deleted indicator and the no-edit rule is still open, so confirm it with the maintainers before building.

Written by the indexing model from the issue text.

Description

backend frontend needs testing

Currently, when you delete an Entity, it is listed in the deleted filtered list but the only action that can be taken on it is to restore it.

This makes it hard to audit what happened. Ideally it would be possible to access that Entity's history to review create date, the date of any edits, the contents of any edits, the delete date, and the deleter. I think being able to access the standard detail page with an indication that it's for a deleted Entity would be ideal.

The same would be helpful for submissions.

CC @ksefadedeh @nicoleorlowski I'm filing this as an issue because I think it's a very small change, it mostly needs design to indicate clearly that it's deleted, not allow further edits, etc.

Dominant language
JavaScript
Stars
233
Forks
241
Avg merge
1d 22h
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/central

All issues in getodk/central

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.