Add "Plan" category to categorize what is called "meta issues" in core right now
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #1815826. -->
Reported by: [Bojhan](https://www.drupal.org/user/87969)
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Since Drupal 7 we started to create [meta] issues to capture process and give an overview to those problems that cannot be solved with one issue. Now with all the initiatives there are more and more [meta] issues to follow, and no way to categorize them in your tracker. </p>
<p>The [meta] issues seem to hog up both priorities (since they are often tasks), and being able to overview all meta issues will allow you to quickly spot the major hubs of issues.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Scheduled for deployment between June 5 - 11 per change record: <a href="https://www.drupal.org/node/2501177">https://www.drupal.org/node/2501177</a></p>
> Related issue: [Issue #2226335](https://www.drupal.org/node/2226335)
> Related issue: [Issue #2503351](https://www.drupal.org/node/2503351)
> Related issue: [Issue #2504997](https://www.drupal.org/node/2504997)
issue