feat(projects): New Project form exposes status / dates / manager (PMS-361) #231

Merged

YousifShkara merged 1 commit from fix/pms-361-new-project-form-exposes-edit-fields into main

2026-06-16 23:31:45 +02:00

YousifShkara commented

2026-06-16 23:31:33 +02:00

Owner

The Edit Project modal already lets the user set status, start_date, target_end_date, and project_manager_id, but the New Project form only carried name, company, description, and the two budget fields, so every project was born as "planning" with no schedule and needed a follow-up edit just to flip it to "active" or assign an owner. Brought the Create form to field-parity with the Edit modal: added a Status Select (defaulting to "planning" so the prior implicit default is preserved), a Project Manager Select fed by /auth/users, and the two DateField rows matching the Edit modal's layout. Submit threads each through the POST body, with the optional fields only sent when non-empty so the server side doesn't have to special-case empty-string-as-uuid coercion. The server-side CreateProjectRequest already accepts every one of these (see PR #278 on mokosh-server which added the missing actual_end_date field; the four fields surfaced here have been server-supported for longer).

#PMS-361

The Edit Project modal already lets the user set status, start_date, target_end_date, and project_manager_id, but the New Project form only carried name, company, description, and the two budget fields, so every project was born as "planning" with no schedule and needed a follow-up edit just to flip it to "active" or assign an owner. Brought the Create form to field-parity with the Edit modal: added a Status Select (defaulting to "planning" so the prior implicit default is preserved), a Project Manager Select fed by `/auth/users`, and the two DateField rows matching the Edit modal's layout. Submit threads each through the POST body, with the optional fields only sent when non-empty so the server side doesn't have to special-case empty-string-as-uuid coercion. The server-side `CreateProjectRequest` already accepts every one of these (see PR #278 on mokosh-server which added the missing `actual_end_date` field; the four fields surfaced here have been server-supported for longer). #PMS-361

YousifShkara self-assigned this

2026-06-16 23:31:33 +02:00

YousifShkara added 1 commit

2026-06-16 23:31:33 +02:00

feat(projects): New Project form exposes status / dates / manager (PMS-361)

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / clippy + fmt + tests (pull_request) Successful in 2m33s

Details

877f18d013

The Edit Project modal already lets the user set status, start_date, target_end_date, and project_manager_id, but the New Project form only carried name, company, description, and the two budget fields, so every project was born as "planning" with no schedule and needed a follow-up edit just to flip it to "active" or assign an owner. Brought the Create form to field-parity with the Edit modal: added a Status Select (defaulting to "planning" so the prior implicit default is preserved), a Project Manager Select fed by `/auth/users`, and the two DateField rows matching the Edit modal's layout. Submit threads each through the POST body, with the optional fields only sent when non-empty so the server side doesn't have to special-case empty-string-as-uuid coercion. The server-side `CreateProjectRequest` already accepts every one of these (see PR #278 on mokosh-server which added the missing `actual_end_date` field; the four fields surfaced here have been server-supported for longer).

#PMS-361

YousifShkara merged commit cf5c120940 into main

2026-06-16 23:31:45 +02:00

YousifShkara deleted branch fix/pms-361-new-project-form-exposes-edit-fields

2026-06-16 23:31:45 +02:00

YousifShkara referenced this pull request from a commit

2026-06-16 23:31:47 +02:00

Merge pull request 'feat(projects): New Project form exposes status / dates / manager (PMS-361)' (#231) from fix/pms-361-new-project-form-exposes-edit-fields into main