Modify ↓
Opened 14 years ago
Last modified 9 years ago
#9537 new enhancement
to implement cherry-picking for wiki pages
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | wiki system | Version: | |
| Severity: | normal | Keywords: | wikicopy |
| Cc: | itamarost@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
partially motivated by #1114
Would be nice to have an ability to pick any version from wiki revision history and copy it, making it the latest version. This way we don't need to delete anything (as mentioned in #1114). Instead, we keep full history intact, but just bring the version we need to the "head".
Attachments (0)
Change History (3)
comment:1 by , 14 years ago
| Component: | general → wiki system |
|---|---|
| Keywords: | wikicopy added |
| Milestone: | → next-major-0.1X |
| Owner: | set to |
comment:2 by , 14 years ago
| Cc: | added |
|---|
comment:3 by , 9 years ago
| Owner: | removed |
|---|
Note:
See TracTickets
for help on using tickets.
I'd suggest extending the requested feature to "allow copying a specified version to an arbitrary destination (including self)", which will create a copy of that version as the head version in the target (or version 1 if target does not exist).
And another extension, possibly a little more involved, is to implement batch selection of a group of wikis (possible a result of a query on the wiki hierarchy) with multiple-copy to arbitrary destination, possibly allowing to specify the source version for each source, or using some "selection rule" (like all versions as they seemed on date X). This practically implements a branch / tag feature for wiki-hierarchies.
See also this mailing list thread on additional use-cases for management of wiki-documents.