Decouple default workflow status from Kanban/pivot column order / Allow default status for new records

What is the challenge?

• The order of statuses in a workflow controls two unrelated things at once: which status is pre-selected as the default when a new record is created, and the left-to-right column order in Kanban boards and pivot grid reports. Because both are driven by the same ordered list, you can't change one without changing the other.

• For example, if "Achieved" sits first in a workflow so it anchors the first column of a Kanban/pivot report, it also becomes the default status assigned to every new record created against that workflow — even when a different status (e.g. "Later") would make a more sensible default.

We have this issue specifically for Initiatives where we'd like to show the Roadmap with columns Achieved - Now - Next - Later as that is how stakeholders naturally expect it (Done items on the left side).

What is the impact?

• Teams sharing one workflow across multiple Kanban boards or pivot grid reports can't set a sensible default status without shifting every board and report that depends on the existing column order. The only workaround is creating a separate custom workflow, which fragments reporting and doesn't scale when several teams want the same fix.

Describe your idea.

• Let the default status for new records be configured independently of the status order used for Kanban/pivot column layout. For example, add a "default status" flag on the workflow, decoupled from position in the ordered status list, so column order in boards and reports stays unaffected by which status is marked default.