Add a create follow-up issue link which fills in values (clone an issue)

just testing the patch

link back added
uses the issue summary

This is a wonderful suggestion IMHO :) Good for managing followups to big issues.

+++ b/dreditor.user.jsundefined
@@ -2295,6 +2295,42 @@ Drupal.behaviors.dreditorIssuesFilterFormReset = function (context) {
+      var project = $('#edit-project-info-project-title').val();
+      if (project == 'Drupal core') {
+		project = 'drupal';
+	  }
+      var w = window.open('//drupal.org/node/add/project-issue/' + project, '_blank');

Is there some info that is not the title in the page? Most project machine names do not equal their name :/

#7 fixed, thanks for the tip

for easy testing a patched version

Works as advertised!

#12 + #14 the page is taking too long to load, in the script is a timeout of 3 seconds, attached a new version but needs testing in different browsers.

Works great! Thanks :) I won't mark RTBC because there is a "needs accessibility review" tag. But... would be awesome if this got in asap.

Ok... it would be *great* to have the tags *not* be collapsed because we won't often want to change these and we forget because they are collapsed ;) 3 of us had this issue so far in the sprint today. Thanks!

Should work

Yeah! Tested and works great :) Thanks!

New patch and interdiff with the suggested changes by YesCT in #21

#22 Thanks, back to RTBC

#24 I mostly just change the title, maybe we should look into adding settings to dreditor, but I rather do this in a separate issue.

If more people wants the title blanked out, I don't mind changing it.

Perhaps prepend "[Follow-up]: " to the title by default

I think either empty or #26 suggestion for title is fine.

Removed the prefilled title. Made the page scroll to the fields by using url hash. Focused on title. Removed issue summary since there will be a button for that and is not always needed. Let me know if we need to work on this more or if it's RTBC.

New position of button

+++ b/dreditor.user.jsundefined
@@ -2715,6 +2715,41 @@ Drupal.behaviors.dreditorIssuesFilterFormReset = function (context) {
+      var w = window.open('//drupal.org/node/add/project-issue/' + project + '#edit-rid-wrapper', '_blank');

Here you are using a protocol relative URL ...

+++ b/dreditor.user.jsundefined
@@ -2715,6 +2715,41 @@ Drupal.behaviors.dreditorIssuesFilterFormReset = function (context) {
+            var matches = window.location.href.match('^https?://drupal.org/node/([0-9]+)');

... and here we have HTTPS only, is there are reason for that? Just asking :)

Thanks for taking a look @yannickoo. The RegEx there actually makes the s in https optional by adding a question mark after it.

Making the docblock for this behavior a bit clearer and (hopefully) fixing up indentation - no functional changes.

Tested and working well on Chrome and Firefox.

We could use HTTPS in every place because drupal.org redirects you automatically to the HTTPS version.

#35 We do now, but nobody knows what the future will bring, although I think this will not change, better to support all protocols.

Screenshot looks neat

I'm happy with #32 and #34.

Thanks everyone! Committed 89418ac :)