Awesome, thanks a lot for the super-fast turnaround!

The work is not "lost" since it's in the history indeed. It's super annoying to fix things this way though, and it implies you already know some contents has disappeared. In the 2 occurrences that I know of after a few days with Phab at our org with a subset of people, they were discovered randomly, so there might be others.

I think matching the new value is sufficient for already improved task routing e.g. status changes to "Verify" and project contains "iOS", assign to iOS QA.

We lost some edits again yesterday because of this issue due to another set of people happening to touch the same page roughly at the same time like in T5060.

Fair enough, that makes sense.

Thanks for the feedback. I was aware of the Celerity but thought it was a bit overkilled. I'm glad D9148 improved things though.

It's not so much about reordering the existing fields which are in a fine order but about "inserting" custom fields in between them.

I can only agree, it would be much better to have everything in Herald. We'll give it a shot with an event observer until these features land.

Search is enabled for our custom fields but they are of the pop-up menu kind. You are correct that search works.

IMO at the minimum, there should be a warning in the search results saying such and such terms have been ignored as shorter than 4 characters.

Yep, fixed!

This is about a year old, any chance this can be implemented soon using hashtag? It would be very nice to have.

Here's our concrete use case:

• We want to enforce classifications of tasks at a high level in "components" (iOS, Android, Server, PR, Marketing...) and "types" (Task, Bug, Feature...).
• I created 2 "select" custom fields which work fine (and are searchable)
• We need to have a default assignee per component: my solution was to use a Herald rule for that: if task has component X, and assignee is empty, set assignee to Y

In Maniphest today, when grouping query results by priority you can drag & drop tasks between groups and adjust priorities accordingly which is quite convenient.

Be able to have a rule execute when the status changes.