>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2151041. --> Reported by: [xjm](https://www.drupal.org/user/65776) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <ul> <li>Currently, all existing change record nodes are automatically listed at (e.g.) <a href="https://drupal.org/list-changes/drupal">https://drupal.org/list-changes/drupal</a>.</li> <li>Starting soon, it will be required to draft a change records for relevant core issues <em>before</em> the patch for a given issue is committed.</li> <li>Having "draft" change records for API changes that are not yet complete will confuse developers.</li> <li>So, draft change records should not be listed on <a href="https://drupal.org/list-changes/drupal">https://drupal.org/list-changes/drupal</a>, but should behave like normal change records otherwise. </li> </ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li> <p>Add a <em>Change record status</em> field to the change record content type.<br> <img src="https://drupal.org/files/issues/create_change_record_0.png"></p> </li> <li> <p>Add three child tabs to the change record listing page: Published, Draft, and Review. "Published" and "Draft" are published and draft change records, respectively. "Review" are draft change records associated with fixed or closed (fixed) issues.</p> <h4>Published (default)</h4> <p><img src="https://www.drupal.org/files/issues/published_tab.png"></p> <h4>Draft</h4> <p><img src="https://www.drupal.org/files/issues/draft_tab.png"></p> <h4>Review</h4> <p><img src="https://www.drupal.org/files/issues/review_tab.png"></p> </li> <li> <p>Make the <em>Change record status</em> field default to "Draft change". When a draft change record is created, add a message informing the user where the draft change records can be listed.</p> <p><img src="https://drupal.org/files/issues/initially_draft.png"></p> </li> <li> <p>When the change record and its issue are ready, the field can be checked ("Published") and the change record will appear in the default list. The node creation date is also updated when the change record is published.</p> <p><img src="https://drupal.org/files/issues/now_published.png"></p> </li> <li> </li> <li> <p>Update existing change records to a "published" value.</p> </li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Attached patch implements the proposed resolution. You can see the new feature in action at:<br> <a href="http://project-issues-drupal.redesign.devdrupal.org/list-changes/drupal">http://project-issues-drupal.redesign.devdrupal.org/list-changes/drupal</a><br> <a href="http://project-issues-drupal.redesign.devdrupal.org/node/2143392">http://project-issues-drupal.redesign.devdrupal.org/node/2143392</a><br> <a href="http://project-issues-drupal.redesign.devdrupal.org/node/2143391">http://project-issues-drupal.redesign.devdrupal.org/node/2143391</a><br> <a href="http://project-issues-drupal.redesign.devdrupal.org/node/add/changenotice">http://project-issues-drupal.redesign.devdrupal.org/node/add/changenotice</a><br> Test site credentials: drupal/drupal for the http auth; testable/testable for the site user</p> <h4>Deployment instructions</h4> <ol> <li>After updating the feature, run <code>update.php</code> to set the change record status field value on all existing change records.</li> <li>At <code>admin/structure/block</code>, configure the <strong>Issue page draft API changes</strong> block identically to the <strong>Change records for issue page</strong> block (weight, region, visibility settings, etc.)</li> <li>Announce the new feature and policy change on g.d.o/core.</li> </ol> > Related issue: [Issue #2173425](https://www.drupal.org/node/2173425) > Related issue: [Issue #2292469](https://www.drupal.org/node/2292469)