🐛 Bug: Issues created or updated via REST API send no notifications or emails

[wildsurfer]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Creating, updating, or assigning an issue through the REST API (/api/v1/...)
generates no notification — assignees and subscribers get no in-app notification
and no email. The same actions in the web UI work, and SMTP is fine (OTP and
web-UI emails arrive), so the notification pipeline itself is healthy. Only issue
create and update over the API are affected; comments, attachments, and relations
over the API do notify.

Cause: issue_activity dispatches notifications only when called with
notification=True (default is False, in
apps/api/plane/bgtasks/issue_activities_task.py). In
apps/api/plane/api/views/issue.py, issue create (IssueListCreateAPIEndpoint,
POST) and update (IssueDetailAPIEndpoint, PATCH/PUT) call
issue_activity.delay(...) without notification=True, so notifications.delay(...)
never runs. The web app views (apps/api/plane/app/views/issue/base.py) pass it;
in the same API file attachments and relations pass it, but issue create/update
do not.

This is the same pattern as the webhook bug #8054 (fixed by #8055). Impact: any
team using the REST API, integrations, or the official plane-mcp-server gets no
assignment/update notifications, while the pipeline is healthy.

Expected: REST API create/update/assign should notify assignees and subscribers,
like the web UI. Fix: pass notification=True on those two issue_activity.delay(...)
calls in apps/api/plane/api/views/issue.py.

Steps to reproduce

1. SMTP configured; user B is an active project member with email notifications on.
2. With user A's API key: PATCH /api/v1/workspaces/{slug}/projects/{project_id}/issues/{issue_id}/ with {"assignees": ["<user B id>"]} (or create an issue assigned to B).
3. Result: user B gets no notification and no email; no new rows in notifications / email_notification_logs. Worker logs show issue_activity ran but no notifications task was dispatched.
4. Do the same assignment in the web UI → user B is notified. Confirms it is API-path only.

Environment

Production

Browser

Other

Variant

Self-hosted

Version

v1.3.1 (Community); also present on the current default branch