Coming from

#1791872-18: [Policy, no patch] Add special tag to identify issues ready for a high level only review

Problem/Motivation

I am reporting http://drupal.org/node/1155816 to moderators because:

As I see following the core issue queue - there are many situations with a long term issues that generates a follow-up issues

Proposed resolution

And my proposal is to add into issue summary template

header

<h3 id="summary-parent">Coming from(Or part of meta issue [#123457-45])</h3>
[#123456-23]

and

footer

<h3 id="summary-related-issues">Related issues</h3>
[#345678]

<h3 id="summary-follow-up-issues">Follow up issues</h3>
#234567: creation of node-image.tpl.php or node-gallery.tpl.php - coming from [#123456-45] (point to comment born from)

Its easy and very simple to follow long term tasks

Remaining tasks

just do it

User interface changes

no

API changes

no

no

Follow up issues

no

CommentFileSizeAuthor
#4 issues-ref.png328.68 KBYesCT
#4 fields.png44.16 KBYesCT
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

podarok’s picture

Issue summary: View changes

Updated issue summary.

podarok’s picture

Issue summary: View changes

Updated issue summary.

podarok’s picture

Issue summary: View changes

Updated issue summary.

podarok’s picture

Issue summary: View changes

Updated issue summary.

podarok’s picture

Issue summary: View changes

Updated issue summary.

podarok’s picture

Category: task » feature

looks like feature request ;)

andypost’s picture

Yeah! It's realy cool to have a temple-set for the most common issue kinds

EDIT Probably after discussion this issue should be moved to webmasters queue to deploy some code to d.org and follow-up to prototype

andypost’s picture

Issue summary: View changes

Updated issue summary.

LeeHunter’s picture

Project: Documentation » Drupal.org site moderators
Component: Missing documentation » Other
Issue summary: View changes

Moving this to the webmaster's queue since it seems to be more about changing the template than changing the documentation.

YesCT’s picture

FileSize
44.16 KB
328.68 KB

I think this might be marked fixed.. or won't fix
related to the addition to issues as meta data. which might have been #2131965: add an Entity Reference Selection Handler for related issues

Examples of what we have already now:

tvn’s picture

Status: Active » Closed (won't fix)

Closing due to inactivity for a year. And also we do have related/parent/chile issues now to link follow ups to the original issue.