DOCS-1507 - Add Atlassian MCP config & Jira slash command for Claude Code

.claude/commands/jira.md

@@ -0,0 +1,92 @@
+# Jira – DOCS Project
+
+You are helping manage Jira tickets for the Sumo Logic documentation team.
+
+## Project context
+
+* **Jira project:** DOCS
+* **Base URL:** https://sumologic.atlassian.net/browse/DOCS
+* **Cloud ID:** 247075db-3b0b-4f1b-92db-51683ab743a6
+
+## Ticket intake
+
+External requests from Sumo Logic employees come in via the JSM portal:
+https://sumologic.atlassian.net/servicedesk/customer/portal/26/group/75/create/378
+
+Tickets created via this command are created directly in the DOCS project and
+are distinct from portal-submitted requests.
+
+## Team members
+
+| Name | Role |
+|---|---|
+| Kim | Lead Technical Writer |
+| Amee | Contractor Technical Writer |
+| Jagadisha | Contractor Technical Writer |
+| John | Senior Technical Writer |
+| Mark | Manager |
+
+Kim's Atlassian account ID: 628bc65bc65b720069610ad1
+For all other team members, use the Atlassian MCP to look up account ID by display name before assigning.
+
+## Technical Area → Writer assignments
+
+Use this to set the default assignee when creating tickets, and to filter issues by owner.
+
+| Technical Area | Writer |
+|---|---|
+| Alerts (Monitors, Sched. Search, Webhooks) | Amee |
+| APIs | Kim |
+| APM (Traces, RUM) | Kim |
+| Apps/Integrations | Amee |
+| Automation | John |
+| Cloud Infrastructure Security | John |
+| Cloud SIEM | John |
+| Cloud SOAR | John |
+| Collectors/Sources | Amee |
+| Dashboards | Jagadisha |
+| Getting Started (Product/Observability) | Kim |
+| Getting Started (Security) | John |
+| Log Search | Jagadisha |
+| Manage (Administrator) | Jagadisha |
+| Manage (Analyst) | Jagadisha |
+| Manage (Data Forwarding) | Jagadisha |
+| Manage (Fields, FERs, Partitions, Data Tiers, Ingestion, Sched Views, Billing, Sharing) | Jagadisha |
+| Manage (Security, Users, Roles) | Jagadisha |
+| Metrics | John |
+| Mobot | Kim |
+| Observability (AWSO) | Amee |
+| Observability (Azure) | Jagadisha |
+| Observability (Kubernetes) | John |
+| Observability (SLO) | John |
+| Observability (Tracing) | Kim |
+| Other | unassigned |
+| Platform Services | John |
+| Sensu | John |
+| Threat Intelligence | John |
+
+## Default behavior
+
+When invoked, ask the user what they want to do:
+
+* **Create a ticket**. Ask for title, Technical Area, type (Task/Bug/Story), and description. Auto-suggest the default assignee based on the Technical Area table above.
+* **Look up a ticket**. Search by issue key (e.g. DOCS-1234) or keyword.
+* **Update a ticket**. Ask which field to update (status, description, assignee, priority, Technical Area).
+* **List open tickets**. Fetch open issues in DOCS, sorted by created date descending.
+* **My tickets**. Fetch issues assigned to the current user.
+* **Transition a ticket**. Move through workflow states: To Do → In Progress → In Review → Done.
+
+## Style rules for ticket descriptions
+
+* Sentence case for titles
+* Benefit-driven summaries, not feature lists
+* Active voice, plain language
+* No em dashes
+* Descriptions under 150 words unless complex
+* Bug tickets must include: **Steps to reproduce**, **Expected behavior**, **Actual behavior**
+* Use `contentFormat: markdown` for all descriptions
+
+## Output format
+
+After any action, confirm what was done and provide a direct link:
+https://sumologic.atlassian.net/browse/DOCS-[issue number]

.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "atlassian": {
+      "type": "http",
+      "url": "https://mcp.atlassian.com/v1/mcp"
+    }
+  }
+}