Skip to content

config: Add a flag to determine what should be populated in the publication date of the next versions of a record on migration #387

Description

@sakshamarora1

We have 2 use cases:

  1. Records like issues and articles :- Where a file is updated but the publication date needs to be same across versions
  2. Records like HR documents :- A new file uploaded on a new version should show show the date when it was "refreshed"

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions