Feature #1330
openCopy a Wiki Page
Added by Curtis Stewart over 16 years ago. Updated about 1 year ago.
0%
Description
We are trying to document our software project requirements and test cases in the project wiki. The simple reason is to allow multiple people to create and fix the items as we go along. To help, I have built some templates that can be used to make sure that we capture the data in a consistent format. We then just create issues to test the cases referencing the wiki pages. Works slick.
Since I have the formats, the only way I see that I can copy it to a new page is to cut and paste it into the new page. I would be simpler if I had an "include", "copy from" or some similar function.
I am aware that has changes occur to the format the old pages will not reflect the changes, but then neither do the paper versions I am doing currently.
Files
1330-copy-wiki-page.patch (11.9 KB) 1330-copy-wiki-page.patch | Takenori TAKAKI, 2023-07-20 08:08 | ||
1330-copy-wiki-page-with-childs.patch (20.4 KB) 1330-copy-wiki-page-with-childs.patch | Takenori TAKAKI, 2023-09-14 04:01 | ||
copy_wiki_page_with_child_pages.gif (356 KB) copy_wiki_page_with_child_pages.gif | Takenori TAKAKI, 2023-09-14 04:35 |
Updated by Chad Heuschober almost 14 years ago
+1 to this. Much like duplicating an issue, duplicating a wiki template (with retention of the parent!) would be a fantastic help.
We could use this for our pain points (user stories), and the individuals who design these are not usually technically adept enough to build link to another wiki page much-less the steps required edit the template, copy the contents, return to the pain points page, create a link to a new pain point, click the link to edit the new pain point, and paste the template contents.
If it were possible to duplicate the template (and inherit the same parent), I could direct users to duplicate the template, give it a new name, and simply use child_pages to generate my list of known pain points.
Updated by Ivan Cenov over 13 years ago
What if the templates have files and pictures attached? Should the copies share same files (these in the templates) or they have to be duplicated too?
Updated by Terence Mill over 13 years ago
include
Include a wiki page. Example:
Updated by Terence Mill over 13 years ago
Terence Mill wrote:
include
Include a wiki page. Example:
!{{include(Foo)}}
Updated by Jos Accapadi over 13 years ago
The include won't be exactly what people need as that means any changes to that affect changes to anything the include is in, which is sometimes opposite of what people need.
Simplest case:
I have an example template that I want everyone to use that says -
- Requirements
- Deployment
- QA Checklist
- Requirements
- Deployment
- Requirements
- Deployment
- QA Checklist
I would like them to just copy this template without having to go into the code, cut and paste into the new project, since version numbers may vary from project to project (which means that an include wouldn't work). A copy from project:wikipage would be nice here.
includes have their use case, but this is a different use case. Project managers run into this often with word documents being slightly modified from project to project.
Updated by Jos Accapadi over 13 years ago
In some way it is like the Duplicate function on an issue, except you can specify the target project wiki (come to think of it, duplicate on an issue and specifying a target project would be nice as well).
Updated by Tomasz Sawicki over 12 years ago
+1
Additional option for copying with child pages would be also nice...
Updated by Arthur Zalevsky over 11 years ago
we use wiki for educational courses which differs just in some details, so this feature would save much time, so +1
Updated by José Roberto García Chico about 11 years ago
+1 for this feature: duplicate a wiki page and its children pages
Updated by sebastien lemaitre over 10 years ago
+1 for reuse a wiki page with attachments
Updated by Mischa Mundwiler over 7 years ago
+1 - we use wiki pages for meeting minutes and a copy function of a predefined template would be awesome!
Updated by Takenori TAKAKI over 1 year ago
I attach the patch that allows copying of wiki page content, attached files, and optionally the parent wiki page (within the same project).
It doesn't support copying of child wiki page avoid functional complexity.
I hope this feature will be helpful to many Redmine users.
Updated by Mizuki ISHIKAWA over 1 year ago
+1
The #note-17 patch was tried and worked fine.
Updated by Takenori TAKAKI about 1 year ago
Updated by Takenori TAKAKI about 1 year ago
- File 1330-copy-wiki-page-with-childs.patch 1330-copy-wiki-page-with-childs.patch added
- File copy_wiki_page_with_child_pages.gif copy_wiki_page_with_child_pages.gif added
I attach the patch that allows for optional copying of child pages. When the "Copy child pages" option is selected, the copied child page title will automatically be appended with a suffix like "_1".
Updated by C S about 1 year ago
Takenori TAKAKI wrote in #note-20:
I attach the patch that allows for optional copying of child pages. When the "Copy child pages" option is selected, the copied child page title will automatically be appended with a suffix like "_1".
Looks great! +1