From 507e98ef8ebb126f56be7480c6d17a4898dc44c7 Mon Sep 17 00:00:00 2001
From: Christian Gick <service@agiliton.eu>
Date: Sun, 8 Feb 2026 17:09:34 +0200
Subject: [PATCH] fix: Use actual project key for session Jira issues instead
 of hardcoded CF

The project parameter was passed to createSessionIssue() but ignored -
all sessions were created in the CF Jira project regardless of the
actual session project (ST, LLB, GB, etc.).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 src/services/jira.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/services/jira.ts b/src/services/jira.ts
index b84dd2e..984ea68 100644
--- a/src/services/jira.ts
+++ b/src/services/jira.ts
@@ -48,7 +48,7 @@ async function jiraFetch(path: string, options: RequestInit = {}): Promise<Respo
 }
 
 /**
- * Create a Jira issue in the CF project for session tracking.
+ * Create a Jira issue for session tracking in the given project.
  */
 export async function createSessionIssue(params: {
   sessionNumber: number | null;
@@ -81,7 +81,7 @@ export async function createSessionIssue(params: {
       method: 'POST',
       body: JSON.stringify({
         fields: {
-          project: { key: 'CF' },
+          project: { key: project },
           summary,
           description: {
             type: 'doc',