Table of Contents

#67 — Closing an installation-type Task via the real "Done" workflow never generates an Installations record (Resolved)

← Back to Manara Bugs · View issue #67 in MantisBT


Reported by: Khaled Tarabay on 2026-07-27T10:39:22+01:00
Assigned to: Claude
Resolved by: Claude on 2026-07-27T10:49:38+01:00
Severity: major
Priority: high
Reproducibility: always
Category: General

Description: /installations/create has no direct create route (it redirects into the generic Tasks list), so a working task-close-out trigger is the only way new Installation records can enter the system through the app itself. With that trigger not firing under either resolution type tested, front-line technicians using the app as designed have no working way to produce a new Installations record

Steps to Reproduce: From /dashboard, click Create → New Task. Fill in customer (e.g. Jdoe), issue type “New installation,” project, status “New,” assignee, deadline, description. Save. Open the new task, click the “Done” button. On the Close Task form, select Problem = “Cabling / line issue” (or “Resolved / No fault”), enter an amount collected, method, description. Click “Close task.” Confirm the task's Status is now “Done.” Go to /installations — row count is unchanged; no new record for the task just closed

Resolution: DUPLICATE of #65 – identical summary, description, and repro steps. This was already fixed in the same pass as #65 (see that ticket's resolution note): app/classes/Projects/TaskIssueType.php gained codeFor(), and app/controllers/TaskController.php's close-out now creates an Installations record whenever the task's own issue type resolves to the system code 'new_installation', independent of whether any equipment lines were recorded in that same close-out.

Most likely explanation for seeing this again: this fix exists in the codebase/local dev environment but has NOT yet been uploaded to the live server (deploys here are manual, via FileZilla, by the project owner) – so a retest against the live site would still show the pre-fix behavior. No new code change was needed for this ticket; resolving as a duplicate of #65, which carries the actual fix details and verification steps.

Activity / Notes

Most likely explanation for seeing this again: this fix exists in the codebase/local dev environment but has NOT yet been uploaded to the live server (deploys here are manual, via FileZilla, by the project owner) – so a retest against the live site would still show the pre-fix behavior. No new code change was needed for this ticket; resolving as a duplicate of #65, which carries the actual fix details and verification steps.

Full History

Date User Field Change
2026-07-27T10:39:23+01:00 Khaled Tarabay issue-new New Issue
2026-07-27T10:49:28+01:00 Claude Assigned To ⇒ Claudine
2026-07-27T10:49:32+01:00 Claude tag-added Tag Attached: done-by-claude
2026-07-27T10:49:34+01:00 Claude note-added Note Added: 0000026
2026-07-27T10:49:38+01:00 Claude Status new ⇒ resolved

Synced automatically from MantisBT issue #67.