You’re viewing Paradaux’s public workspaceSign in to vote Get taskl.ie for your team

PAR-466

Loading issues

PAR-466 · QA: new issues land in different workflows depending on… · Paradaux · taskl.ie

PAR-466· sub-issue of PAR-457

QA: new issues land in different workflows depending on creation entry point

Part of QA PAR-457. In the same fresh workspace, full-page /issues/new defaults Initial status to Triage; desktop C opens a quick-create dialog defaulting Status to Backlog. A user creating the same request on mobile (+ → full page) versus desktop (C) silently gets different routing, and one request bypasses the triage queue. Expected one default policy per workspace/team, reflected in every creation surface, or explicit context when creation intentionally targets a status. Reproduced 18 Oct 2026, design-qa-20261018, GENE team. Full-page was opened from All issues, quick-create from All issues; neither was invoked from a status group.

Activity

taskl.ie created the issue 5d ago
taskl.ie added label Production Design QA · 2026-10-18 5d ago
taskl.ie set a parent issue 5d ago
taskl.ie changed status from Backlog to In progress 5d ago
taskl.ie5d ago
Implemented in the dependent QA stack: https://github.com/ParadauxIO/taskl.ie/pull/91

Combined verification passed: full API suite (1,306 tests), web lint and TypeScript, unit suite (1,211 passed; one existing skip), 483 Chromium story checks, and the production Next.js/CSS build. Desktop/mobile component evidence and a flow diagram are attached where applicable; server-rendered screenshot gaps and GitHub rollout prerequisites are explicit in the PR.

Awaiting review and merge; production application code has not been deployed by this task.
taskl.ie changed status from In progress to Done 4d ago

Workspace permission required to comment

Comments and reactions require workspace permission. Ask a workspace owner or admin for access. You can sign in to vote.