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>
This commit is contained in:
Christian Gick
2026-02-08 17:09:34 +02:00
parent 9042bf0878
commit 507e98ef8e

View File

@@ -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: { export async function createSessionIssue(params: {
sessionNumber: number | null; sessionNumber: number | null;
@@ -81,7 +81,7 @@ export async function createSessionIssue(params: {
method: 'POST', method: 'POST',
body: JSON.stringify({ body: JSON.stringify({
fields: { fields: {
project: { key: 'CF' }, project: { key: project },
summary, summary,
description: { description: {
type: 'doc', type: 'doc',