horilla
horilla copied to clipboard
horilla-opensource
Job Position to multiple departmets dosent work
Bug Report
Description
Hi guys, i tried to make multiple departments, after that, i created the same job position for multiple departments.
Steps to Reproduce
- Create 2 departments
- Create 1 job position for the first department (Example: Manager -> Sales Dep)
- Create the same job position for different department (Example: Manager -> HR Dep)
Expected Behavior
To create the same job position for multiple departments.
Actual Behavior
Job Position with this Job position already exists.
Environment
The latest version.
Possible Solution
[If you have any ideas or suggestions on how to fix the issue, feel free to provide them here. This is optional.]
Hi @zgurea1 , The solution is updated in the latest commit. Please check and let us know if you face any issues.
With Regards, Team Horilla
@horilla-opensource hi, its not working, if i duplicate the same job position in department it not showing error.
DETAIL: Key (job_position)=(Specialist principal) already exists.
Internal Server Error: /settings/job-position-creation/ Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "base_jobposition_job_position_key" DETAIL: Key (job_position)=(Specialist principal) already exists.
Hi @zgurea1 , Can you try by creating another record with new data and confirm whether its working?
With Regards, Team Horilla
@horilla-opensource I mentioned to you the same error, also I have sent ss of the mistakes with the editable code that you had provided
Hi @sharukhkhan234 , Were you able to work around with it?
With Regards, Team Horilla
Hi @sharukhkhan234 , We are closing this issue due to inactivity. It seems that there hasn't been any recent activity or discussion, and we believe it may have been resolved or is no longer relevant. If you feel this issue is still important and should be addressed, please feel free to reopen it or create a new issue with updated details.
With Regards, Team Horilla