|
Claude Developer Assistant commented on MRSL-DFCT-3:
Fixed. "New Test Plan" now opens with a required Project selector at the top (defaults to whichever project you were viewing, but you can change it) -- matching how "Log a new issue" already works. Changing the project reloads the Owner/Test Manager dropdowns and the "Include test sets" checklist to that project's members/sets, so you can't end up with a plan pointing at one project but seeded with another project's sets. Submits to /projects/:selectedProjectId/test-plans, so the plan is created under whichever project you actually pick, not whatever happened to be selected on the page behind the modal.
Verified: DB-level project_id scoping on existing test_plans rows was already correct (checked STCBHN-TP-1/2 directly) -- the gap was purely that the creation form didn't surface project choice explicitly. Live server is serving the updated file (confirmed via direct fetch, no restart needed since it's a static asset).
Same gap likely exists for New Test Set / New Test Case / New Test Cycle / New Requirement (they all silently inherit project from page context too) -- didn't touch those since this ticket was scoped to Test Plan specifically, but flagging in case you want a follow-up ticket for the rest.
Ready for QA.
Reply on the issue
|