Unable to clear Salary & Compensation fields after initial save and missing "Negotiable" option

[ntuan2502]

Summary

In the Job Settings under Salary & Compensation, while the fields can be left empty during the first save, once values (Minimum/Maximum Salary, etc.) have been entered and saved, they cannot be cleared back to an empty state. Additionally, there is a need for a "Negotiable" option to bypass mandatory salary ranges.

Steps to reproduce

1. Go to Job menu and select a specific Job.
2. Navigate to Settings -> Salary & Compensation.
3. (Optional) Note that fields can be saved while empty initially.
4. Enter values for: Minimum Salary, Maximum Salary, Currency, and Pay Period.
5. Click Save (Data is saved successfully).
6. Attempt to delete all values in these fields to make them empty again.
7. Click Save.
8. Observe that the fields either restore the previous values or fail to update to an empty state.

Expected behavior

1. Users should be able to clear previously saved salary information and return the fields to an empty state.
2. A "Negotiable" checkbox/toggle should be implemented.
   • When checked: It should allow saving without numerical salary values and potentially hide the Min/Max input fields.
   • When unchecked: It allows users to input specific salary ranges.

Actual behavior

1. The system allows saving empty fields only if they have never been filled. Once data is saved, it becomes "permanent" in the UI/Database and cannot be reset to null/empty through the interface.
2. There is currently no "Negotiable" status, forcing users to provide specific numbers even if the salary is not yet fixed.

Version / commit

No response

Environment

No response

Logs / screenshots

[ntuan2502]

I also noticed that a similar issue occurs with the Listing Expiry field. Once an expiry date has been set and saved, it cannot be cleared or reset to an empty state, which is consistent with the behavior observed in the Salary & Compensation section.

[ntuan2502]

Additional Observations & UI Inconsistencies:

I noticed several discrepancies between the "New Job" creation flow and the "Job Settings" page:

1. Missing Field: The "Experience level" field is present during the job creation process but is missing from the Job Settings page, making it impossible to update after the job is created.
2. Inconsistent Labeling: Several fields refer to the same data but use different labels, which causes confusion:
   • Title (Settings) vs. Job title (Creation)
   • Location (Settings) vs. Office location (Creation)
   • Employment Type (Settings) vs. Workplace type (Creation)
   • Work arrangement (Settings) vs. Remote status (Creation)

Recommendation:
I suggest implementing an i18n (internationalization) framework as soon as possible to standardize these labels across the entire application and prevent typing inconsistencies. Once the i18n structure is in place, I would be more than happy to contribute by providing a native language translation for the app.

---

[JoachimLK]

Thank you for the thorough bug report and for the excellent follow-up observations from the community, these were very helpful in identifying the full scope of the problem!

All issues have been resolved in PR #157:

Fields unable to be cleared — The root cause was that the PATCH handler only sent salary fields when they were non-empty, so clearing them never reached the database. All salary and validThrough fields now always send their value (including null) to explicitly clear the DB column. The same fix applies to the listing expiry date, as noted in the comments.

"Negotiable" option: A salaryNegotiable toggle has been added to the Salary & Compensation section. When enabled, the min/max/currency/period fields are hidden and cleared, and the job is saved with null salary values. The database schema has been updated with a new migration.

Experience Level field missing from Settings: The Experience Level field is now present on the Job Settings page, consistent with the creation flow. The DB schema has been updated accordingly.

Thank you also for the labeling inconsistency observations, those are tracked separately as part of the i18n groundwork 👍