Explicitly set revision log on cloned logs

Created on 16 July 2022, almost 3 years ago
Updated 28 May 2025, about 1 month ago

Problem/Motivation

The fact that a log is initially cloned from another log is not preserved in the revision history of the new log. It would be easy to include this, and add useful context to the history of the records.

Proposed resolution

Set the log revision message on newly cloned logs to say "Cloned from log [original-log-id]"

Remaining tasks

Implement.

User interface changes

Revision log of cloned logs will indicate that they were cloned.

API changes

None.

Data model changes

None.

✨ Feature request
Status

Active

Version

2.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States m.stenta

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024