How do I create a new case that looks just like an existing one (all the fields the same) so I can quickly use a case as a template for a new one?
|
51
8
|
||||
|
|
17
|
Update: I'm working on a port of Rich's bookmarklet generator script. Up-vote this question if you'd like something like it. There isn't a built-in way to clone a case to a new one, but there are several options:
(Here's the same text as above on one line in case you just want to copy it):
When you view a case and click the bookmarklet, it will open a new case in a new window/tab that's a clone of the case. It will include "See Case XXX" to link back to the other one. You can remove this from the URL of the bookmarklet if you want. If you click it with some text selected, that text is put in the body of the new case as well. You can create various new case bookmarklets using Rich's bookmarklet generator, but note that the site is not SSL so your username and password will go in cleartext.
See also this blog post about creating cases with field values pre-filled: http://blog.fogcreek.com/a-halloween-treat/ |
|||||||||||||||||
|
|
3
|
I wrote an app which allows you to do this (source available). http://www.fogcreek.com/fogbugz/blog/post/CaseCloner-for-batch-creating-cases-in-FogBugz.aspx Just remember, the URL field it wants is the actual url to the api, so something like |
|||
|
|
|
2
|
I've just converted this into a 'customization' (Settings > Customizations) so it will add a link to the page to do it rather than as a bookmarklet.
I've also added a custom field to this using the following to get the field, and adding the string to the url:
|
|||
|
|
0
|
I also started with 'WTF, no clone case here?', but after some thinking we rather use the bug hierarchy. In our work clone is needed because the same bug is present on different releases, and patching, especially release process is different. As the parent item is just one click away it serves well, and information is not duplicated. The only problem was the Release notes, for which I wrote a simple tool that is enhanced version of FB's release notes view. We use special words in RN, 'NA' fir intentionally empty, 'Parent' to find the note in the parent bug. So that information is not duplicated either, and everyone gets the one true version of the text. :) So I no longer need Bugzilla-like cloning. OTOH 'template' bugs would be great to have. Snippets can be used for the text part, and certainly it is possible to post the bug with an external tool in a templated state, but that all is hassle. 'New Case' could have a dropdown to pick a template from a list. A template just a selection of fields and their initial value. |
||
|
|