Jira — Da Vinci NO-TOUCH (ABSOLUTE)

🚨 ABSOLUTE: NEVER touch Da Vinci Jira project

User directive 2026-05-03 (r_goto, verbatim):

“Dont touch Da Vinci! Dont you ever do any edit, add, or delete in Da Vinci Projects Jira. For the rest, you can do task update, description, task creation, ticket movement, comments”

Da Vinci Jira project key

DVG — full name “Da Vinci Graph プロジェクト” / “Da Vinci Graph”

Forbidden operations on DVG (and any Da Vinci variant if added later)

• ❌ mcp__jira__jira_create_issue with project_key=DVG
• ❌ mcp__jira__jira_update_issue on any DVG-* ticket
• ❌ mcp__jira__jira_delete_issue on any DVG-* ticket
• ❌ mcp__jira__jira_transition_issue on DVG-* (state changes)
• ❌ mcp__jira__jira_add_comment on DVG-* (any write)
• ❌ mcp__jira__jira_create_issue_link, attachments, labels, assignees on DVG-*
• ❌ Bulk operations including any DVG ticket

Allowed on DVG

• ✅ READ ONLY: jira_get_issue, jira_search, jira_get_transitions (view-only)

Allowed on ALL OTHER projects (CRV, KOKO, PASS, PL, RMY, SL)

• ✅ Task creation
• ✅ Task update / description edit
• ✅ Ticket movement (transitions)
• ✅ Comments
• ✅ All standard write operations (subject to standard workflow rules)

Pre-write check (REQUIRED before any Jira write)

1. Inspect target ticket key
2. If starts with DVG- → ABORT, inform user
3. If project_key parameter == DVG → ABORT
4. If unsure → ASK user, never assume

Why

Da Vinci is a separate team’s domain. Wrong edits would break their workflow. User has explicit ownership boundary.

Cross-refs

• jira-mcp-setup — full project list
• all-jira-projects — project catalog