|
Quin opened 2 years ago
|
||||||
|
Robin Shen changed fields 2 years ago
|
||||||
|
|
No such feature yet. Changed as an improvement. |
||||||
|
|
Hello Just following up on this, has it been implemented? I have an issue which I want to duplicate (same project, etc.) just with a name change. |
||||||
|
|
Not yet. Maybe in one or two patch release. |
||||||
|
|
Robin Shen changed title 1 year ago
|
||||||
|
OneDev changed state to 'Closed' 1 year ago
|
||||||
|
|
State changed as code fixing the issue is committed |
||||||
|
|
OneDev changed state to 'Released' 1 year ago
|
||||||
|
|
State changed as build #3271 is successful |
||||||
|
|
@robin This works great, thanks. Is it possible to not copy over the change history? Or maybe have the ability to delete it? (I'm just thinking how long these copied tasks may become with all the change history included; I find it useful, in some circumstances 😆) |
||||||
|
|
Maybe we can add an option for that if it turns out to be slow in future. |
| Type |
Improvement
|
| Priority |
Minor
|
| Assignee |
Not assigned
|
Issue Votes (0)
Watchers (4)
I understand that issues can be moved to other projects, but I was wondering if they could be copied to other projects.
Basically, it is a duplicate issue, split over two different projects (technically 1 project, 2 repos: a front-end and back-end). So when something needs to happen in the back-end, discovered in the front-end, I can simply "copy and paste" the task into the other repo. The alt. being is just to move it there, and then move it back.