Feature: Add 'Status' field on new task creation

[thesoundhead]

I propose the following:

When creating a new task, there is currently no Status field in the edit window. Sometimes you are already working on a task and then want to create it in the board, so the Status is not inherently Open, but In Progress (or something else). Adding a Status field just like when editing a task seems reasonable to solve this. Furthermore, this would lead to a more consistent UX/UI.

[ulsklyc]

You read the code correctly without seeing it. The task form builds the status field behind an isEdit check:

${isEdit ? `
  <div class="form-group">
    <label class="label" for="task-status">${t('tasks.statusLabel')}</label>
    ...
` : ''}

So the field is not missing by design, it is simply gated to the edit case - and your example (writing down something you have already started) is the case that gate does not survive. The server side is ready: POST /tasks already accepts a status, the form just never sends one.

The one thing worth getting right is the default. It has to stay the first status, so that creating a task without touching the field behaves exactly as it does today - the field is an option, not a new decision everyone has to make on every task.

Agreed on the consistency argument too: two versions of the same form that differ in one field is the kind of difference nobody can predict from the outside.

[ulsklyc]

Shipped in v2.60.0, @thesoundhead.

A new task can now be created as "in progress" or "done" straight away - the field moved out of the edit-only branch, so writing down something you had already started no longer takes two steps.

The second half of this turned out to be on the server, and it was the more unpleasant one: POST /tasks had been validating a supplied status against the allowed values and then never writing it. A value that is checked and silently discarded is the worse of both, so the field is now actually stored, and it runs through the same transition handling as editing does - points and completion timestamps behave the same whether you set the status at creation or afterwards.