Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Committed the trivial fix to HEAD and D5--2, and deployed on d.o. On d6.d.o this field becomes an autocomplete text field, anyway, so the bug isn't present there.
Ok, I was going to open an issue about the project selector being an autocomplete, so I will just jump in here. I think it would be clearer what is going on on the /project/user page if the project field was a select box. I was really confused then I started typing in the box, and it started autocompleting with things that were not my projects. If the select box is unwealdy, then you need to create a new autocomplete source that only selects from the user's projects.
Comments
Comment #1
dwwCommitted the trivial fix to HEAD and D5--2, and deployed on d.o. On d6.d.o this field becomes an autocomplete text field, anyway, so the bug isn't present there.
Comment #2
starbow commentedOk, I was going to open an issue about the project selector being an autocomplete, so I will just jump in here. I think it would be clearer what is going on on the /project/user page if the project field was a select box. I was really confused then I started typing in the box, and it started autocompleting with things that were not my projects. If the select box is unwealdy, then you need to create a new autocomplete source that only selects from the user's projects.
PS. I love this functionality!
Comment #3
dww@Tao: that's a totally separate issue. ;) This issue is about the autocomplete when you're changing a project during an issue followup. The issue you're talking about is #368371: Fix "Project" exposed filters on issue queue views
Comment #4
starbow commentedOops :)
Comment #5
starbow commented