The interplay between project.module and feature.module on drupal.org causes confusion. We have received many feature requests attached to the "Feature" project, even though they were intended for another module, because of the name of that module. Solutions to this problem might be:

- Reworking the Project dropdown to make it clear that Feature is a module, not a type of issue
- Renaming feature.module to resolve the ambiguity
- Removing Feature from the dropdown entirely

The dropdown menu is huge and, near the end of the list, unordered (another problem), so the first approach is probably the best long-term solution.

Comments

jonbob’s picture

jonbob commented

I just discovered that http://drupal.org/node/add/project_issue/feature *defaults* to having "Feature" as the project, compounding the problem greatly.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Yes, like http://drupal.org/node/add/project_issue/mailhandler defaults to having mailhandler as a project. Every project has such default links. As the link say, you are submitting an issue related to this project... Is there a link anywhere to submit a feature via the feature project?

Goba

jonbob’s picture

jonbob commented

Well, you can get to this URL by selecting "create content" -> "issue" -> "feature request" in the site navigation menu. It appears that the same URL scheme is being used for two different purposes, causing a conflict in this case.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

JonBob, you are right, the URL scheme used for feature requests does interfer with the feature module... This should be fixed in the project module somehow.

Kjartan’s picture

Kjartan commented
Assigned: Unassigned » Kjartan
Anonymous’s picture

(not verified) commented