personally, i wish you could disable the now-required taxonomy for projects, since in many cases, it's just not relevent (e.g. sites that only exist to support a single project, etc). however, if we're going to have them, we might as well use them. ;) in particular, when you're on the page to query issues (e.g. /project/issue), it'd be nice if the drop-down box to select the project was sorted by taxonomy, just like the one when you're being asked to select the project on the first page of the "create issue" form. i haven't had a chance to look into this yet to see how hard it would be, but i figured i'd post an issue for it in case anyone else is inspired to work on it and commit it.
thanks,
-derek
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | project_select_by_taxonomy.patch | 1.52 KB | dww |
Comments
Comment #1
dwwwow, http://drupal.org/node/74995 is just helping me find/fix *all* the bugs. ;)
the problem is that in a few places when constructing the set of options for a project select field, we just don't use
project_projects_select_options()like we should. the fix will be easy. stay tuned.Comment #2
dwwthis patch would apply against the current project/issue.inc, but it's really intended to go into project_issue/project.inc. i generated it from the local directory, so the same patch applies easily to either one. ;)
anyway, as soon as http://drupal.org/node/74995 is resolved, i'm planning to commit this...
Comment #3
dwwapplied to HEAD and 4.7. i notice that this change also fixes a bug, since previously we were presenting projects where the issue tracker was disabled. this also gets rid of some more queries where we were testing the moderate bit. i notice that
project_projects_select_options()does not query against moderate, even in 4.7. i'm going to figure out if that should be changed. if so, i'll just open a new issue about it.Comment #4
(not verified) commented