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

SkillZone view - Inconsistent data #445

Open
Daavide opened this issue Dec 30, 2024 · 1 comment
Open

SkillZone view - Inconsistent data #445

Daavide opened this issue Dec 30, 2024 · 1 comment

Comments

@Daavide
Copy link

Daavide commented Dec 30, 2024

Bug Report

Hi,
I noticed a problem in the Skill Zone view.

Sometimes, when adding a candidate to a skill zone, the record is created in the database (sqlite) but is not displayed on the webpage.

It is visible also in the "add skillzone" form from candidate view.

I noticed this error when starting the application that may be related:

UnorderedObjectListWarning: Pagination may yield inconsistent results with an unorde
red object_list: <class 'recruitment.models.SkillZoneCandidate'> QuerySet.

Adding screenshots:

image

image

Record in recruitment_skillzonecandidate table:

sqlite> select * from recruitment_skillzonecandidate where "candidate_id_id" = 1;
25|2024-12-30 16:11:56.227619|1|xxx|2024-12-30|1|7|7|28

Record in recruitment_skillzone table:

select * from recruitment_skillzone;
[...]
28|2024-12-30 16:11:45.121059|1|test|test|1|7|7

@horilla-opensource
Copy link
Owner

Hi @Daavide ,

Thank you for reporting this issue.

We reviewed the behavior and conducted tests by creating a Skill Zone, adding a candidate to the Skill Zone from the Recruitment Pipeline page, and then verifying the candidate's visibility on the Skill Zone page. In our testing, the candidate appeared as expected.

However, please ensure that the Recruitment, Candidate, and Skill Zone are all associated with the same company, as data may not display correctly if they belong to different companies due to company-specific filtering. If the issue persists, we would appreciate it if you could provide additional details, such as the exact steps to reproduce the issue, any relevant logs or screenshots, and confirmation that the entities involved are under the same company.

With Regards,
Team Horilla

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

No branches or pull requests

2 participants