Issue tracker: Jira (solcom P2503)

Project basics

Cloud host

solcomde.atlassian.net

Project key

P2503

Issue format

P2503-<number>

Issue types

Story, Bug, Task, Epic, Sub-task

Board

Backlog Board

Authentication

Run the Atlassian MCP auth flow once per environment:

mcp__claude_ai_Atlassian__authenticate
Follow the OAuth flow in browser
mcp__claude_ai_Atlassian__complete_authentication

After that, the MCP server exposes Jira read/write tools (search issues, get issue, create issue, add comment, transition status, set labels, etc.). Prefer those over curling the REST API directly.

Conventions

Create an issue: create in project P2503 via the Atlassian MCP server. Default issue type is Task unless context clearly suggests Story / Bug / Epic. New issues land in status IDEE.
Read an issue: fetch by key (e.g. P2503-123) including comments, labels, and current status.
List / search issues: use JQL via the MCP server — e.g. project = P2503 AND status = "TO DO" or project = P2503 AND labels = "needs-triage".
Comment on an issue: add a comment via the MCP server, addressed by issue key.
Apply / remove labels: edit the issue's labels field. Triage labels are mapped in docs/agents/triage-labels.html.
Transition status: move through the workflow. Don't skip transitions just because Jira allows it.

Workflow

IDEE → TO DO → IN PROGRESS → ZU REVIEW → DONE

When a skill says…

"pub"

"publish to the issue tracker"

Create a Jira issue in project P2503. New work starts in IDEE (or TO DO if already groomed).

"fet"

"fetch the relevant ticket"

Resolve the issue key (P2503-<number>) from context and fetch via the Atlassian MCP server, including comments and status.

"rev"

"mark ready for review"

Transition the issue to status ZU REVIEW.