Merge pull request #77 from Blazity/feat/jira-service-token

Feat/jira service token

Author: woywro

.claude/skills/init-env/SKILL.md

@@ -123,7 +123,7 @@ The CLI is interactive — let the user complete it. On success, `.vercel/projec
 
 Invoke the `init-jira` subskill via the Skill tool. It detects state and runs phase 1 because `JIRA_BASE_URL` is not yet set in Vercel:
 
-- Asks for `JIRA_BASE_URL` / `JIRA_EMAIL` / `JIRA_API_TOKEN` / `JIRA_PROJECT_KEY` / `COLUMN_AI` / `COLUMN_AI_REVIEW` / `COLUMN_BACKLOG`.
+- Asks for `JIRA_BASE_URL` / `JIRA_API_TOKEN` / `JIRA_PROJECT_KEY` / `COLUMN_AI` / `COLUMN_AI_REVIEW` / `COLUMN_BACKLOG`.
 - **Pre-generates `JIRA_WEBHOOK_SECRET`** via `openssl rand -hex 32`.
 - Emits a single `.env`-format paste-template.
 - Walks the user through pasting into the Vercel dashboard (Project Settings → Environment Variables).

.claude/skills/init-jira/SKILL.md

@@ -66,8 +66,7 @@ Hold the value for the paste-template below. Even if the user later defers webho
 Ask in one prompt (single credential bundle):
 
 - `JIRA_BASE_URL` — e.g. `https://acme.atlassian.net` (no trailing slash, no `/jira`)
-- `JIRA_EMAIL` — the bot account's email
-- `JIRA_API_TOKEN` — created at https://id.atlassian.com/manage-profile/security/api-tokens
+- `JIRA_API_TOKEN` — scoped service-account token (Bearer) from https://id.atlassian.com/manage-profile/security/api-tokens
 - `JIRA_PROJECT_KEY` — e.g. `AWT`
 
 Then ask:
@@ -84,7 +83,6 @@ Print this single block for the user to copy into Vercel → Project Settings 
 
 ```
 JIRA_BASE_URL=<value>
-JIRA_EMAIL=<value>
 JIRA_API_TOKEN=<value>
 JIRA_PROJECT_KEY=<value>
 COLUMN_AI=<value>

.claude/skills/init-jira/references/column-statuses.md

@@ -39,8 +39,9 @@ Each column should contain exactly one status with the matching name. Don't put
 ## Verify the status spelling
 
 ```bash
-curl -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
-  "$JIRA_BASE_URL/rest/api/3/project/$JIRA_PROJECT_KEY/statuses" | \
+CLOUD_ID=$(curl -s "$JIRA_BASE_URL/_edge/tenant_info" | jq -r .cloudId)
+curl -H "Authorization: Bearer $JIRA_API_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$CLOUD_ID/rest/api/3/project/$JIRA_PROJECT_KEY/statuses" | \
   jq '.[].statuses[].name'
 ```
 

.claude/skills/init-jira/references/transitions.md

@@ -32,8 +32,9 @@ If the source status doesn't have an outbound transition to the target, draw a n
 For an issue currently in `AI`:
 
 ```bash
-curl -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
-  "$JIRA_BASE_URL/rest/api/3/issue/$JIRA_PROJECT_KEY-1/transitions" | \
+CLOUD_ID=$(curl -s "$JIRA_BASE_URL/_edge/tenant_info" | jq -r .cloudId)
+curl -H "Authorization: Bearer $JIRA_API_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$CLOUD_ID/rest/api/3/issue/$JIRA_PROJECT_KEY-1/transitions" | \
   jq '.transitions[] | {name, to: .to.name}'
 ```
 

.env.e2e.example

@@ -1,9 +1,8 @@
 # Target server
 E2E_BASE_URL=https://your-staging.vercel.app
 
-# Jira
+# Jira (scoped service-account Bearer token; routed through api.atlassian.com)
 JIRA_BASE_URL=https://your-domain.atlassian.net
-JIRA_EMAIL=your-email@example.com
 JIRA_API_TOKEN=
 JIRA_PROJECT_KEY=PROJ
 JIRA_WEBHOOK_SECRET=

.env.example

@@ -1,7 +1,8 @@
 # Issue Tracker (Jira)
 # ISSUE_TRACKER_KIND defaults to "jira" (only supported tracker today).
 JIRA_BASE_URL=https://your-domain.atlassian.net
-JIRA_EMAIL=your-email@example.com
+# Scoped service-account API token (Bearer). Issue from id.atlassian.com
+# under the bot account; requests are routed through api.atlassian.com.
 JIRA_API_TOKEN=your-jira-api-token
 JIRA_PROJECT_KEY=PROJ
 

.github/workflows/ci.yml

@@ -35,7 +35,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}
@@ -88,7 +87,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}
@@ -141,7 +139,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}

.github/workflows/e2e.yml

@@ -29,7 +29,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}
@@ -85,7 +84,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}
@@ -141,7 +139,6 @@ jobs:
     env:
       E2E_BASE_URL: ${{ secrets.E2E_BASE_URL }}
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
-      JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
       JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
       JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
       JIRA_WEBHOOK_SECRET: ${{ secrets.JIRA_WEBHOOK_SECRET }}