You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Information about bug
When trying to create a Job Opening under the Recruitment, the user may publish the post on the Web Site by ticking the [Publish on website] checkbox. Once checked, the user is presented with two new data fields:
Route
Job Application Route
Any value filled by the user in the [Route] field is overlooked. The system fills the tabJob Opening.route field with the job opening title replacing space characters with dashes.
To fix this, either:
Respect user input of [Route] field and save that to database, or
Hide [Route] data field if design dictates using system-assigned routes
Information about bug
When trying to create a Job Opening under the Recruitment, the user may publish the post on the Web Site by ticking the [Publish on website] checkbox. Once checked, the user is presented with two new data fields:
Route
Job Application Route
Any value filled by the user in the [Route] field is overlooked. The system fills the tabJob Opening.route field with the job opening title replacing space characters with dashes.
To fix this, either:
Respect user input of [Route] field and save that to database, or
Hide [Route] data field if design dictates using system-assigned routes
+---------------------+---------------------+----------------+---------------------+
| name | job_title | designation | route |
+---------------------+---------------------+----------------+---------------------+
| foreman | Foreman | Superintendant | foreman |
| senior-mep-engineer | Senior MEP Engineer | Engineer | senior-mep-engineer |
+---------------------+---------------------+----------------+---------------------+
Version info
ERPNext: v14.12.0 (version-14)
Frappe Framework: v14.21.1 (version-14)
Frappe Helper: v0.2.8 (master)
Frappe HR: v1.0.0 (develop)
Payments: v0.0.1 (develop)
The text was updated successfully, but these errors were encountered: