Repository navigation
Conversation
(cherry picked from commit d304f18)
- The stage form of 20.0 has no stage_definition group anymore: the per-job rotting fields are anchored to the configuration group. - In 20.0 the talent pool wizard copies the attachments to the talent and redirects applicants already linked to one. The attachment move is removed and only applicants that become a new talent are archived (PO decision on task 76631).
…t pool In 20.0 the talent pool wizard accepts applicants already linked to a talent, directly or by sharing email, phone or LinkedIn with one. Those applicants keep their application active, as the PO decided on task 76631.
Contributor
|
|
…lent The talent pool wizard of 20.0 creates a new talent for an applicant that is only linked to a talent by email, phone or LinkedIn, because it only looks at pool_applicant_id. Those applicants must be archived too: the module archives exactly the applicants the core copies into a new talent.
Contributor
|
@roboadhoc r+ nobump rebase-ff |
Contributor
|
Merge method set to rebase and fast-forward. |
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
(cherry picked from commit d304f18) Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
- The stage form of 20.0 has no stage_definition group anymore: the per-job rotting fields are anchored to the configuration group. - In 20.0 the talent pool wizard copies the attachments to the talent and redirects applicants already linked to one. The attachment move is removed and only applicants that become a new talent are archived (PO decision on task 76631). Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
…chiving Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 30, 2026
…t pool In 20.0 the talent pool wizard accepts applicants already linked to a talent, directly or by sharing email, phone or LinkedIn with one. Those applicants keep their application active, as the PO decided on task 76631. Part-of: #75 Signed-off-by: Matias Velazquez <[email protected]>
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tarea: https://www.adhoc.inc/odoo/project.task/76631
What changes
upgrade_code(19.4-00-ir-access): manifest to20.0.1.0.0,ir.model.access.csvconverted toir.access.csv(same rights: usercrud, interviewerr).stage_definitiongroup is gone in 20.0.use_rotting_per_jobnow goes after the "Rotting in N days" block of theconfigurationgroup, and the per-job grid after the main group, before Requirements (same place as in 19.0)._compute_rotting): unchanged, the rotting mixin and the applicant fields it uses are the same in 20.0.Data
No migration script: the new model, the stage fields and the constraint are the same in 19.0 and 20.0.
Test plan
--test-tags /hr_recruitment_ux:0 failed, 0 error(s) of 2 tests(6 sub-cases); each behavior was broken on purpose and the matching test failed.pre-commitpasses; anchors of the inherited view checked on 20.0.