Phase 04: Job Deactivation System - 2 plans created - 3 total tasks defined - Ready for execution Plan 04-01: Deactivation form with reason capture (2 tasks) Plan 04-02: Admin notification on deactivation (1 task)
4.3 KiB
phase, plan, type, depends_on, files_modified
| phase | plan | type | depends_on | files_modified | ||
|---|---|---|---|---|---|---|
| 04-job-deactivation-system | 02 | execute |
|
|
Purpose: Give admins visibility into deactivation patterns - whether jobs are being filled successfully, withdrawn due to problems, or removed for other reasons. This intelligence helps assess platform effectiveness. Output: Email notification sent to admin on job deactivation with reason included.
<execution_context> ~/.claude/get-shit-done/workflows/execute-plan.md ./summary.md </execution_context>
@.planning/PROJECT.md @.planning/ROADMAP.md @.planning/STATE.mdPrior work this plan builds on:
@.planning/phases/03-job-management-core/03-03-SUMMARY.md @.planning/phases/04-job-deactivation-system/04-01-SUMMARY.md
Source files:
@includes/class-notifications.php
Tech stack available: wp_mail, transition_post_status hook, ACF field access Established patterns:
- transition_post_status hook with status guards (new_status, old_status checks)
- German email templates with job details and context
- Error logging for wp_mail failures
Constraining decisions:
- Phase 03-03: transition_post_status used to detect status changes, prevents spam on updates
- Phase 03-03: Email sent to admin_email option, includes direct edit link
- Phase 04-01: Deactivation reason stored in ACF field 'job_deactivation_reason'
- Phase 04-01: Deactivation changes post status from publish to draft
<success_criteria>
- Admin receives email when provider deactivates published job
- Email includes job details (title, provider, location, type, date)
- Email includes deactivation reason captured from form
- Email sent only on publish→draft transitions (not draft→draft)
- Phase 4 complete - deactivation workflow functional end-to-end </success_criteria>
Phase 4 Plan 2: Deactivation Notifications Summary
[Substantive one-liner - what shipped, not "phase complete"]
Accomplishments
- [Key outcome 1]
- [Key outcome 2]
Files Created/Modified
includes/class-notifications.php- Description
Decisions Made
[Key decisions and rationale, or "None"]
Issues Encountered
[Problems and resolutions, or "None"]
Next Step
Phase 4 complete. Ready for Phase 5: Mentor Job Board.