Plan Add Remove Test Cases

Add / Remove Test Cases to Test Plan (planAddTC) — Wiki

The modernized Add / Remove Test Cases screen replaces the legacy lib/plan/planAddTC.php tree-based linker. It links test case versions into a test plan (optionally per platform), unlinks them, sets execution order and can assign a tester + build for freshly added cases — all with the same server-side semantics as TestLink 1.9.20 (testplan::link_tcversions(), unlink_tcversions(), setExecutionOrder()).

Path: Test Plan > Add / Remove Test Cases (requires an active test plan) URL: gui/templates/plans/planAddTCView.html?tproject_id=<id>&tplan_id=<id> BFF API: api/plans/index.php (REST: GET /planaddtc/init, /planaddtc/suites, /planaddtc/container; POST /planaddtc/save, /planaddtc/reorder, /planaddtc/savecustomfields, /planaddtc/save-platform) Prerequisite: testplan_planning right on the test project; removing links that already have executions additionally requires testplan_unlink_executed_testcases.

---

Table of Contents

1. Screen Layout
2. Linking Model 2d. Platform Reassignment + Save platform (Issue #1129)
3. Executed-Link Guard
4. Rights Model
5. REST API Reference
6. i18n Keys
7. Testing
8. Bugfix — Issue #1909: column alignment for platform-less plans
9. Task — Issue #1130: per-TC execution-history + test-spec-design icons
10. Task — Issue #1131: requirement-coverage navigator modes
11. Task — Issue #1132: full navigator filter panel
12. Task — Issue #1133: render-time gating of the executed remove checkbox
13. Feature — Issue #1135: platform-scoped bulk check/uncheck + per-suite remove-all

---

1. Screen Layout

• Teal Dashio header: title, subtitle, locale switcher.
• Toolbar: test project picker, test plan picker (re-inits the whole screen), Group by selector (Test suites / Requirement coverage — legacy setting_testsgroupby, see §10), Filters toggle button (full navigator filter panel, see §11), bulk platform check/uncheck control (see §13), Refresh button.
• Left panel — suite tree with linked/total deep badges per suite (or the requirement-coverage tree when Group by = Requirement coverage).
• Right panel — per-suite table:
  • ADD: checkbox; version dropdown (active versions only, newest active preselected; inactive versions disabled); platform multi-select when the plan has platforms (nothing preselected, legacy default); execution order input.
  • Status column (always) and Importance column (only when the project enables test priority) — legacy planAddTC.tpl:171-172; both follow the version chosen in the row and are re-rendered when it changes (see §2b).
  • Linked rows show a remove chip v<n> #<order> (red dot when executed) and the add controls collapse into the linked state.
  • Added on date column (rightmost) — the link creation date of a linked test case (legacy linked_ts), blank for unlinked add-rows (see §2c).
  • Linked rows additionally render a full-width custom-fields row per link when the project has custom fields with show_on_testplan_design/ enable_on_testplan_design (scope testplan_design): tag "Custom fields for v · " followed by the legacy CF inputs (custom_field_<type>_<cfid>_<link_id> names, pre-filled with the values stored in cfield_testplan_design_values).
• Footer: Save changes (links) / Save execution order (reorder) / Save custom fields (CF values — visible only when at least one linked TC in the suite has testplan-design CFs and the user holds testplan_planning).
• Tester assignment block appears when exec_assign_testcases right is present and the plan has active builds: tester + build dropdowns applied to newly created features.

2. Linking Model

Payloads mirror the legacy structures exactly: {items:{tcId:{platId:versionId}}, tcversion:{tcId:versionId}, platform:{platId:platId}}.

• Platform-less plans link version id under platform key 0.
• Already-linked pairs are silently deduplicated server-side (legacy getFilteredLinkedVersions behavior).
• Reorder sends {order:{tcversion_id: node_order}} → setExecutionOrder().

2a. Testplan-design custom fields (Issue #1126)

Legacy parity with planAddTC.php doSaveCustomFields() (lib/plan/planAddTC.php :715-778): the BFF renders the ready-to-write inputs server-side with the exact legacy helper (testcase::html_table_of_custom_field_inputs scope testplan_design), so every CF type (string, combo, multi-select, checkbox, radio, date, datetime) keeps its native input/name/value semantics. The POST endpoint groups the submitted custom_field_*_*_<link_id> names by link_id (≈ testplan_tcversions.id, explode('_') position 4, same split as legacy), rejects links not owned by the plan, and persists each subset through cfield_mgr::testplan_design_values_to_db($cfvalues, null, $link_id).

2b. Workflow Status + Importance columns (Issue #1127)

The modern table dropped the two attribute columns the legacy screen rendered (planAddTC.tpl:311-317). They are restored:

• Status — always shown; label from tcversions.status mapped through the tcView wording (Draft, Ready for review, Review in progress, Rework, Obsolete, Future, Final, i.e. config_get('testCaseStatus')).
• Importance — shown only when the project option testPriorityEnabled is set (planAddTC.php:621) — the header and the body cells are both omitted otherwise; labels High / Medium / Low.
• A row shows the attributes of its linked version, or of the version preselected in the dropdown for an unlinked case. Changing the version dropdown re-renders both cells via updTCAttr() — the modern twin of legacy updTCAttr(tcID,tcvID) — so it matches specview.php:1323-1324.

2c. "Added on date" column (Issue #1128)

Legacy 1.9.20 rendered a rightmost Added on date column built from the link timestamp TPTCV.creation_ts (aliased linked_ts in testplan.class.php:6076; template planAddTC.tpl:184-186 header, :370 no-platform cell localize_date d=$tcase.linked_ts[0], :438 per-platform cell). The modern screen had dropped it entirely.

• BFF /planaddtc/container now selects TPTCV.creation_ts AS linked_ts and each links[] entry carries linked_ts (raw YYYY-MM-DD HH:MM:SS) plus linked_ts_display rendered with the same helper legacy used (localize_dateOrTimeStamp(..., 'date_format', ...) → %d/%m/%Y).
• The screen renders the localized date for linked TCs; because the modern screen aggregates the legacy per-platform rows into one row per test case, the cell joins every distinct link date (legacy showed linked_ts[0] without platforms, linked_ts[platform.id] with platforms). Unlinked add-rows stay blank, exactly like legacy  .
• Cell tooltip = paddtc.infoAddedOnDate (legacy info_added_on_date = "Date when test case was added to test plan").

2d. Platform Reassignment + Save platform (Issue #1129)

Legacy planAddTC.php let you reassign the platform of a test case already linked to the plan: on ?edit=testsuite&id=<suite> each linked TC whose link had platform_id=0 rendered a <select name="feature2fix[<feature_id>][<tcversion>]"> (gui/templates/dashio/plan/planAddTC_m1.tpl:319-321), and the header button Save platform (btn_save_platform, planAddTC.php:114) posted to doSavePlatforms (:791-800), which called testplan::changeLinkedTCVersionsPlatform() (lib/functions/testplan.class.php:3603-3626) to move the link and its executions to the chosen platform. The button only appeared under full_control / testplan_planning (initDrawSaveButtons()).

The modern screen restores it:

• Per-link <select class="pfsel"> — in the Platforms cell of each linked test case. Because a modern row aggregates possibly several links, one select is rendered per link ({feature_id, tcversion_id, platform_id}), preset to the link's current platform; options are none (0) plus every platform linked to the plan (/planaddtc/container → platforms). This is a strict superset of the legacy platform_id=0-only select: an already-platformed link can be changed too.
• Save platform button (#btnSavePlatform) — shown only when the plan uses platforms and there is at least one linked row. It collects only the selects whose value differs from the original (data-pl) and POSTs the changed map; when nothing changed it shows paddtc.noPlatformChange and makes no request.
• BFF POST /planaddtc/save-platform (api/plans/index.php:1502) — body {tproject_id,tplan_id,platforms:{<feature_id>:<platform_id>}} where feature_id is testplan_tcversions.id (the same key the legacy template used). It requires testplan_planning, ignores feature ids not owned by the plan, and rejects a target platform not linked to the plan (400 INVALID_PLATFORM). For each changed link it runs the legacy two statements transactionally: update testplan_tcversions.platform_id, and move the link's executions.platform_id from the old to the new platform so existing results follow it. Moving a link that already carries executions requires testplan_unlink_executed_testcases (else 403 EXECUTED_PRESENT), mirroring the sibling removal guard.

3. Executed-Link Guard

When removing links whose executed_qty > 0 and the user lacks testplan_unlink_executed_testcases, the request is rejected (403). Users that have the right see a confirmation modal listing affected test cases; confirming removes links and cascades execution deletion (same as 1.9.20).

Since Issue #1133 the guard is mirrored in the UI at render time (legacy $show_remove_check=$gui->can_remove_executed_testcases, planAddTC.tpl:347-363): when the user lacks the right, an executed link renders as a read-only <span class="chip executed chip-ro"> with no remove checkbox and the executed_can_not_be_removed tooltip, while non-executed links keep their checkbox. A JS pre-submit guard + the server-side 403 remain as defense in depth.

4. Rights Model

Right	Effect
testplan_planning	required on every endpoint
testplan_unlink_executed_testcases	remove executed links
exec_assign_testcases	enables tester/build assignment

Hardening (code review round): /planaddtc/init validates tplan ownership, suites rejects foreign recursion roots, save verifies every test case lives inside the target project (parent-walk to project root), CSRF same-origin proof required on POSTs.

5. REST API Reference

Method & Route	Purpose
GET /api/plans/index.php/planaddtc/init?tproject_id=&tplan_id=	plans, rights, keywords, platforms, builds, testers, priority_enabled
GET /planaddtc/suites?tproject_id=&tplan_id=[&keyword_id=][&container_id=]	suite tree w/ deep totals + linked counts
GET /planaddtc/container?container_id=	test cases of one suite: versions (incl. status, importance), links (incl. linked_ts + linked_ts_display), executed_qty, per-link custom_fields_html, has_custom_fields
POST /planaddtc/save	link/unlink pairs + optional tester/build assignment
POST /planaddtc/reorder	save execution orders
POST /planaddtc/savecustomfields	persist testplan-design CF values (grouped by link_id, owned-link check, testplan_design_values_to_db)
POST /planaddtc/save-platform	reassign an already-linked TC's platform (by testplan_tcversions.id); moves the link + its executions (legacy doSavePlatforms/changeLinkedTCVersionsPlatform)

Errors are JSON {status:"error",message} with proper HTTP codes (400 invalid input, 401 no session, 403 rights/ownership, 404 not found, 422 NO_SELECTION / INACTIVE_VERSION).

6. i18n Keys

paddtc.* keys in all 10 bundles (en, ro, de, es, fr, it, ja, pt, ru, zh), plus reuse of pv.testProject, common.*. The five testplan-design-CF keys (paddtc.saveCustomFields, paddtc.cfFor, paddtc.cfHelp, paddtc.cfNothingSaved, paddtc.msg.cfSaved) were added for Issue #1126 and paddtc.colStatus / paddtc.colImportance for Issue #1127 (which reuses tcview.statusN and search.*Importance for the cell values). paddtc.addedOnDate (column header) and paddtc.infoAddedOnDate (tooltip) were added for Issue #1128. paddtc.savePlatforms, paddtc.reassignPlatform, paddtc.noPlatformChange and paddtc.msg.platformSaved were added for Issue #1129. paddtc.executionHistory and paddtc.testSpecDesign were added for Issue #1130 (the per-TC icon tooltips; values reused from the verified ta2p.execHistory / ta2p.design translations so wording matches sibling screens). paddtc.executedNoRemove was added for Issue #1133 — the tooltip on an executed link's read-only remove cell when the user lacks testplan_unlink_executed_testcases (legacy executed_can_not_be_removed, locale/en_US/strings.txt:1486), also used as the vial-icon title in that state.

7. Testing

Regression suites in tmp/TLU_Test_Cases.md: 56 (original load/rights/i18n/ navigation/add-reorder-remove/executed-guard/keyword-filter), Task — Issue #1126 (9/9 PASS): CF row rendering, custom_field_*_<link_id> naming, save round-trip persistence, Event Viewer clean, i18n coverage gate; and Task — Issue #1127 (9/9 PASS): Status/Importance rendering for linked + unlinked rows, version-change update, priorityEnabled=0 hides the Importance column, Event Viewer clean, i18n coverage gate; and Task — Issue #1128 (7/7 PASS): BFF linked_ts/linked_ts_display, Added-on-date header + linked-row date, blank for unlinked rows, tooltip, i18n coverage gate, Event Viewer clean; and Task — Issue #1129 (9/9 PASS): per-link platform select preset to the link's platform, "Save platform" button visibility, no-change toast, true reassignment (none → Linux → Windows, DB-verified), executions follow the link, INVALID_PLATFORM/ NO_SELECTION/unauthenticated errors, Event Viewer clean. and Task — Issue #1130 (11/11 PASS): per-row execution-history + test-spec-design icon links, correct hrefs/labels/glyph font, both targets open the right page, #1767 summary button intact, Event Viewer clean, i18n coverage gate exit 0; and Task — Issue #1133 (6/6 PASS): no modal for non-executed removals, confirmation modal + cascade for executed ones (cancel / OK), render-time gating for a right-less user, JS+server defense in depth, i18n coverage gate, Event Viewer clean.

---

8. Bugfix — Issue #1909: column alignment for platform-less plans

Defect. For any test plan without platforms, the table header and body were misaligned: renderContainer() hid the Platforms header ($('#thPlat').toggle(hasPlat), planAddTCView.html:380) but the row template still emitted a platform <td> unconditionally (:468). A platform-less plan therefore rendered 6 header cells against 7 body cells, so Exec. order and Remove links were shifted one column to the left and sat above the wrong cells (the remove chip had no header at all). All test cases in such a plan are affected; the defect was pre-existing in the screen (not introduced by #1127) and purely cosmetic — saving, ordering and removing links were unaffected because collectSelection() already branches on hasPlat (add[tc]={"0":vid}).

Before (no platforms — 6 headers, 7 cells; Exec. order/Remove links off by one):

After (no platforms — 6 headers, 6 cells, aligned):

Fix (2 lines, gui/templates/plans/planAddTCView.html).

// :468 — emit the platform cell only when the plan actually has platforms
(hasPlat?'<td>'+(isLinked?'':platCell)+'</td>':'')+
// :486 — cf-row colspan = the number of visible columns
$('<td>').attr('colspan', 6+(priorityEnabled?1:0)+(hasPlat?1:0))

The second site (testplan-design custom-fields row) shared the same root cause: its colspan hard-coded the platform column as always present. The correct visible column count is 6 + importance? + platforms? (checkbox, Test Case, version, Status, [Importance], [Platforms], Exec. order, Remove links).

Verified across all four configurations — no-platforms/no-priority (6=6, cf-colspan 6), platforms/no-priority (7=7, cf-colspan 7), platforms+priority (8=8, cf-colspan 8), no-platforms+priority (7=7, cf-colspan 7) — plus linked and unlinked rows (add-checkbox, version dropdown, platform multi-select render in the correct cells), the custom-fields row, and the platform-less collectSelection() payload; browser console clean, Event Viewer clean. Regression suite Regression — Issue #1909 appended to tmp/TLU_Test_Cases.md (8/8 PASS, i18n gate exit 0). Landed as 526a902cd.

---

9. Task — Issue #1130: per-TC execution-history + test-spec-design icons

Gap (legacy vs modern). Legacy planAddTC.tpl:247-252 (and the per-link variant planAddTC_m1.tpl:327-331) rendered, next to every test case, a history_small span titled $labels.execution_history that called openExecHistoryWindow(tcase_id,...), and an edit_icon.png titled $labels.design that called openTCaseWindow(tcase_id). The modern screen (planAddTCView.html) dropped both. Its third legacy item — the hover summary tTip() backed by lib/ajax/gettestcasesummary.php — was already replaced by the rights-checked .sum-btn → tcSummary.html popup in Issue #1767.

After the fix (every row now carries a history clock and a design pencil next to the #1767 summary button):

Fix (client-side only, gui/templates/plans/planAddTCView.html).

• Two URL helpers execHistoryUrl(tcId) / designUrl(tcId) next to verOf(), emitting the same targets as the sibling screens (testUrgency.html:317-320, showNewestTcVersions.html:216-218): /gui/templates/execute/execHistory.html?tcase_id=<id>&tproject_id=<id> and /gui/templates/testcases/tcView.html?tcase_id=<id>&tproject_id=<id>.
• Two icon anchors per row in the Test Case cell (rendered for linked and unlinked rows, exactly like legacy): <i class="fas fa-clock-rotate-left"> (execution history) and <i class="fas fa-pen-to-square"> (test spec design), each target="_blank" rel="noopener" with matching title + aria-label from the new i18n keys.
• .ic-link CSS in the Dashio palette (grey #7a8a99 → teal #1d6f69 on hover).

No BFF change was required: api/plans/index.php:1143 already returns tc_id per item.

Clicking the history icon opens the read-only execution history for that test case:

Clicking the design icon opens the modern test-case viewer:

Verified with fixtures php tmp/fixtures_1767.php (tproject SUM1=1, plan 3, suite 5): both icon links present on every row; hrefs correct for tcase 10/6/14; computed font-family="Font Awesome 6 Free"; clicking the history icon opened TS1767-2 - Execution History and the design icon opened TS1767 Empty Summary - Test Case Viewer; node --check clean; i18n coverage gate exit 0 (7627 keys); Event Viewer clean. Regression suite Task — Issue #1130 appended to tmp/TLU_Test_Cases.md (11/11 PASS).

---

10. Task — Issue #1131: requirement-coverage navigator modes

The legacy navigator had a setting_testsgroupby control that switched the left tree between the test suite hierarchy and the requirement coverage hierarchy (lib/functions/tlTestCaseFilterByRequirementControl.class.php:669, tree built by generateTestReqCoverageTree(), lib/functions/treeMenu.inc.php:1646). Clicking a tree node opened the right pane through lib/plan/planAddTC.php with item_level=reqcoverage (a single requirement) or item_level=reqspeccoverage (a whole requirement spec). The modern workframe had dropped this — its tree was suites-only and the /planaddtc/container route 404'd on non-suite containers.

After the port — Group by = Requirement coverage shows the req-spec subtree with per-node linked/total badges of covering test cases:

Behavior

• Group by selector in the toolbar: Test suites (default) / Requirement coverage. Reuses the existing i18n keys pnav.groupBy, pnav.groupsSuites, pnav.groupsReqs, pnav.treeHeaderReqs (present in all 10 bundles — no new keys, no hardcoded strings).
• In coverage mode the left panel renders requirement specs as parent nodes and their requirements as indented leaves; both show linked/total, where total is the number of DISTINCT test cases covering the node (req_coverage.is_active = 1) and linked is how many of those are already linked into the selected test plan.
• Clicking a requirement (node_type=req) shows its covering test cases; clicking a requirement spec (node_type=req_spec) shows the union of the covering test cases of all its requirements. Linked ones render as today; unlinked ones render as add-rows, so a test case that covers a requirement can be linked straight from the requirement view — and the tree counts refresh after saving. The keyword filter and the mode selection persist.

REST API

• GET /planaddtc/suites?tproject_id=&tplan_id=[&mode=normal|req_coverage] — with mode=req_coverage returns {status, mode:"req_coverage", items:[{id,name,doc_id,parent_id,node_type:"req_spec",total_qty,linked_qty,deep_total_qty,deep_linked_qty,req_count,requirements:[{id,name,doc_id,total_qty,linked_qty,covered}]}]}.
• GET /planaddtc/container?tproject_id=&tplan_id=&container_id=&mode=req_coverage&node_type=req|req_spec — resolves the covering test cases via req_coverage and returns the same item shape as a suite container (container.node_type, mode, items, platforms, rights, has_custom_fields), so the entire version / link / executed-qty / custom-field pipeline is reused unchanged. A node that does not belong to the addressed project is rejected with 404.
• Ownership of a requirement/spec node is proven against the addressed project (requirements.srs_id → req_specs.testproject_id); the normal suite path is untouched.

Verification

Fixture php tmp/fixtures_1572.php (tproject NAV1572, plan 20, spec RS-NAV 22, reqs 24/26; req_coverage req1→tcA1, req2→tcB1; plan links A1/B1/B2):

• mode=req_coverage → spec 2/2, REQ-NAV-1 1/1, REQ-NAV-2 1/1.
• container node_type=req id=24 → Alpha One linked; node_type=req_spec id=22 → Alpha One + Beta One.
• With an extra unlinked covering row (req2→tcA2), opening REQ-NAV-2 showed Alpha Two as not linked; ticking it and Save changes returned 1 link(s) added, 0 removed, the row became linked and the tree updated to REQ-NAV-2 2/2, spec 3/3.
• Regression: Group by = Test suites → Suite A 1/3, Suite B 2/2, Suite A1 0/1.
• Console clean; Event Viewer only audit rows. Test suite Task — Issue #1131 appended to tmp/TLU_Test_Cases.md (11/11 PASS).

---

11. Task — Issue #1132: full navigator filter panel

The legacy Add/Remove Test Cases navigator rendered a full filter panel (gui/templates/dashio/include/inc_filter_panel.tpl + inc_filter_panel_js.tpl, driven server-side by lib/functions/tlTestCaseFilterControl.class.php plan_add_mode) with test-case ID, title, top-level test suite, keywords (Or/And), platforms, importance, workflow status and design custom fields. The modern workframe had dropped it, keeping only a single keyword <select>. This port restores the whole panel and the BFF filter engine.

Behavior

• Toolbar Filters button toggles a collapsible panel (#filterPanel) with:
  • Test case ID (external id, e.g. TP-1) and Title (substring, LIKE).
  • Top-level test suite — re-roots the left tree to that branch.
  • Keywords multi-select + Any (OR) / All (AND) radios.
  • Platforms multi-select (plan platforms), Importance multi-select (only when the project has test priority), Workflow status multi-select.
  • Custom fields — one control per design custom field linked to the project (list/radio → select, else text).
• Apply filters re-queries the tree and the container; Reset filters clears everything; a hint shows No filters active / Filters active.
• Selections persist per session in sessionStorage (paddtc.filters.<tproject_id>), so a reload keeps the active filter set.

REST API

• GET /planaddtc/suites?... accepts the legacy filter_* query dict: filter_tc_id, filter_testcase_name, filter_toplevel_testsuite, filter_keywords[] + filter_keywords_filter_type (Or|And), filter_platforms[], filter_importance[], filter_workflow_status[], filter_custom_fields[<field_id>]. Suites with deep_total_qty == 0 are pruned; filter_toplevel_testsuite overrides the requested root.
• GET /planaddtc/container?... applies the same restriction to the suite branch rows and to the requirement-coverage branch.
• GET /planaddtc/init returns filters = {top_level_suites, workflow_status, custom_fields} used to populate the panel.
• Semantics mirror legacy testproject::getTestSpec() / tlTestCaseFilterControl (see tlTestCaseFilterControl.class.php:242-250): title LIKE, external id resolved to internal, importance/status/custom-field matched on the latest ACTIVE tcversion, keywords testcase-level, platforms via the plan links.
• api/_guard.php: the new GET arrays are whitelisted in $arrayParams for api/plans/index.php; the #1810 non-scalar guard would otherwise answer 400 invalid_parameter.

i18n

New keys paddtc.filters + 16 paddtc.filter* (filterTitleHeader, filterTcId, filterName, filterTopSuite, filterKeywords, filterKwOr, filterKwAnd, filterPlatforms, filterImportance, filterStatus, filterCustomFields, filterAny, filterApply, filterReset, filterHint, filtersApplied) in all 10 locale bundles.

Verification

Fixture tmp/opencode/fixtures1132.sql (tproject 1, plan 50; suites 10/11; TCs 100/101/102; keywords 300/301; design CF 400 browser):

• suites filter_testcase_name=Payment → Payments suite (Login pruned); filter_toplevel_testsuite=11 → Payments suite.
• container: filter_importance[]=3 → Login test; filter_workflow_status[]=2 → Logout test; keywords 300 Or → Login+Logout; 300+301 And → Logout; filter_custom_fields[400]=Firefox → Login test, =Chrome → Payment test; filter_platforms[]=5 → empty; filter_tc_id=TP-2 → Logout test.
• UI: Apply importance=High → hint Filters active, tree Login suite 1/1, row Login test; reload keeps it; Reset restores Login suite 1/2, Payments suite 0/1; title=Logout + click Login suite → right pane Logout test.
• First-load plan domains: boot() re-inits for the resolved default plan, so the Platforms filter is populated (verified with a Linux plan platform) without the user changing the plan.
• Console clean; Event Viewer only audit rows. Test suite Task — Issue #1132 appended to tmp/TLU_Test_Cases.md (19/19 PASS).

---

12. Task — Issue #1133: render-time gating of the executed remove checkbox

Reported gap. The original issue claimed the executed-link removal confirmation had been dropped during modernization. Investigation (see the issue's INVESTIGATION comment) proved the modal already existed since c3bfaba0c (2026-08-22) — 16 days before the issue was filed — and works: Save with an executed link selected fires no POST until the modal is confirmed, Cancel leaves link + executions intact, OK removes the link and cascades the execution deletion. The genuine legacy-parity gap found in the same legacy block was the render-time gating of the remove checkbox.

Legacy behavior (planAddTC.tpl:347-363).

{* executed test case => can not be removed *}
{$show_remove_check = $gui->can_remove_executed_testcases}

When the user lacks testplan_unlink_executed_testcases, legacy renders the executed link's remove cell without a checkbox and titles the executed icon executed_can_not_be_removed (planAddTC.php:692-697); otherwise has_been_executed. The modern screen always rendered an interactive checkbox and relied solely on the BFF 403.

Fix.

• gui/templates/plans/planAddTCView.html — in renderContainer() the remove cell now branches on INIT.rights.canRemoveExecuted: for an executed link without the right it emits <span class="chip executed chip-ro" title="paddtc.executedNoRemove"> (no input.rmchk); the vial-icon tooltip likewise switches between paddtc.executed and paddtc.executedNoRemove. New CSS .chip.chip-ro (cursor:not-allowed; opacity:.75) marks the read-only state.
• gui/templates/i18n/*.json — new key paddtc.executedNoRemove in all 10 bundles.
• Unchanged defense in depth: the pre-submit execList guard (paddtc.errExecuted toast) and the server-side 403 EXECUTED_PRESENT.

Rights-less user — executed chip is a read-only span (no checkbox, "Executed test cases can not be removed." tooltip); non-executed link keeps its checkbox:

With the right, the confirmation modal still lists the executed cases and their results before removing them:

Verification. GET /planaddtc/init for the right-less user returns rights={canPlan:true,canRemoveExecuted:false,canAssignExecTask:false}; DOM shows TA-1 = <label>+input.rmchk, TA-2 = <span class="chip executed chip-ro"> (no checkbox). Forcing a checked input.rmchk on the executed row + Save yields the red paddtc.errExecuted toast, no modal, no POST, DB unchanged. Admin paths re-verified (no modal for unexecuted, modal+cascade+toast for executed). bash ai/verify_i18n_coverage.sh PASS (7799 keys); Event Viewer only log_level=16 audit rows. Suite Task — Issue #1133 appended to tmp/TLU_Test_Cases.md (6/6 PASS).

---

13. Feature — Issue #1135: platform-scoped bulk check/uncheck + per-suite remove-all

Reported gap. Legacy 1.9.20 rendered, above the suite tables, a bulk control "Check/uncheck all Test cases for [] for [adding|removal]" (planAddTC_m1.tpl:167-183, backed by checkboxes.js:271 cs_all_checkbox_in_div_with_platform), and every suite header had an "all" toggle for both the add checkbox and the per-link remove checkbox (planAddTC_m1.tpl:244 add / :262 remove). The modern screen had only a global add toggle that ignored platforms.

Behavior

• A toolbar control (#bulkPlatform select + #btnBulkAdd + #btnBulkRm) renders whenever the plan has platforms; the select lists All platforms plus each plan platform. When the plan has no platforms the control is hidden (parity with legacy, which only rendered the per-platform control with platforms).
• adding mode checks the add checkbox of every unlinked row, and sets that row's platform multi-select to the chosen scope (All platforms selects every plan platform, a single platform selects just it, All platforms + no specific = [All] snake).
• removal mode checks the per-link remove checkbox of every removable row: for a single platform only that platform's link row; for All platforms every removable link. Executed links the user may not unlink stay read-only (§12).
• Clicking the active mode again toggles the group off (legacy cs_all_checkbox_in_div semantics).
• The per-suite header toggles: #chkAllAdd (add column) and #chkAllRm (remove column, fa-link-slash). #chkAllAdd honours the current platform scope — it selects that platform in each row's select.psel so the add actually submits for the platform. #chkAllRm unlinks every removable link in the suite.

i18n

New keys paddtc.checkUncheckAll, paddtc.allPlatforms, paddtc.for, paddtc.adding, paddtc.removal, paddtc.checkAllAdd, paddtc.checkAllRm in all 10 locale bundles.

Verification

Fixtures tmp/fixtures_1126.sql + tmp/fixtures_1135.sql (plan 2000 "Demo Plan", platforms 4001 Linux / 4002 Windows; LC1 @Linux executed, LC2 @Windows, LC3 unlinked):

• select Linux + adding → LC3 add checked, psel=["4001"]; clicking again unchecks (toggle).
• select All platforms + adding → psel=["4001","4002"].
• select Linux + removal → only rmchk[data-pl=4001] checked; All → every removable link.
• #chkAllRm → all 4 link remove-checkboxes checked; #chkAllAdd with scope Windows → LC3 add checked, psel=["4002"].
• End-to-end Save changes: Linux+adding persisted the LC3@Linux link (node 9103, tcversion 30031, platform 4001, toast "1 link(s) added, 0 removed"); Windows+removal unlinked LC2@Windows (toast "0 link(s) added, 1 removed", LC2 shows only v1 · none).
• Executed-removal guard still fires: Linux+removal + Save opened the confirmation modal listing LC1.
• No-platform plan hides the bulk select; locale switch to ro renders translated labels ("Toate platformele", "adăugare", "eliminare"). Console clean; ai/verify_i18n_coverage.sh 9/9 PASS. Suite Issue #1135 appended to tmp/TLU_Test_Cases.md (17/17 PASS). A pre-existing save-path warning was filed separately as #1919.