User-Agent: Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2.1) Gecko/20030711 When a bug involves a lot of work, we need the ability to split it up into parts that multiple engineers can work on, possibly concurrently. We need the ability, from the page in which a bug is viewed, to file a new bug in which the dependency of the existing bug on the new bug is created automatically. The operation should be exactly as the existing method for filing new bugs, except that the dependency between the parent and new bug is created automatically when the new bug is recorded in the database. The workaround is to remember the parent bug ID, create a new bug, remember the new bug ID, review either the parent or new bug explicitly, and create the dependency. But this is very cumbersome. Reproducible: Always Steps to Reproduce: 1. 2. 3.

This could be done with a button and a little bit of javascript by a well-motivated javascript hack. If you can find a workaround to bug 235937, you can select the text and then click on a link to create a new bug blocking this one. If you don't want to get that fancy, just add a button that makes a call to some javascript like.. window.open( 'enter_bug.cgi' + '?blocked=[% bug.bug_id %]' + '&product=' + escape('[% bug.product %]') + '&version=' + escape('[% bug.version %]') + '&component=' + escape('[% bug.component %]') + '&rep_platform=' + escape('[% bug.rep_platform %]') + '&op_sys=' + escape('[% bug.op_sys %]') , '_blank');

Better yet, put this in a bookmark (get rid of the newlines first) javascript:var url=location.pathname ; if (url == "/"); else if (url.charAt(url.length-1) =="/") url =".."; else url = "."; window.open(url + "/enter_bug.cgi?blocked=" + document.forms[0].id.value + "&product=" + document.forms[0].product.value + "&version=" + document.forms[0].version.value + "&component=" + document.forms[0].component.value + "&rep_platform=" + document.forms[0].rep_platform.value + "&op_sys=" + document.forms[0].product.value ,'_blank'); void 0

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.

This feature exists since Bugzilla 2.20.