Except maybe title and description which would always be at the top and bottom if that creates UX problems.
|Open||None||T5786 Separate Differential reviewer warnings from the reviewers field|
|Open||None||T7443 Include full link to Maniphest tasks in commit messages|
|Resolved||fabe||T8295 Show which commits were included in a merge commit in Herald emails|
|Open||None||T6030 Allow CustomFields to specify additional options (like "required") configurable in `<application>.fields`|
|Wontfix||joshuaspence||T5011 Convert builtin fields in Maniphest to CustomField|
|Resolved||btrahan||T5245 Migrate Maniphest Projects to use edge infrastructure|
Maniphest is only mostly-transitioned to the CustomFields and ApplicationTransactions infrastructure, and still has some stuff like this at the edges.
This is essentially an infrastructure project -- complete the transition to CustomFields by getting the native fields on the common infrastructure.
Out of curiosity, which fields do you want to reorder?
Phabricator's infrastructure has evolved a lot and CustomFields now serve a smaller role than they once did -- roughly, just custom fields. Later generation stuff (particularly EditEngine) feels better factored, and has reduced the responsibility of CustomFields.
Phabricator's task view UI is now less of a list of properties than it once was, and tasks don't really have any orderable fields by default anymore, so I think the original ordering motivation is sort of moot. With EditEngine, fields are fully reorderable on the edit form.
Overall, I don't think there's any real product or infrastructure motivation for this anymore. If you have one, file a new task per Contributing Feature Requests so we can get a more modern use case.