Hey we actually have the same issue-- folks on the team would like to edit "owning team" from within the action menu. The problem with having to edit the task is that the UI for task editing is less discoverable and requires more clicks than the action menu -- folks are used to being able to accomplish what they need from the action menu so it frustrates them when they can't. This isn't a blocking impediment to our workflows or anything but it would be a nice-to-have UI improvement.

@epriestley so maybe this isn't the right place to leave this comment (let me know if I should create a new task?) but I'm finding this is acting in a way that seems a bit inconsistent. In particular, I added a new boolean custom field --

@chad do you need any more help reproducing this/is this fixed? I just noticed this behavior after our office upgraded to a more recent Phabricator build and it is totes annoying, I can also reproduce it with 100% reliability.

Thanks! The + thing didn't work but I've just asked the team that owns the Phabricator install to change the config setting.

Huh, our install definitely treats it as an OR. Do you know which configuration settings I should be looking at to control it?

I can reproduce it in both Chrome and Firefox on Windows, and my co-worker was having the same problem on Firefox on Mac. (I can also send a video if the problem is that my description isn't great.)

Ah -- I'm on Windows, and the keyboard arrows thing is a useful trick, thanks! but ~99% of our users are on Mac, so it doesn't really help the rest of the company as much. It would be good if the drag and drop operation just put the card on the bottom of the destination column even if there's no card directly above it, that would resolve the issue.

One problem we have that causes this is:

Specific subsets of cards. E.g. "move all resolved bugs from column "in progress" to column "done"", or "move these 30 bugs that I've selected from column "backlog" to column "in progress"".

We would like to request this feature as well, it comes up a lot for us

BTW, this is something that we'd like to request as well -- our primary use case is that our developer relations people want to get alerts whenever we fix bugs in our API so we can notify the affected developers. Do we have any sort of an ETA on this?

I talked with the dev who reported this, his take is:

See also @T600, which I think this is a duplicate of

Sounds like people prefer not having messages come from noreply, but a practical workaround is to change your phabricator email to something like <username>+<string>@<domain> e.g. ahoffer+phabricator@dropbox.com. So that's what we're advising folks to do right now if this issue is annoying them.

Ah, I figured it out. Or at least I found an old post by Euresti in which he figured it out, so it's basically the same thing. It is a configuration issue, namely that our install has messages come from <yourself>@dropbox.com and your install has them come from no-reply@phabricator.com. Gmail screws up the first case by stripping the reply-to field. I'll see about changing that setting, so I think we can mark this as resolved.

I haven't been able to reproduce it on this install but can repro it easily on our work installation :-/. I wonder if it might be a configuration issue somehow?