Active
Project:
Project issue tracking
Version:
7.x-2.x-dev
Component:
Issues
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2006 at 15:04 UTC
Updated:
27 Apr 2012 at 19:48 UTC
Thanks for a great module. I'm using this as a issue tracking module for several non-drupal projects now.
I'd like to see component not be required. For small projects, it doesn't seem to provide much value, and it gets in the way of users submitting issues, cause they often don't know what to put here.
If I were to write module this from scratch now, I think "component" should be implemented as a taxonomy term. Then the views module would be able to tap into it as well :).
Comments
Comment #1
dwwi'd be in favor of making component optional in some way. i'd have to think about making it a taxonomy -- that could get impossibly hard to deal with on a huge site like drupal.org with hundreds of unique projects, since each project gets its own namespace for components.
feel free to submit patches and i'll review/comment on them.
thanks,
-derek
Comment #2
dwwalso, keep in mind that component can already be used to filter issues via the advanced search (e.g. http://drupal.org/project/issues/search/signup) and that it should be put in the default query interface, too (http://drupal.org/node/65336).
that said, long term, it'd still be nice to re-consider how component actually works.
Comment #3
aclight commentedI read this and the first thing I thought of was to just edit the components for a project and delete them all. When I then went to try and create an issue for that project, I had two choices in the component menu:
1.
2.
That's right, line 2 was just completely empty.
When I tried to submit the issue with either of these selected as the component, I got an error telling me that I didn't pick a valid component.
Since we don't prevent a project's maintainer from removing all of the components, we need to allow issues to be submitted without components.
Or, we need to prevent maintainers from removing all components from a project.
Comment #4
dwwYup, component needs better validation and/or logic to deal with cases like this. See also #140989: Renaming components is unsafe.
Comment #5
webchickThis is actually still an issue in the latest 7.x-2.x code. :)
The field isn't required on Projects, but it is on issues.