Problem/Motivation

The "component" field in the Drupal core issue queue has an enormous number of options in it.

It is especially difficult for new users (see #2785735-34: [policy, no patch] Agile process for bigger changes in core (Part A: Ideation)) but since it's a required field you are currently forced to pick something even if you don't know enough about Drupal core to be able to intelligently do that.

Proposed resolution

Add a new component (probably called "unknown") and make that the default choice. This allows newcomers to create an issue without having to open the component dropdown at all if they don't want to. Someone else with more knowledge can always categorize the "unknown" issues later.

If we put this new default component at the top of the list, that will also improve the frequently-encountered situation where if you comment on an issue that is assigned to a no-longer-existing component, it randomly gets assigned to the "ajax system" component on save. (Going forward it would get assigned to "unknown" instead, which makes more sense.)

Remaining tasks

I believe this can be done via the Drupal.org user interface by anyone with permission to edit the Drupal core project node (e.g. core committers).

So we just need to decide we want to do it, then do it.

This issue affects all Drupal core versions, but I filed it against Drupal 8 for lack of a better place.

Comments

David_Rothstein created an issue. See original summary.

David_Rothstein’s picture

Status: Active » Needs review

Moving to "needs review" since as noted above there shouldn't be any code changes needed for this.

heddn’s picture

+1

cilefen’s picture

Fabianx’s picture

+1 to doing this

dawehner’s picture

Could we maybe move "other" to the top and name it different (other/unknown) ? Conceptually other and unknown feels kinda similar.

vijaycs85’s picture

+1. I always end up spending time thinking/looking around this field to get a proper category and end up setting as base system. As @dawehner mentioned in #6 we already have 'other' which can be reused? Only down side is, we need to keep an eye on this value and change them to different category, which I believe better than creating issues in wrong category and no one notice.

jmuzz’s picture

Status: Needs review » Reviewed & tested by the community

+1 for the addition of a default component and for @dawehner's suggestion to reuse 'other'.

RTBCing because there are some other +1's and no objections.

Fabianx’s picture

Yes, RTBC + 1

David_Rothstein’s picture

Status: Reviewed & tested by the community » Needs review

I'm pretty sure that changing the label of an existing category will orphan all issues that have that category (in other words, everything currently at https://www.drupal.org/project/issues/drupal?component=other would become orphaned and would no longer appear on that or any other per-component list).

Also "other" and "unknown" aren't necessarily the same thing - if you look through the above list I think you can find many issues that are legitimately "other".

So I would suggest sticking with the original proposal of just creating a new category for "unknown".... It doesn't preclude merging the two categories at some point later, if "other" turns out to be useless.

jmuzz’s picture

changing the label of an existing category will orphan all issues that have that category

I tested this and can confirm.

I can see benefits for keeping them separate too. You'd know which ones could likely be categorized and which ones probably won't fit into any of the categories.

cilefen’s picture

Having read #10 and #11, those are persuasive points.

xjm’s picture

I think having a default component is a fantastic idea; however, I don't want to add a third vague component in addition to "other" and "base system".

The concern about orphaned issues can be easily addressed by an issue component migration, for which we could repurpose @drumm's branch update script, so if a new component name is the best choice I don't think we should rule that out.

Fabianx’s picture

Title: Add a default component to the Drupal core issue queue » Add a default component 'Unknown' to the Drupal core issue queue

#13: Base system might feel vague to new comers, but does actually make sense for things like DrupalKernel or Class Loader or bootstrap or other very 'core' and 'base' things.

And David is right that Unknown is very different from 'Other', which is just for everything that does not really fit a component in the list, but specifically actionable to put to a real component.

In that 'Unknown' is more a workflow step and actionable like 'Needs reroll' or similar:

- Not assigned => Unknown
- Not assigned => [real component]
- Unknown => [real component]

Therefore my new vote goes to add 'Unknown' as the default component and we can triage it then nicely.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.