I'm thinking something like moving the resolve button and select to the bottom of the details column. then adding a 2nd row for moving tickets.
[resolve btn] [resolve reasons dropdown]
[move up btn] [parent board + indented sister boards dropdown]
[move down btn] [child board dropdowns]
My thoughts: I like grouping the comment and resolve buttons and dropdown together with the comment textarea. Because you can comment and resolve in the same action, I like that they are organizationally linked.
Say the bug is in an upstream repo (debian's bugzilla for example) should the textbox be a URI which could then then be polled to keep this issue up to date? when ever todo.sr.ht detects a change, this ticket would then get updated, and fire off set notifications?
Not a joke, autocomplete isn't trivial. So rather than add a huge list of js dependencies to the sr.ht suite, one for each minor feature. I'd like to know if you'd rather include jQuery, which is a nice framework that includes most of the JS needs.
Let's do this one step at a time. First the ticket move feature, and a separate ticket for autocompletion.