View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009072 | mantisbt | feature | public | 2008-04-15 07:59 | 2021-05-06 10:24 |
Reporter | BovenH | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Product Version | 1.1.1 | ||||
Summary | 0009072: Not possible to create a clone in a different project | ||||
Description | In our organization we have 2 projects configured (one for Systems department and one for Software department). If a problem is found it is reported on system level. If it is not only a documentation/hardware issue, and software needs to be changed, a clone is created for the Software project. However, this is not directly possible. It is only possible to:
We do not need to adjust custom fields, since these are the same for both projects. Sugestion: When pressing Clone, first show a different page (like e.g. the “login_select_proj_page.php?ref=bug_report_page.php”) this page then will request
and then show the Report Issue page, with the new custom fields (which are not present in the original project) set to their defaults. | ||||
Tags | No tags attached. | ||||
We've just implemented exactly this feature in our customized mantis deployment. I'll work on a patch for this. |
|
another vote for this feature, thanks! |
|
Daryn, Excellent!!! Thankx for picking up this issue! |
|
+1 |
|
Any updates? I'd also need that feature! |
|
Unassigned after having been assigned for a long time without progress. |
|
May we remind Daryn of GPL? |
|
We might get the complete code of his customized MantisBT but will still not have a patch to resolve this issue. |
|
This seems to be related to 0008144. Will it be implemented in 1.3? |
|
|
|
Seems you mean 0008114 |
|
You might want to use the "Copy" functionality of the "View Issues" page for it. |
|
Oh, sorry for the confusion, you are perfectly right with the issue #. Ah, and there is no "Copy" button on the "View Issue Details" page; I rarely use the action menu on the "View Issues" page, so I was not aware of it. But this is good to know, now I can tell my colleagues about it. Thanks a lot! |
|
Hi, I comment on this issue because we have the same need as in the description. Thanks for the tip of the copy (I was not ware of its existence till now). Very useful and could fulfill the action in a certain way.
|
|
+1 too, definitely need this! Our use case involves tracking security vulnerabilities and 'cloning' a task descriptive values without its notes would definitely be awesome. |
|
+1 |
|
+1 |
|
I also need this capability. In the interim, it would be helpful to be able to turn on the Project Id field when reporting issues. Copy isn't a good solution because it takes you back to the View Issues page without showing you the number of the new issue you copied, so you have to go to the project you copied the issue to and search for it, then open it and revise it. That doesn't seem more efficient than the original solution, which was to clone the issue, then move it. |
|
reated to 0024745 ? |
|