Issue submission form fields seems to me as a duplicate of How to make an issue report and Adding tags to issues.

I suggest archiving and unpublishing, and moving its child page "Status settings for an issue" up to the same level as "How to make an issue report".

Comments

heyitspython’s picture

This thread is now over a year old, but I took a look at this, and I think maybe what's going on here is that the titles are a little confusing and there is some overlap. I think "Making an issue report" goes over more tips and tricks, where as Issue submission form fields really just breaks down what the fields purpose is.

For example, with regard to the title field, we see in "Issue submission form fields" the following very dry and straight forward text:
"Issue Title definition:
A descriptive heading for the issue."

Whereas with "Making an issue report" we see more illustration of how this field should be used, and what makes an appropriate issue title:
"Title: you want your title to be descriptive and concise. Compare these two titles:

SITE BROKEN YOU MUST FIX NOW!!!111!!

and

Admin-Modules Page Blank After Installing Module Foo

"

And it goes even further over the course of two more paragraphs, but to present the point, the above example is sufficient.

I propose we separate the two into a more detailed "Guidelines for making an issue report" (or, alternatively, "Tips for making an issue report") page and "Issue submission form fields" for quick and easy referencing. So there would be some transferral of information from one to the other and some cleaning up. Then, we could house the "Issue submission form fields" underneth the "Making an issue report" menu item. As the first child.

As for "Adding tags to issues," it seems to me that this (and its children) should live under the "Making an issue report" menu item.

Thoughts?

heyitspython’s picture

Also, I'm happy to do all this, but I wanted to get some buy-in from folks in the queue if anybody's out there :)

heyitspython’s picture

Assigned: Unassigned » heyitspython
batigolix’s picture

Sounds good. Go for it.

The pages should contain clear links to each other. It is not enough that they related as children - parents in the book outline.

Try also embedding & removing the comments on http://drupal.org/node/1023102 and http://drupal.org/node/73179

heyitspython’s picture

Issue submission form fields is ready for review.
http://drupal.org/node/314328

Leaving this as active until I can get Tips for making a good issue report finished out.

batigolix, I don't believe I have the ability to remove the comments below on the two nodes you listed-- unless I'm missing something.

heyitspython’s picture

Status: Active » Needs review

OK-- Tips for making a good issue report is ready too.
http://drupal.org/node/73179

Repeating for ease of access--
Issue submission form fields is ready for review.
http://drupal.org/node/314328

apaderno’s picture