Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.1) Each one of them takes 30+ seconds to spin until it finally finds it's looking for. Even if entering the NID directly.
2) *If* it does, in fact, manage to find it that is. I tried entering #2124405: Take advantage of ARIA roles (specifically widget roles) to enrich the non-visual interface of Views as a related issue to #1806308: Review Views JavaScript + generic modals for accessibility, and no dice.
3) If you even *breathe* near the field when it's spinning, the AJAX lookup stops. Which means you get to start your 30+ seconds all over again! Fun!
"Easy"? solution: Just let me quickly enter NIDs there, don't bother with the big fancy AJAX lookup. Resolve them on node save when I'm waiting 30+ seconds for POST anyway. If it can't be resolved, at least the NID is there. And then my editing flow isn't disrupted for 8+ minutes waiting around for stuff to happen.
"Awesome" solution: Automatically populate the list of related issues whenever someone does [#xxxx] in one of their posts. (Requires the ability to remove related issues which does not seem to be present.)
Comments
Comment #1
dave reidAlso, you can add an issue related to itself. We should probably have some validation around that.
Comment #2
dddave commentedComment #3
klonosComment #4
klonos@Dave Reid, #1: #2132215: Validation for not allowing adding an issue relation to itself.