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.

Sign up for GitHub

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

Jump to bottom

Bug: incorrect applicant status behavior #1369

Open

Snorre98 opened this issue Sep 16, 2024 · 0 comments

Assignees

Labels

bug difficulty: medium

Milestone

Recruitmentsystem

Contributor

Snorre98 commented Sep 16, 2024

RecruitmentPositionOverview has multiple bugs.

Related to the status field:

When setting the status "called and rejected" on an application the applicant are NOT to recive automatic rejection. This is both a frontend bug and a backend bug.

This are applicants which have recived an offer of position, but did not want the
position. Therefor they should not recive an rejection email (the applicant is rejecting us, so it would be weird if we sendt rejection email)

When setting some (vilkårlig) status and the applicant(A1) is "moved" to the group it was set to, it is indicated by the status dropdown menu that the applicant which takes the place of A1 in the table recives the same status as A1. This seems to only be a frontend bug, but it should be investigated further.

[here](http://localhost:3000/control-panel/recruitment/15/gang/9/position/144)
(you might get an invalid page if there are no positions or recruitment on these IDs)

Snorre98 added bug difficulty: medium labels

Snorre98 added this to the Recruitmentsystem milestone

simensee self-assigned this

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