Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Route field in Job Opening page is obsolete #260

Closed
mabdeljawwad opened this issue Jan 14, 2023 · 1 comment · Fixed by #835
Closed

[bug] Route field in Job Opening page is obsolete #260

mabdeljawwad opened this issue Jan 14, 2023 · 1 comment · Fixed by #835

Comments

@mabdeljawwad
Copy link

mabdeljawwad commented Jan 14, 2023

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

Screenshot 2023-01-14 at 6 35 15 PM

+---------------------+---------------------+----------------+---------------------+
| 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)

@niraj2477
Copy link
Contributor

niraj2477 commented Jul 24, 2023

Check is already there, looks like it is getting overridden from somewhere else. Looking into the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants