Add a new status 'Needs architectural review' for core issues

1. There's no way to add a status for a single project. All status values (at least in project_issue) are site-wide.
2. To add another allowed value for d.o, we could just click it together in the UI, but the proper way would be to patch drupalorg/drupalorg_issues/drupalorg_issues.features.field_base.inc.
3. I doubt there's much desire among the DA infra team to be putting any more effort into the legacy project_issue world with the imminent move to GitLab issues.
4. Adding the new allowed value is only 1 small piece of the required work for this effort. We'd also have to update documentation (e.g. https://www.drupal.org/docs/develop/issues/fields-and-other-parts-of-an-... → ), perhaps tutorials, etc.

All of this is why I proposed a new 'Needs architectural review' issue tag, not a status, at #1791872-97: [Policy, no patch] Rethink Drupal core's code quality review process → . 😅

@dww, thanks.

Given that, can you explain how to add a special tag? I found Maintaining issue tags → which allows edit and delete, not creating a tag.

Using any previously-unnamed tag when updating the issue creates that tag as the issue is saved. From there, edit the tag.

I think I wasn't clear. I meant how to make special tag → so that a description can be added. There are tags in use that do not appear on the special tags page.

Any issue tag can be edited to add a description to make it “special” using the links at https://www.drupal.org/drupalorg/docs/maintenance/maintaining-issue-tags →

@drumm, thanks! I clearly misread Maintaining issue tags → . I have added the new tag with a description.

Automatically closed - issue fixed for 2 weeks with no activity.