Job Creation Flow: Navigation stuck after completion, premature validation, and incorrect "Back" redirect

[ntuan2502]

Summary

I found three main issues regarding the Job Creation UX:

1. After completing a job (Save Draft or Publish), the "New Job" button in the navbar does not trigger a fresh creation flow.
2. The "Job title" field shows a "Title is required" error immediately on page load before any interaction.
3. The "Back to Jobs" link redirects to /dashboard instead of the correct /dashboard/jobs page.

Steps to reproduce

Issue 1: Navbar "New Job" button is stuck

1. Navigate to /dashboard/jobs/new.
2. Complete the flow by clicking "Save draft" or "Publish".
3. While still on the success/finished state, click the "New Job" button on the top navbar.
4. Observe that the page stays at the current state and does not return to Step 1 of a fresh job creation.

Issue 2: Premature Validation

1. Open the "New Job" page (Step 1).
2. Observe that the "Job title" field already displays the error message "Title is required" despite the form being pristine.

Issue 3: Incorrect Redirection

1. On the "New Job" page, click the "Back to Jobs" button at the top left.
2. Observe that the application redirects to /dashboard.

Expected behavior

1. Clicking "New Job" in the navbar should always initiate a brand new creation cycle (resetting to Step 1), even if the user just finished creating a previous job.
2. The "Title is required" error should only be triggered after the user interacts with the input (on blur) or attempts to proceed to the next step.
3. The "Back to Jobs" button should redirect to the job listing page: /dashboard/jobs.

Actual behavior

1. The "New Job" button does nothing because the URL /dashboard/jobs/new is already active. The user is forced to navigate to a different page first to "reset" the route.
2. Validation is triggered on component mount, which is distracting and confusing for users.
3. The "Back to Jobs" button sends the user to the main Dashboard home.

Version / commit

No response

Environment

No response

Logs / screenshots

[JoachimLK]

Thank you so much for this detailed and well-structured report, the clear reproduction steps made these fixes straightforward to track down and resolve!

All three issues have been addressed in PR #157:

Navbar "New Job" button stuck: The AppTopBar now emits a shared new-job-reset-signal state signal when the user clicks "New Job" while already on /dashboard/jobs/new. The page watches this signal and calls a resetState() function that resets all wizard steps, form fields, and local storage back to their initial values — giving a truly fresh creation flow every time.

Premature validation: The canGoNext computed property was previously calling validateStep1() (which had the side effect of writing to errors), causing the "Title is required" error to appear on mount. This has been replaced with a pure isStep1Valid computed property using safeParse with no side effects. Validation that populates errors is now only triggered on input blur and on explicit "Next" clicks.

Incorrect "Back to Jobs" redirect: The NuxtLink on the new job page was pointing to /dashboard. This has been corrected to /dashboard/jobs.

Thanks again for the thorough report, this is exactly the kind of feedback that makes the product better!