You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
You cannot tag a task or add subtasks, and a mentioned colleague is never notified #649
On a task's detail page you cannot attach a label or add a subtask. The board can filter by label, but no screen lets you put one on a task. When you @mention a colleague in a comment, the mention renders, but the colleague gets no notification.
src/utils/taskHelpers.js:34 sets TASK_SIDEBAR_HIDDEN_TABS = ['tags', 'tasks'], so the task sidebar hides the library's tags and tasks tabs. The comment says Planninq has its own label and subtask concepts, but no replacement exists. task.labels is only displayed and filtered. task.parent is never read or written in src/.
src/views/TaskDetail.vue:129-137 mounts CnObjectSidebar without a @mention listener. In nextcloud-vue, CnNotesTab emits mention with the mentioned user ids and dispatches nothing itself (CnNotesTab.vue:164-173). CnObjectSidebar passes it through. The consuming app has to notify, and Planninq does not.
Fix direction
Either stop hiding the tags tab, or add a label picker to the task detail page that writes task.labels.
Either stop hiding the tasks tab, or add a subtask list that writes task.parent.
Bind @mention on the sidebar and send a Nextcloud notification from the backend to each mentioned user who is a project member.
Live check
Open a task. Look for a way to add a label or a subtask. Expected today: none.
As user A, comment "@b please look" on a task in a project B belongs to. Log in as B. Expected today: no notification.
Matrix rows
tsk-labels, tsk-subtasks, tsk-mentions in openspec/parity/capabilities.json (PR #645).
Activity
github-actions commentedon Sep 26, 2026
Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.
What happens next:
Triage labels:
triage:accept-feature— accepted as a new featuretriage:accept-bugfix— accepted as a bug fixtriage:needs-info— more information neededtriage:wontfix— will not be addressedtriage:duplicate— duplicate of another issue