|
That's a good idea.
This is a bigger issue than just comments!
I have made some fields - such as due date and time estimate - required fields, and these are ALSO not copied! At a minimum, I think that clone should copy all required fields. Is that issue already in the database somewhere? Okay - generalizing the summary. The checkbox would then be whether to do a deep or shallow copy.
We are really in need of a DEEP COPY !!!
We are using this to forward issues from one project to another, an we would like to have an identical clone. This means, we nedd:
Doesn't anyone else need this feature? I would have guessed that there are more people here wondering, why clone works so shallow. Gerd,
Can I ask why you are moving issues between projects? I'd be interested in hearing why you need this. Cheers, Hi Scott,
we have follwing situation: We have 2 Teams Project 1 contains support requests, bug reports, feature request from customers, which are mainly handled by Team 1. The Developers are not bothered by this. Project 2 contains the development roadmap, which is discussed between the project-lead and the client-manager. Both projects have an identical setup concerning versions and components and also share common custom fields. If there are Bugs/Support Requests, which have seriously to be dealt with, then Team1 wants to forward the request to Team2 (and to project2). Within jira-project2 the developers will add technical information, discussion and lots of other stuff which most of the users wouldn't understand anyway and schouldn't be bothered with, The double-project setup gives us follwing advantages:
We also considered using security levels, but this would mean, that the user couldn't see his request any more. We also thought about just assigning a developer, but that would disclose the developers name and too much internal stuff, we don't want the user to see. So these alternatives didn't satisfy our needs. So we came up with the idea, we have now. And my problem is, that i thought "clone" would do an exact copy. What we realized now, is that our first level support team is doing a lot of work, typing the same information twice, when they first clone an issue and then move it to another project. What we would need is a "complete clone" together with an "extended move". "Move" schould try to match versions/components by value, if posible. What do you think? Is this idea too "exotic" ? I have to agree that this is an important issue for us. We have many cases where we use a public front end issue management project with a related developer only project. cloning/moving issues between is common practice and we really need a mechanism to clone all details of an issue.
I move issues between projects too (on a daily basis), in a similar (but more simple) way to that which Gerd describes.
We have a "support" project which takes any sort of user request, from "how do I do [this]?" to "[that] throws an exception". If it's a "how to" issue, it stays where it is and I deal with it there. If it's a bug type issue, then I clone/move the issue to the bugbase so the software team can deal with it, whilst I continue with the original issue to discuss / document / provide a temporary work around, until the bug is fixed. This might be a subversion of the intent of Jira, I dunno, but the system works for us. A new requirement: we need that a clone has the same workflow status as the original issue.
Cloning should lead over some checkboxes where you can select whether comments, attachments, components, versions, due dates, workflow status, usewr defined fields, etc. should be cloned, too. A must have for help desk. If you the issue is researched and found to be a bug and a nice feature enhancement, you would want the comments to be copied to the programming project for reference.
I would have several check boxes, just like link is an option. So I would have Link There will always be a reason that someone needs one combination or another, and you leave the flexibility in the user hands. We need this immediately. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Clone issue should copy comments, due dates etc.
i think that the best solution is to put some checkbox on the "clone" page, so any user can choose wether or not to copy comments