WIP jira ticket to spec

src/functions/jira-to-test-spec/.env.example

@@ -0,0 +1,55 @@
+# Main repository configuration
+MAIN_REPO_URL=https://github.com/Ebitda-SRL/test-ai-code-agents.git
+# Use either token or username/password for main repo
+MAIN_REPO_TOKEN=your_token_here
+# OR
+MAIN_REPO_USERNAME=your_username_here
+MAIN_REPO_PASSWORD=your_password_here
+
+# GitHub credentials
+# Use either token or username/password for GitHub
+GITHUB_TOKEN=your_github_token_here
+# OR
+GITHUB_USERNAME=your_github_username_here
+GITHUB_PASSWORD=your_github_password_here
+
+# Gitea credentials
+GITEA_USERNAME=your_gitea_username_here
+GITEA_PASSWORD=your_gitea_password_here
+
+# Jira credentials
+JIRA_BASE_URL=your_jira_base_url_here
+JIRA_USERNAME=your_jira_username_here
+JIRA_API_TOKEN=your_jira_api_token_here
+
+# Google Cloud configuration
+GOOGLE_CLOUD_PROJECT_ID=your_gcp_project_id_here
+GOOGLE_CLOUD_LOCATION=us-central1
+GEMINI_MODEL=gemini-2.0-flash-lite-001
+
+# Google Cloud Authentication
+# You can authenticate using one of the following methods:
+# 1. API key (for local development)
+GOOGLE_API_KEY=your_google_api_key_here
+# 2. Service account key file (for production)
+# Set this environment variable to the path of your service account key file
+# GOOGLE_APPLICATION_CREDENTIALS=/path/to/your/service-account-key.json
+# 3. Application Default Credentials (ADC)
+# No environment variables needed if using ADC
+# See: https://cloud.google.com/docs/authentication/application-default-credentials
+
+# Function configuration
+# Set to 'true' to enable debug logging
+DEBUG=false
+# Set to 'true' to use local repository instead of cloning
+USE_LOCAL_REPO=false
+# Dry run options
+# Set to 'true' to skip Gemini API calls (returns mock responses)
+DRY_RUN_SKIP_GEMINI=false
+# Set to 'true' to skip creating commits and PRs
+DRY_RUN_SKIP_COMMITS=false
+# Set to 'true' to skip updating Jira ticket status
+DRY_RUN_SKIP_JIRA_STATUS_UPDATE=false
+
+# Jira label to identify workitems to be processed (will be removed after processing)
+JIRA_TO_TEST_SPEC_LABEL=jira-to-test-spec

src/functions/jira-to-test-spec/.gitignore

@@ -0,0 +1,4 @@
+node_modules/
+dist/
+.env
+coverage/

src/functions/jira-to-test-spec/README.md

@@ -0,0 +1,128 @@
+# Jira to Test Spec Function
+
+This function fetches work items from Jira and generates test specifications in the cucumber format.
+
+## Overview
+
+The `jira-to-test-spec` function is based on the `prompts-to-test-spec` function, but instead of reading work items from the filesystem, it fetches them from Jira using the Jira API. It then processes these work items to generate test specifications in the cucumber format.
+
+## Configuration
+
+The function requires the following environment variables to be set:
+
+### Main Repository Configuration
+- `MAIN_REPO_URL`: URL of the main repository
+- `MAIN_REPO_TOKEN` or `MAIN_REPO_USERNAME`/`MAIN_REPO_PASSWORD`: Credentials for the main repository
+
+### Jira Configuration
+- `JIRA_BASE_URL`: Base URL of the Jira instance
+- `JIRA_USERNAME`: Username for Jira authentication
+- `JIRA_API_TOKEN`: API token for Jira authentication
+
+### Google Cloud Configuration
+- `GOOGLE_CLOUD_PROJECT_ID`: Google Cloud project ID
+- `GOOGLE_CLOUD_LOCATION`: Google Cloud location (default: 'us-central1')
+- `GEMINI_MODEL`: Gemini model to use (default: 'gemini-1.5-pro')
+- `GOOGLE_API_KEY`: Google API key for local development
+
+### Function Configuration
+- `DEBUG`: Set to 'true' to enable debug logging
+- `USE_LOCAL_REPO`: Set to 'true' to use local repository instead of cloning
+- `DRY_RUN_SKIP_GEMINI`: Set to 'true' to skip Gemini API calls (returns mock responses)
+- `DRY_RUN_SKIP_COMMITS`: Set to 'true' to skip creating commits and PRs
+- `DRY_RUN_SKIP_JIRA_STATUS_UPDATE`: Set to 'true' to skip updating Jira ticket status
+- `JIRA_TO_TEST_SPEC_LABEL`: Label used to identify Jira issues to be processed (default: 'jira-to-test-spec')
+
+## Project Configuration
+
+Each project should have an `INFO.md` file with the following information:
+
+```markdown
+# Project Name
+
+- [x] Repo host: <repo host url, eg https://gitea.fteamdev.valuya.be/ or https://github.com/organizations/Ebitda-SRL>
+- [x] Repo url: <url of the project repository>
+- [x] Target branch: <target branch for the PR>
+- [ ] AI guidelines: <path to ai guidelines md file in the project repo>
+- [x] Jira component: <component of the project in jira>
+- [x] Jira labels: <labels of the tickets in jira, comma-separated>
+- [x] Jira project: <JIRA project name>
+- [x] Write paths: <comma-separated list of path filters (globs) to which the agent can write>
+```
+
+## Usage
+
+### Local Development
+
+1. Clone the repository
+2. Navigate to the `src/functions/jira-to-test-spec` directory
+3. Copy `.env.example` to `.env` and fill in the required values
+4. Install dependencies: `npm install`
+5. Run the function locally: `npm run dev`
+
+### Deployment
+
+To deploy the function to Google Cloud Functions:
+
+```bash
+npm run deploy
+```
+
+## API
+
+### HTTP Endpoint
+
+The function exposes an HTTP endpoint that can be called to process projects:
+
+```
+POST /jiraToTestSpecHttp
+```
+
+### Cloud Event
+
+The function can also be triggered by a Cloud Event:
+
+```
+jiraToTestSpecEvent
+```
+
+## Implementation Details
+
+The function works as follows:
+
+1. It finds all projects in the prompts directory
+2. For each project, it:
+   - Clones the project repository
+   - Fetches work items from Jira based on the project's Jira configuration
+   - Processes each work item to generate test specifications
+   - For each work item:
+     - Creates a separate branch with the work item key
+     - Commits changes related to the work item
+     - Creates a pull request for the work item
+     - Updates the Jira ticket status to "Review" (unless skipped)
+     - Generates a summary using Gemini
+     - Adds a comment to the Jira ticket with the PR link and summary (unless skipped)
+     - Resets the repository to the main branch and removes any dangling files
+
+### Jira Integration
+
+The Jira integration uses the Jira REST API to:
+1. Fetch issues based on the project's Jira component, labels, and project name
+   - Only issues with the `JIRA_TO_TEST_SPEC_LABEL` label (default: 'jira-to-test-spec') are processed
+2. Update issue status to "Review" after creating a pull request
+3. Add comments to issues with pull request links and summaries
+4. Remove the `JIRA_TO_TEST_SPEC_LABEL` label from the issue after processing
+   - This prevents the issue from being processed again in subsequent runs
+
+### Individual PRs for Work Items
+
+Each Jira work item is processed independently with its own:
+- Git branch (named after the Jira ticket key)
+- Commit
+- Pull request
+- Jira status update
+- Jira comment
+
+### Skipping Jira Updates
+
+If you want to skip updating Jira ticket status and adding comments, set the `DRY_RUN_SKIP_JIRA_STATUS_UPDATE` environment variable to `true`.

src/functions/jira-to-test-spec/package.json

@@ -0,0 +1,41 @@
+{
+  "name": "jira-to-test-spec",
+  "version": "1.0.0",
+  "scripts": {
+    "build": "tsc",
+    "prestart": "npm run build",
+    "deploy": "gcloud functions deploy jiraToTestSpecHttp --gen2 --runtime=nodejs20 --source=. --trigger-http --allow-unauthenticated",
+    "deploy:event": "gcloud functions deploy jiraToTestSpecEvent --gen2 --runtime=nodejs20 --source=. --trigger-event=google.cloud.storage.object.v1.finalized --trigger-resource=YOUR_BUCKET_NAME",
+    "clean": "rm -rf dist",
+    "test": "jest",
+    "test:watch": "jest --watch",
+    "dev": "npm run build && functions-framework --target=jiraToTestSpecHttp --port=18080",
+    "dev:watch": "concurrently \"tsc -w\" \"nodemon --watch dist/ --exec functions-framework --target=jiraToTestSpecHttp --port=18080\"",
+    "dev:event": "npm run build && functions-framework --target=jiraToTestSpecEvent --signature-type=event"
+  },
+  "main": "dist/index.js",
+  "dependencies": {
+    "@google-cloud/functions-framework": "^3.0.0",
+    "@google-cloud/vertexai": "^0.5.0",
+    "axios": "^1.6.7",
+    "dotenv": "^16.4.5",
+    "shared-functions": "file:../shared",
+    "simple-git": "^3.23.0"
+  },
+  "devDependencies": {
+    "@types/express": "^5.0.3",
+    "@types/jest": "^29.5.12",
+    "@types/node": "^20.11.30",
+    "concurrently": "^8.2.2",
+    "jest": "^29.7.0",
+    "nodemon": "^3.0.3",
+    "ts-jest": "^29.1.2",
+    "typescript": "^5.8.3"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "files": [
+    "dist"
+  ]
+}

src/functions/jira-to-test-spec/src/config.ts

@@ -0,0 +1,151 @@
+/**
+ * Configuration module for loading environment variables
+ */
+import * as dotenv from 'dotenv';
+import * as path from 'path';
+
+// Load environment variables from .env file
+dotenv.config({ path: path.resolve(__dirname, '../.env') });
+
+// Main repository configuration
+export const MAIN_REPO_URL = process.env.MAIN_REPO_URL || '';
+export const MAIN_REPO_TOKEN = process.env.MAIN_REPO_TOKEN;
+export const MAIN_REPO_USERNAME = process.env.MAIN_REPO_USERNAME;
+export const MAIN_REPO_PASSWORD = process.env.MAIN_REPO_PASSWORD;
+
+// GitHub credentials
+export const GITHUB_TOKEN = process.env.GITHUB_TOKEN;
+export const GITHUB_USERNAME = process.env.GITHUB_USERNAME;
+export const GITHUB_PASSWORD = process.env.GITHUB_PASSWORD;
+
+// Gitea credentials
+export const GITEA_USERNAME = process.env.GITEA_USERNAME;
+export const GITEA_PASSWORD = process.env.GITEA_PASSWORD;
+
+// Jira credentials
+export const JIRA_BASE_URL = process.env.JIRA_BASE_URL || '';
+export const JIRA_USERNAME = process.env.JIRA_USERNAME || '';
+export const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN || '';
+
+// Google Cloud configuration
+export const GOOGLE_CLOUD_PROJECT_ID = process.env.GOOGLE_CLOUD_PROJECT_ID || '';
+export const GOOGLE_CLOUD_LOCATION = process.env.GOOGLE_CLOUD_LOCATION || 'us-central1';
+export const GEMINI_MODEL = process.env.GEMINI_MODEL || 'gemini-1.5-pro';
+export const GOOGLE_API_KEY = process.env.GOOGLE_API_KEY;
+
+// Function configuration
+export const DEBUG = process.env.DEBUG === 'true';
+export const USE_LOCAL_REPO = process.env.USE_LOCAL_REPO === 'true';
+export const DRY_RUN_SKIP_GEMINI = process.env.DRY_RUN_SKIP_GEMINI === 'true';
+export const DRY_RUN_SKIP_COMMITS = process.env.DRY_RUN_SKIP_COMMITS === 'true';
+export const DRY_RUN_SKIP_JIRA_STATUS_UPDATE = process.env.DRY_RUN_SKIP_JIRA_STATUS_UPDATE === 'true';
+
+// Jira label configuration
+export const JIRA_TO_TEST_SPEC_LABEL = process.env.JIRA_TO_TEST_SPEC_LABEL || 'jira-to-test-spec';
+
+// Validate required configuration
+export function validateConfig(): void {
+  const missingVars: string[] = [];
+
+  // Only check for main repo URL and credentials if not using local repo
+  if (!USE_LOCAL_REPO) {
+    if (!MAIN_REPO_URL) {
+      missingVars.push('MAIN_REPO_URL');
+    }
+
+    if (!MAIN_REPO_TOKEN && (!MAIN_REPO_USERNAME || !MAIN_REPO_PASSWORD)) {
+      missingVars.push('MAIN_REPO_TOKEN or MAIN_REPO_USERNAME/MAIN_REPO_PASSWORD');
+    }
+  }
+
+  // Check for Jira credentials
+  if (!JIRA_BASE_URL) {
+    missingVars.push('JIRA_BASE_URL');
+  }
+
+  if (!JIRA_USERNAME) {
+    missingVars.push('JIRA_USERNAME');
+  }
+
+  if (!JIRA_API_TOKEN) {
+    missingVars.push('JIRA_API_TOKEN');
+  }
+
+  if (!GOOGLE_CLOUD_PROJECT_ID) {
+    missingVars.push('GOOGLE_CLOUD_PROJECT_ID');
+  }
+
+  if (missingVars.length > 0) {
+    throw new Error(`Missing required environment variables: ${missingVars.join(', ')}`);
+  }
+}
+
+// Get repository credentials for the main repository
+export function getMainRepoCredentials(): { type: 'username-password' | 'token'; username?: string; password?: string; token?: string } {
+  if (USE_LOCAL_REPO) {
+    // Return dummy credentials when using local repo
+    return {
+      type: 'token',
+      token: 'dummy-token-for-local-repo'
+    };
+  }
+
+  if (MAIN_REPO_TOKEN) {
+    return {
+      type: 'token',
+      token: MAIN_REPO_TOKEN
+    };
+  } else if (MAIN_REPO_USERNAME && MAIN_REPO_PASSWORD) {
+    return {
+      type: 'username-password',
+      username: MAIN_REPO_USERNAME,
+      password: MAIN_REPO_PASSWORD
+    };
+  }
+
+  throw new Error('No credentials available for the main repository');
+}
+
+// Get GitHub credentials
+export function getGithubCredentials(): { type: 'username-password' | 'token'; username?: string; password?: string; token?: string } | undefined {
+  if (GITHUB_TOKEN) {
+    return {
+      type: 'token',
+      token: GITHUB_TOKEN
+    };
+  } else if (GITHUB_USERNAME && GITHUB_PASSWORD) {
+    return {
+      type: 'username-password',
+      username: GITHUB_USERNAME,
+      password: GITHUB_PASSWORD
+    };
+  }
+
+  return undefined;
+}
+
+// Get Gitea credentials
+export function getGiteaCredentials(): { type: 'username-password'; username: string; password: string } | undefined {
+  if (GITEA_USERNAME && GITEA_PASSWORD) {
+    return {
+      type: 'username-password',
+      username: GITEA_USERNAME,
+      password: GITEA_PASSWORD
+    };
+  }
+
+  return undefined;
+}
+
+// Get Jira credentials
+export function getJiraCredentials(): { username: string; apiToken: string; baseUrl: string } {
+  if (!JIRA_USERNAME || !JIRA_API_TOKEN || !JIRA_BASE_URL) {
+    throw new Error('Jira credentials not found');
+  }
+
+  return {
+    username: JIRA_USERNAME,
+    apiToken: JIRA_API_TOKEN,
+    baseUrl: JIRA_BASE_URL
+  };
+}

src/functions/jira-to-test-spec/src/index.ts

@@ -0,0 +1,90 @@
+import {CloudEvent, cloudEvent, http} from '@google-cloud/functions-framework';
+import {ProcessorService} from './services/processor-service';
+import {validateConfig, DRY_RUN_SKIP_GEMINI, DRY_RUN_SKIP_COMMITS} from './config';
+import {ProcessResult, HttpResponse, ProjectSummary} from './types';
+
+// Validate configuration on startup
+try {
+    validateConfig();
+} catch (error) {
+    console.error('Configuration error:', error instanceof Error ? error.message : String(error));
+    // Don't throw here to allow the function to start, but it will fail when executed
+}
+
+/**
+ * Format process results into a concise HTTP response
+ * @param results Process results from the processor service
+ * @returns Formatted HTTP response
+ */
+export function formatHttpResponse(results: ProcessResult[]): HttpResponse {
+    // Count successful and failed projects
+    const projectsSucceeded = results.filter(r => !r.error).length;
+    const projectsFailed = results.filter(r => !!r.error).length;
+
+    // Find main PR URL if any
+    const mainPullRequestUrl = results.find(r => r.pullRequestUrl)?.pullRequestUrl;
+
+    // Format project summaries
+    const projects: ProjectSummary[] = results.map(result => {
+        // Count workitems
+        const workitemsProcessed = result.processedWorkitems.length;
+        const filesWritten = result.processedWorkitems.reduce((sum, w) => sum + (w.filesWritten?.length || 0), 0);
+
+        return {
+            name: result.project.name,
+            success: !result.error,
+            error: result.error,
+            workitemsProcessed,
+            filesWritten,
+            pullRequestUrl: result.pullRequestUrl,
+        };
+    });
+
+    return {
+        success: projectsFailed === 0,
+        projectsProcessed: results.length,
+        projectsSucceeded,
+        projectsFailed,
+        mainPullRequestUrl,
+        projects
+    };
+}
+
+/**
+ * HTTP endpoint for the jira-to-test-spec function
+ */
+http('jiraToTestSpecHttp', async (req, res): Promise<void> => {
+    try {
+        const processor = new ProcessorService();
+        const results = await processor.processProjects();
+        const response = formatHttpResponse(results);
+
+        res.status(200).json(response);
+    } catch (error) {
+        console.error('Error processing projects:', error);
+        const errorMessage = error instanceof Error ? error.message : String(error);
+        res.status(500).json({
+            success: false,
+            projectsProcessed: 0,
+            projectsSucceeded: 0,
+            projectsFailed: 1,
+            projects: [],
+            error: errorMessage
+        });
+    }
+});
+
+/**
+ * Cloud Event handler for the jira-to-test-spec function
+ */
+cloudEvent('jiraToTestSpecEvent', async (event: CloudEvent<any>): Promise<void> => {
+    try {
+        console.log('Received event:', event.type);
+        const processor = new ProcessorService();
+        await processor.processProjects();
+        console.log('Processing completed successfully');
+    } catch (error) {
+        console.error('Error processing projects:', error);
+        throw error;
+    }
+});

src/functions/jira-to-test-spec/src/services/jira-workitems-service.ts

@@ -0,0 +1,621 @@
+/**
+ * Service for handling Jira workitem operations within a project
+ */
+import * as fs from 'fs';
+import * as path from 'path';
+import axios, {AxiosError} from 'axios';
+import {JiraIssue, ProcessedWorkItem, ProcessResult, Workitem, JiraCredentials} from '../types';
+import {ProjectService} from './project-service';
+import {DRY_RUN_SKIP_GEMINI, JIRA_TO_TEST_SPEC_LABEL} from '../config';
+import {
+    GeminiFileSystemService, GeminiService,
+    Project,
+    RepositoryService as SharedRepositoryService,
+} from 'shared-functions';
+import {GeminiResponse} from "shared-functions/dist/services/gemini-file-system-service";
+
+export class JiraWorkitemsService {
+    private projectService: ProjectService;
+    private sharedRepositoryService: SharedRepositoryService;
+    private jiraCredentials: JiraCredentials;
+
+    /**
+     * Get the Jira base URL
+     * @returns Jira base URL
+     */
+    getJiraBaseUrl(): string {
+        return this.jiraCredentials.baseUrl;
+    }
+
+    constructor(jiraCredentials: JiraCredentials) {
+        this.projectService = new ProjectService();
+        this.sharedRepositoryService = new SharedRepositoryService(
+            path.join(require('os').tmpdir(), 'jira-to-test-spec')
+        );
+        this.jiraCredentials = jiraCredentials;
+    }
+
+    /**
+     * Find workitems for a project from Jira
+     * @param project Project to find workitems for
+     * @returns Array of workitems
+     */
+    async findWorkitems(project: Project): Promise<Workitem[]> {
+        console.log(`JiraWorkitemsService: Finding workitems for project ${project.name}`);
+        try {
+            // Find all workitems in Jira for the project
+            const workitems = await this.findJiraWorkitems(project);
+            console.log(`JiraWorkitemsService: Found ${workitems.length} workitems in project ${project.name}`);
+            return workitems;
+        } catch (error) {
+            console.error(`Error finding workitems for project ${project.name}:`, error);
+            throw error;
+        }
+    }
+
+    /**
+     * Process the project workitems from Jira
+     * @param project Project to process
+     * @param projectRepoPath Path to the project repository
+     * @returns Process result
+     */
+    async processProject(project: Project, projectRepoPath: string): Promise<ProcessResult> {
+        console.log(`JiraWorkitemsService: Processing project ${project.name}`);
+
+        try {
+            // Find all workitems in Jira for the project
+            const workitems = await this.findWorkitems(project);
+
+            // Skip if no workitems found
+            if (workitems.length === 0) {
+                return {
+                    project: project,
+                    processedWorkitems: []
+                };
+            }
+
+            // Read project guidelines
+            const projectGuidelines = await this.projectService.readProjectGuidelines(project.path);
+
+            // Collect all relevant files from the project directory
+            const relevantFiles = await this.projectService.collectRelevantFiles(project, projectRepoPath);
+
+            // Process each workitem
+            const processedWorkitems: ProcessedWorkItem[] = [];
+            for (const workitem of workitems) {
+                const result: ProcessedWorkItem = await this.processWorkitem(project, projectRepoPath, workitem, projectGuidelines, relevantFiles);
+                processedWorkitems.push(result);
+            }
+
+            return {
+                project: project,
+                processedWorkitems
+            };
+        } catch (error) {
+            console.error(`Error processing project ${project.name}:`, error);
+            return {
+                project: project,
+                processedWorkitems: [],
+                error: error instanceof Error ? error.message : String(error)
+            };
+        }
+    }
+
+    /**
+     * Find all workitems in Jira for a project
+     * @param project Project to find workitems for
+     * @returns Array of workitems
+     */
+    private async findJiraWorkitems(project: Project): Promise<Workitem[]> {
+        try {
+            if (!project.jiraComponent || !project.jiraProject) {
+                throw new Error(`Project ${project.name} is missing Jira component or project information`);
+            }
+
+            // Construct JQL query based on project info
+            let jql = `project = "${project.jiraProject}"`;
+
+            if (project.jiraComponent) {
+                jql += ` AND component = "${project.jiraComponent}"`;
+            }
+
+            // Always include the configured label
+            jql += ` AND labels = "${JIRA_TO_TEST_SPEC_LABEL}"`;
+
+            // Include additional labels from project configuration if any
+            if (project.jiraLabels && project.jiraLabels.length > 0) {
+                const additionalLabels = project.jiraLabels.filter(label => label !== JIRA_TO_TEST_SPEC_LABEL);
+                if (additionalLabels.length > 0) {
+                    jql += ` AND labels in (${additionalLabels.map(label => `"${label}"`).join(',')})`;
+                }
+            }
+
+            // Add status filter to only get active issues
+            jql += ` AND  status in ("Selected For Development")`;
+
+            console.log(`JQL query: ${jql}`);
+
+            // Make API request to Jira
+            const response = await this.searchJiraIssues(jql);
+
+            // Convert Jira issues to workitems
+            return response.issues.map(issue => this.convertJiraIssueToWorkitem(issue));
+        } catch (error) {
+            console.error('Error finding Jira workitems:', error);
+            throw error;
+        }
+    }
+
+    /**
+     * Search for Jira issues using JQL
+     * @param jql JQL query
+     * @returns Search results
+     */
+    private async searchJiraIssues(jql: string): Promise<{ issues: JiraIssue[] }> {
+        try {
+            const url = `${this.jiraCredentials.baseUrl}/rest/api/2/search`;
+
+            const response = await axios.post(
+                url,
+                {
+                    jql,
+                    maxResults: 10,
+                    fields: ['summary', 'description', 'status']
+                },
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            console.log(`Jira response: ${JSON.stringify(response.data)}`);
+            return response.data;
+        } catch (error) {
+            console.error('Error searching Jira issues:' + `${error}`);
+            const anyError = error as AxiosError;
+            if (anyError && anyError.response && anyError.response.data) {
+                console.error(anyError.response.data);
+            }
+            throw new Error(`Error searching Jira issues: ${error}`);
+        }
+    }
+
+    /**
+     * Convert a Jira issue to a workitem
+     * @param issue Jira issue
+     * @returns Workitem
+     */
+    private convertJiraIssueToWorkitem(issue: JiraIssue): Workitem {
+        return {
+            name: `${issue.key}`,
+            title: issue.fields.summary,
+            description: issue.fields.description || '',
+            jiraReference: issue.key,
+            isActive: true, // All issues from Jira are considered active
+            key: issue.key
+        };
+    }
+
+    /**
+     * Process a workitem using Gemini
+     * @param project Project containing the workitem
+     * @param projectRepoPath Path to the project repository
+     * @param workitem Workitem to process
+     * @param projectGuidelines Project guidelines
+     * @param relevantFiles Additional relevant files to include in the prompt
+     * @returns Result of the processing
+     */
+    async processWorkitem(
+        project: Project,
+        projectRepoPath: string,
+        workitem: Workitem,
+        projectGuidelines: string,
+        relevantFiles: Record<string, string>
+    ): Promise<ProcessedWorkItem> {
+        try {
+            // Set the current workitem
+            console.log(`JiraWorkitemsService: Processing workitem: ${workitem.name} (Active: ${workitem.isActive})`);
+
+            // Track processing time
+            const startTime = Date.now();
+
+            // Let Gemini decide what to do with the workitem
+            const result = await this.generateFeatureFile(
+                project,
+                projectRepoPath,
+                projectGuidelines,
+                workitem,
+                relevantFiles
+            );
+
+            // Calculate processing time
+            const processingTimeMs = Date.now() - startTime;
+
+            console.log(`JiraWorkitemsService: Completed processing workitem: ${workitem.name} (Files written: ${result.filesWritten.length}, Processing time: ${processingTimeMs}ms, Tokens: ${result.totalCost || 0})`);
+            return {
+                success: true,
+                workitem,
+                filesWritten: result.filesWritten,
+                filesRemoved: result.filesDeleted,
+                processingTimeMs,
+                inputTokens: result.inputCost,
+                outputTokens: result.outputCost,
+                totalTokens: result.totalCost,
+            };
+        } catch (error) {
+            console.error(`Error processing workitem ${workitem.name}:`, error);
+            return {
+                success: false,
+                workitem: workitem,
+                error: error instanceof Error ? error.message : String(error),
+            };
+        }
+    }
+
+    /**
+     * Generate feature file content using Gemini API
+     * @param projectRepoPath Path to the project repository
+     * @param guidelines Project guidelines
+     * @param workitemContent Workitem content
+     * @param workitemName Name of the workitem
+     * @param relevantFiles Additional relevant files to include in the prompt
+     * @returns Object containing the generated text, parsed decision, and files written/deleted
+     */
+    private async generateFeatureFile(
+        project: Project,
+        projectRepoPath: string,
+        guidelines: string,
+        workItem: Workitem,
+        relevantFiles: Record<string, string> = {}
+    ): Promise<GeminiResponse> {
+        const currentDate = new Date().toISOString();
+
+        // If dry run is enabled, return a mock feature file
+        if (DRY_RUN_SKIP_GEMINI) {
+            console.log(`[DRY RUN] Skipping Gemini API call for generating feature file for ${workItem.name}`);
+            return {
+                filesWritten: [],
+                filesDeleted: [],
+                stepOutcomes: [],
+                modelResponses: []
+            };
+        }
+
+        console.log(`Processing work item ${workItem.name}`);
+
+        // Prepare additional context from relevant files
+        let additionalContext = '';
+        for (const [filename, content] of Object.entries(relevantFiles)) {
+            additionalContext += `\n--- ${filename} ---\n${content}\n`;
+        }
+
+        // Import required configuration
+        const {GOOGLE_CLOUD_PROJECT_ID, GOOGLE_CLOUD_LOCATION, GEMINI_MODEL} = require('../config');
+
+        // Initialize the GeminiFileSystemService directly
+        const geminiFileSystemService = new GeminiFileSystemService(
+            GOOGLE_CLOUD_PROJECT_ID,
+            GOOGLE_CLOUD_LOCATION,
+            GEMINI_MODEL,
+            DRY_RUN_SKIP_GEMINI
+        );
+
+        // Get additional Jira issue details if needed
+        const jiraDetails = await this.getJiraIssueDetails(workItem.key);
+
+        const workItemPrompt = `\n`
+            + `WORK ITEM METADATA:\n`
+            + `Name: ${workItem.name}\n`
+            + `Title: ${workItem.title}\n`
+            + `Jira refs: ${workItem.jiraReference}\n`
+            + `Jira URL: ${this.jiraCredentials.baseUrl}/browse/${workItem.key}\n`
+            + `Active: ${workItem.isActive}\n`
+            + `--- START OF WORK ITEM CONTENT\n`
+            + `${workItem.description}\n`
+            + `--- END OF WORK ITEM CONTENT\n`;
+
+        console.debug(workItemPrompt);
+
+        // Process the model stream
+        const result = await geminiFileSystemService.processModelStream(
+            guidelines,
+            workItemPrompt,
+            projectRepoPath,
+            project.writePaths,
+            project.readPaths
+        );
+
+        return result;
+    }
+
+    /**
+     * Get additional details for a Jira issue
+     * @param issueKey Jira issue key
+     * @returns Additional details
+     */
+    private async getJiraIssueDetails(issueKey: string): Promise<any> {
+        try {
+            const url = `${this.jiraCredentials.baseUrl}/rest/api/2/issue/${issueKey}`;
+
+            const response = await axios.get(
+                url,
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            return response.data;
+        } catch (error) {
+            console.error(`Error getting details for Jira issue ${issueKey}:`, error);
+            return {};
+        }
+    }
+
+    /**
+     * Update the status of a Jira issue to "Review"
+     * @param issueKey Jira issue key
+     * @returns Success status
+     */
+    public async updateJiraIssueStatusToReview(issueKey: string): Promise<boolean> {
+        try {
+            // First, get the available transitions for the issue
+            const transitionsUrl = `${this.jiraCredentials.baseUrl}/rest/api/2/issue/${issueKey}/transitions`;
+
+            const transitionsResponse = await axios.get(
+                transitionsUrl,
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            // Find the transition ID for "Review" status
+            const transitions = transitionsResponse.data.transitions;
+            const reviewTransition = transitions.find((t: any) =>
+                t.to.name.toLowerCase() === 'review' ||
+                t.to.name.toLowerCase() === 'in review' ||
+                t.to.name.toLowerCase().includes('review')
+            );
+
+            if (!reviewTransition) {
+                console.error(`No transition to Review status found for issue ${issueKey}`);
+                return false;
+            }
+
+            // Perform the transition
+            await axios.post(
+                transitionsUrl,
+                {
+                    transition: {
+                        id: reviewTransition.id
+                    }
+                },
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            console.log(`Successfully updated issue ${issueKey} to Review status`);
+            return true;
+        } catch (error) {
+            console.error(`Error updating status for Jira issue ${issueKey}:`, error);
+            return false;
+        }
+    }
+
+    /**
+     * Add a comment to a Jira issue
+     * @param issueKey Jira issue key
+     * @param comment Comment text
+     * @returns Success status
+     */
+    public async addCommentToJiraIssue(issueKey: string, comment: string): Promise<boolean> {
+        try {
+            const url = `${this.jiraCredentials.baseUrl}/rest/api/2/issue/${issueKey}/comment`;
+
+            await axios.post(
+                url,
+                {
+                    body: comment
+                },
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            console.log(`Successfully added comment to issue ${issueKey}`);
+            return true;
+        } catch (error) {
+            console.error(`Error adding comment to Jira issue ${issueKey}:`, error);
+            return false;
+        }
+    }
+
+    /**
+     * Remove a label from a Jira issue
+     * @param issueKey Jira issue key
+     * @param label Label to remove
+     * @returns Success status
+     */
+    public async removeJiraIssueLabel(issueKey: string, label: string): Promise<boolean> {
+        try {
+            // First, get the current issue to retrieve its labels
+            const url = `${this.jiraCredentials.baseUrl}/rest/api/2/issue/${issueKey}`;
+
+            const response = await axios.get(
+                url,
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            // Get current labels
+            const currentLabels = response.data.fields.labels || [];
+
+            // Remove the specified label
+            const updatedLabels = currentLabels.filter((l: string) => l !== label);
+
+            // If the label wasn't found, no need to update
+            if (currentLabels.length === updatedLabels.length) {
+                console.log(`Label '${label}' not found on issue ${issueKey}`);
+                return true;
+            }
+
+            // Update the issue with the new labels
+            await axios.put(
+                url,
+                {
+                    fields: {
+                        labels: updatedLabels
+                    }
+                },
+                {
+                    auth: {
+                        username: this.jiraCredentials.username,
+                        password: this.jiraCredentials.apiToken
+                    },
+                    headers: {
+                        'Content-Type': 'application/json'
+                    }
+                }
+            );
+
+            console.log(`Successfully removed label '${label}' from issue ${issueKey}`);
+            return true;
+        } catch (error) {
+            console.error(`Error removing label from Jira issue ${issueKey}:`, error);
+            return false;
+        }
+    }
+
+    /**
+     * Generate a summary for a workitem using Gemini
+     * @param workitem Workitem to generate summary for
+     * @param pullRequestUrl Pull request URL
+     * @param filesWritten Files written during processing
+     * @param processingTimeMs Time taken to process the workitem in milliseconds
+     * @param inputTokens Number of input tokens consumed
+     * @param outputTokens Number of output tokens consumed
+     * @param totalTokens Total number of tokens consumed
+     * @returns Generated summary
+     */
+    public async generateWorkitemSummary(
+        workitem: Workitem,
+        pullRequestUrl: string,
+        filesWritten: string[],
+        processingTimeMs?: number,
+        inputTokens?: number,
+        outputTokens?: number,
+        totalTokens?: number
+    ): Promise<string> {
+        try {
+            // Import required configuration
+            const {
+                GOOGLE_CLOUD_PROJECT_ID,
+                GOOGLE_CLOUD_LOCATION,
+                GEMINI_MODEL,
+                DRY_RUN_SKIP_GEMINI
+            } = require('../config');
+
+            // If dry run is enabled, return a mock summary
+            if (DRY_RUN_SKIP_GEMINI) {
+                console.log(`[DRY RUN] Skipping Gemini API call for generating summary for ${workitem.name}`);
+                return `[DRY RUN] Mock summary for ${workitem.name}. Pull request: ${pullRequestUrl}`;
+            }
+
+            // Initialize the GeminiService directly
+            const geminiService = new GeminiService(
+                GOOGLE_CLOUD_PROJECT_ID,
+                GOOGLE_CLOUD_LOCATION,
+                GEMINI_MODEL,
+                DRY_RUN_SKIP_GEMINI
+            );
+
+            // Prepare the prompt for Gemini
+            const prompt = `
+    Please generate a concise summary of the changes made for this Jira ticket.
+
+    Jira Ticket: ${workitem.key}
+    Title: ${workitem.title}
+    Description: ${workitem.description}
+
+    Files modified:
+    ${filesWritten.map(file => `- ${file}`).join('\n')}
+
+    Pull Request: ${pullRequestUrl}
+
+    The summary should:
+    1. Be professional and concise (3-5 sentences)
+    2. Explain what was implemented
+    3. Mention the pull request link
+    4. Be suitable for posting as a comment on the Jira ticket
+    `;
+
+            // Generate the summary
+            const summary = await geminiService.generateText(prompt);
+
+            // Format the summary with the PR link and processing information
+            let formattedSummary = `
+    ${summary}
+
+    Pull Request: ${pullRequestUrl}
+    `;
+
+            // Add processing time and token consumption if available
+            if (processingTimeMs || totalTokens) {
+                formattedSummary += `\n    Processing Information:`;
+
+                if (processingTimeMs) {
+                    const processingTimeSec = (processingTimeMs / 1000).toFixed(2);
+                    formattedSummary += `\n    - Processing Time: ${processingTimeSec} seconds`;
+                }
+
+                if (totalTokens) {
+                    formattedSummary += `\n    - Total Tokens: ${totalTokens}`;
+                    if (inputTokens) {
+                        formattedSummary += ` (Input: ${inputTokens}, Output: ${outputTokens || 0})`;
+                    }
+                }
+            }
+
+            return formattedSummary;
+        } catch (error) {
+            console.error(`Error generating summary for workitem ${workitem.name}:`, error);
+            return `A pull request has been created for this issue: ${pullRequestUrl}`;
+        }
+    }
+}

src/functions/jira-to-test-spec/src/services/processor-service.ts

@@ -0,0 +1,367 @@
+/**
+ * Service for orchestrating the entire process
+ */
+import * as path from 'path';
+import * as os from 'os';
+import {ProcessResult, RepoCredentials} from '../types';
+import {
+    RepositoryService as SharedRepositoryService,
+    PullRequestService as SharedPullRequestService,
+    GeminiService, Project
+} from 'shared-functions';
+import {ProjectService} from './project-service';
+import {JiraWorkitemsService} from './jira-workitems-service';
+import {
+    DRY_RUN_SKIP_COMMITS,
+    getGiteaCredentials,
+    getGithubCredentials,
+    getJiraCredentials,
+    getMainRepoCredentials,
+    MAIN_REPO_URL,
+    USE_LOCAL_REPO,
+    validateConfig,
+    GOOGLE_CLOUD_PROJECT_ID,
+    GOOGLE_CLOUD_LOCATION,
+    GEMINI_MODEL,
+    DRY_RUN_SKIP_GEMINI,
+    DRY_RUN_SKIP_JIRA_STATUS_UPDATE,
+    JIRA_TO_TEST_SPEC_LABEL
+} from '../config';
+
+export class ProcessorService {
+    private sharedRepositoryService: SharedRepositoryService;
+    private projectService: ProjectService;
+    private sharedPullRequestService: SharedPullRequestService;
+    private geminiService: GeminiService;
+    private jiraWorkitemsService: JiraWorkitemsService;
+    private mainRepoUrl: string;
+    private mainRepoCredentials: RepoCredentials;
+    private giteaCredentials?: RepoCredentials;
+    private githubCredentials?: RepoCredentials;
+
+    constructor() {
+        // Validate configuration
+        validateConfig();
+
+        // Initialize services
+        const repoBaseDir = path.join(os.tmpdir(), 'jira-to-test-spec');
+        this.sharedRepositoryService = new SharedRepositoryService(repoBaseDir);
+        this.projectService = new ProjectService();
+        this.sharedPullRequestService = new SharedPullRequestService();
+        this.geminiService = new GeminiService(
+            GOOGLE_CLOUD_PROJECT_ID,
+            GOOGLE_CLOUD_LOCATION,
+            GEMINI_MODEL,
+            DRY_RUN_SKIP_GEMINI
+        );
+
+        // Initialize Jira workitems service
+        const jiraCredentials = getJiraCredentials();
+        this.jiraWorkitemsService = new JiraWorkitemsService(jiraCredentials);
+
+        // Get main repository URL and credentials only if not using local repo
+        if (!USE_LOCAL_REPO) {
+            this.mainRepoUrl = MAIN_REPO_URL;
+            this.mainRepoCredentials = getMainRepoCredentials();
+        } else {
+            // Set dummy values when using local repo
+            this.mainRepoUrl = '';
+            this.mainRepoCredentials = getMainRepoCredentials();
+        }
+
+        // Initialize other credentials
+        this.githubCredentials = getGithubCredentials();
+        this.giteaCredentials = getGiteaCredentials();
+    }
+
+    /**
+     * Get credentials for a project based on its repository host
+     * @param project Project information
+     * @returns Credentials for the project repository
+     */
+    private getCredentialsForProject(project: Project): RepoCredentials {
+        if (!project.repoHost) {
+            throw new Error(`Repository host not found for project ${project.name}`);
+        }
+
+        if (project.repoHost.includes('github.com')) {
+            if (!this.githubCredentials) {
+                throw new Error('GitHub credentials not found');
+            }
+            return this.githubCredentials;
+        } else if (project.repoHost.includes('gitea')) {
+            if (!this.giteaCredentials) {
+                throw new Error('Gitea credentials not found');
+            }
+            return this.giteaCredentials;
+        } else {
+            throw new Error(`Unsupported repository host: ${project.repoHost}`);
+        }
+    }
+
+    /**
+     * Process all projects in the main repository
+     * @returns Array of process results
+     */
+    async processProjects(): Promise<ProcessResult[]> {
+        const results: ProcessResult[] = [];
+        let mainRepoPath: string;
+
+        try {
+            // Use local repository or clone the main repository
+            if (USE_LOCAL_REPO) {
+                console.log('Using local repository path');
+                // When running with functions-framework, we need to navigate up to the project root
+                // Check if we're in the jira-to-test-spec directory and navigate up if needed
+                const currentDir = process.cwd();
+                if (currentDir.endsWith('jira-to-test-spec')) {
+                    mainRepoPath = path.resolve(currentDir, '../../..');
+                } else {
+                    mainRepoPath = currentDir;
+                }
+                console.log(`Resolved local repository path: ${mainRepoPath}`);
+            } else {
+                console.log(`Cloning main repository: ${this.mainRepoUrl}`);
+                mainRepoPath = await this.sharedRepositoryService.cloneMainRepository(
+                    this.mainRepoUrl,
+                    this.mainRepoCredentials
+                );
+            }
+
+            // Find all projects in the prompts directory
+            const promptsDir = path.join(mainRepoPath, 'src', 'prompts');
+            console.log(`Finding projects in: ${promptsDir}`);
+            const projects = await this.projectService.findProjects(promptsDir);
+
+            console.log(`Found ${projects.length} projects`);
+
+            // Log details of each project
+            if (projects.length > 0) {
+                console.log('Projects found:');
+                projects.forEach((project, index) => {
+                    console.log(`  ${index + 1}. ${project.name} (${project.path})`);
+                });
+            } else {
+                console.log('No projects found. Check if the prompts directory exists and contains project folders.');
+            }
+
+            // Process each project
+            console.log('Starting to process projects...');
+            for (const project of projects) {
+                try {
+                    console.log(`Starting processing of project: ${project.name}`);
+                    const result = await this.processProject(project, mainRepoPath);
+                    console.log(`Finished processing project: ${project.name}`);
+                    results.push(result);
+                } catch (error) {
+                    console.error(`Error processing project ${project.name}:`, error);
+                    results.push({
+                        project,
+                        processedWorkitems: [],
+                        error: error instanceof Error ? error.message : String(error)
+                    });
+                }
+            }
+            console.log(`Finished processing all ${projects.length} projects`);
+
+            return results;
+        } catch (error) {
+            console.error('Error processing projects:', error);
+            throw error;
+        }
+    }
+
+    /**
+     * Process a single project
+     * @param project Project information
+     * @param mainRepoPath Path to the main repository
+     * @returns Process result
+     */
+    async processProject(project: Project, mainRepoPath: string): Promise<ProcessResult> {
+        console.log(`Processing project: ${project.name}`);
+
+        // Skip if no repository URL
+        if (!project.repoUrl) {
+            console.log(`Skipping project ${project.name}: No repository URL found`);
+            return {
+                project,
+                processedWorkitems: []
+            };
+        }
+
+        try {
+            // Get credentials for the project
+            const credentials = this.getCredentialsForProject(project);
+
+            // Clone the project repository
+            console.log(`Cloning project repository: ${project.repoUrl}`);
+            const projectRepoPath = await this.sharedRepositoryService.cloneProjectRepository(project, credentials);
+
+            // Find workitems within the project using the Jira workitems service
+            console.log(`Finding workitems within project: ${project.name}`);
+            const workitems = await this.jiraWorkitemsService.findWorkitems(project);
+
+            // If no workitems were found, return early
+            if (workitems.length === 0) {
+                console.log(`No workitems found for project ${project.name}`);
+                return {
+                    project,
+                    processedWorkitems: []
+                };
+            }
+
+            // Skip creating commits/PRs if dry run is enabled
+            if (DRY_RUN_SKIP_COMMITS) {
+                console.log(`[DRY RUN] Skipping commit and PR creation for project ${project.name}`);
+                return {
+                    project,
+                    processedWorkitems: [],
+                    pullRequestUrl: 'https://example.com/mock-pr-url (DRY RUN)'
+                };
+            }
+
+            // Read project guidelines
+            const projectGuidelines = await this.projectService.readProjectGuidelines(project.path);
+
+            // Collect all relevant files from the project directory
+            const relevantFiles = await this.projectService.collectRelevantFiles(project, projectRepoPath);
+
+            // Process each workitem independently
+            const processedWorkitems = [];
+            for (const workitem of workitems) {
+                try {
+                    console.log(`Processing workitem: ${workitem.name}`);
+
+                    // Process workitem with Gemini
+                    const processedWorkitem = await this.jiraWorkitemsService.processWorkitem(
+                        project,
+                        projectRepoPath,
+                        workitem,
+                        projectGuidelines,
+                        relevantFiles
+                    );
+
+                    // Skip workitems with no files written
+                    if (!processedWorkitem.filesWritten || processedWorkitem.filesWritten.length === 0) {
+                        console.log(`Skipping workitem ${processedWorkitem.workitem.name}: No files written`);
+                        processedWorkitems.push(processedWorkitem);
+                        continue;
+                    }
+
+                    // Create a new branch for this workitem
+                    // Extract function name from the title (first word or up to first colon)
+                    const functionName = 'jira-to-test-spec'
+                    const workitemBranchName = `${processedWorkitem.workitem.key.toLowerCase()}-${functionName}-${new Date().toISOString().split('T')[0]}`;
+                    await this.sharedRepositoryService.createBranch(projectRepoPath, workitemBranchName);
+
+                    // Commit changes for this workitem
+                    await this.sharedRepositoryService.commitChanges(
+                        projectRepoPath,
+                        `Update workitem ${processedWorkitem.workitem.key}: ${processedWorkitem.workitem.title}`
+                    );
+
+                    // Push changes
+                    await this.sharedRepositoryService.pushChanges(projectRepoPath, workitemBranchName, credentials);
+
+                    // Generate git patch for this workitem
+                    let workitemGitPatch: string | undefined = undefined;
+                    try {
+                        console.log(`Generating git patch for workitem ${processedWorkitem.workitem.key}`);
+                        workitemGitPatch = await this.sharedRepositoryService.generateGitPatch(projectRepoPath);
+                    } catch (error) {
+                        console.error(`Error generating git patch for workitem ${processedWorkitem.workitem.key}:`, error);
+                    }
+
+                    // Generate PR description using Gemini
+                    const workItemSummary = `${processedWorkitem.workitem.key}: ${processedWorkitem.filesWritten?.length ?? 0} written, ${processedWorkitem.filesRemoved?.length ?? 0} removed`;
+                    let description = await this.geminiService.generatePullRequestDescription(
+                        workItemSummary,
+                        workitemGitPatch
+                    );
+
+                    // Add Jira ticket link to the description
+                    const jiraTicketUrl = `${this.jiraWorkitemsService.getJiraBaseUrl()}/browse/${processedWorkitem.workitem.key}`;
+                    description = `${description}\n\nJira Ticket: [${processedWorkitem.workitem.key}](${jiraTicketUrl})`;
+                    description = `${description}\n${processedWorkitem.totalTokens} tokens consumed in ${(processedWorkitem.processingTimeMs ?? 0) / 1000} s`;
+
+                    // Generate PR title
+                    // Extract function name and create a short description from the title
+                    const shortDescription = processedWorkitem.workitem.title;
+                    const title = `${processedWorkitem.workitem.key}: ${functionName} - ${shortDescription}`;
+
+                    // Create pull request
+                    const pullRequestUrl = await this.sharedPullRequestService.createPullRequest(
+                        project,
+                        workitemBranchName,
+                        credentials,
+                        title,
+                        description
+                    );
+                    console.log(`Created pull request for workitem ${processedWorkitem.workitem.key}: ${pullRequestUrl}`);
+
+                    // Update the workitem with the pull request URL
+                    const updatedWorkitem = {
+                        ...processedWorkitem,
+                        pullRequestUrl
+                    };
+
+                    // Skip updating Jira status if the flag is enabled
+                    if (!DRY_RUN_SKIP_JIRA_STATUS_UPDATE) {
+                        // Update Jira issue status to Review
+                        await this.jiraWorkitemsService.updateJiraIssueStatusToReview(processedWorkitem.workitem.key);
+
+                        // Remove the jira-to-test-spec label
+                        await this.jiraWorkitemsService.removeJiraIssueLabel(processedWorkitem.workitem.key, JIRA_TO_TEST_SPEC_LABEL);
+
+                        // Generate a summary for the workitem
+                        const summary = await this.jiraWorkitemsService.generateWorkitemSummary(
+                            processedWorkitem.workitem,
+                            pullRequestUrl,
+                            processedWorkitem.filesWritten || [],
+                            processedWorkitem.processingTimeMs,
+                            processedWorkitem.inputTokens,
+                            processedWorkitem.outputTokens,
+                            processedWorkitem.totalTokens
+                        );
+
+                        // Add a comment to the Jira issue with the PR link and summary
+                        await this.jiraWorkitemsService.addCommentToJiraIssue(
+                            processedWorkitem.workitem.key,
+                            summary
+                        );
+                    } else {
+                        console.log(`[DRY RUN] Skipping Jira status update for workitem ${processedWorkitem.workitem.key}`);
+                    }
+
+                    // Reset repository to main branch after PR creation
+                    const mainBranch = project.targetBranch || 'main';
+                    console.log(`Resetting repository to clean state on branch ${mainBranch}`);
+                    await this.sharedRepositoryService.hardResetToCleanBranch(projectRepoPath, mainBranch);
+
+                    processedWorkitems.push(updatedWorkitem);
+                } catch (error) {
+                    console.error(`Error processing workitem ${workitem.name}:`, error);
+                    processedWorkitems.push({
+                        workitem,
+                        success: false,
+                        error: error instanceof Error ? error.message : String(error)
+                    });
+                }
+            }
+
+            return {
+                project,
+                processedWorkitems
+            };
+
+
+        } catch (error) {
+            console.error(`Error processing project ${project.name}:`, error);
+            return {
+                project,
+                processedWorkitems: [],
+                error: error instanceof Error ? error.message : String(error)
+            };
+        }
+    }
+}

src/functions/jira-to-test-spec/src/services/project-service.ts

@@ -0,0 +1,48 @@
+/**
+ * Service for handling project operations
+ */
+import * as fs from 'fs';
+import * as path from 'path';
+import {Project, ProjectService as SharedProjectService} from 'shared-functions';
+import {Workitem} from '../types';
+import {GeminiResponse} from "shared-functions/dist/services/gemini-file-system-service";
+
+export class ProjectService {
+    private sharedProjectService: SharedProjectService;
+
+    constructor() {
+        this.sharedProjectService = new SharedProjectService();
+    }
+
+    /**
+     * Find all projects in the prompts directory
+     * @param promptsDir Path to the prompts directory
+     * @returns Array of projects
+     */
+    async findProjects(promptsDir: string): Promise<Project[]> {
+        return this.sharedProjectService.findProjects(promptsDir, 'jira-to-test-spec');
+    }
+
+    async collectRelevantFiles(project: Project, projectRepoPath: string): Promise<Record<string, string>> {
+        return this.sharedProjectService.collectRelevantFiles(project, projectRepoPath);
+    }
+
+    /**
+     * Read project information from INFO.md
+     * @param projectPath Path to the project directory
+     * @param projectName Name of the project
+     * @returns Project information
+     */
+    async readProjectInfo(projectPath: string, projectName: string): Promise<Project> {
+        return this.sharedProjectService.readProjectInfo(projectPath, projectName);
+    }
+
+    /**
+     * Read AI guidelines for a project
+     * @param projectPath Path to the project directory
+     * @returns AI guidelines content
+     */
+    async readProjectGuidelines(projectPath: string): Promise<string> {
+        return this.sharedProjectService.readProjectGuidelines(projectPath);
+    }
+}

src/functions/jira-to-test-spec/src/types.ts

@@ -0,0 +1,93 @@
+/**
+ * Type definitions for the jira-to-test-spec function
+ */
+
+import {Project} from "shared-functions";
+
+/**
+ * Status of a workitem implementation
+ */
+export type WorkitemImplementationStatus = 'create' | 'update' | 'delete';
+
+export interface Workitem {
+    name: string;
+    path?: string; // Path is optional for Jira workitems
+    title: string;
+    description: string;
+    jiraReference: string; // Required for Jira workitems
+    implementation?: string;
+    pullRequestUrl?: string;
+    isActive: boolean;
+    key: string; // Jira issue key
+}
+
+export interface JiraIssue {
+    id: string;
+    key: string;
+    fields: {
+        summary: string;
+        description: string;
+        status: {
+            name: string;
+        };
+        [key: string]: any;
+    };
+}
+
+export interface RepoCredentials {
+    type: 'username-password' | 'token';
+    username?: string;
+    password?: string;
+    token?: string;
+}
+
+export interface JiraCredentials {
+    username: string;
+    apiToken: string;
+    baseUrl: string;
+}
+
+export interface ProcessedWorkItem {
+    workitem: Workitem;
+    success: boolean;
+    error?: string;
+    filesWritten?: string[];
+    filesRemoved?: string[];
+    processingTimeMs?: number;
+    inputTokens?: number;
+    outputTokens?: number;
+    totalTokens?: number;
+}
+
+export interface ProcessResult {
+    project: Project;
+    processedWorkitems: ProcessedWorkItem[];
+    pullRequestUrl?: string;
+    error?: string;
+}
+
+/**
+ * HTTP response format for the API
+ */
+export interface HttpResponse {
+    success: boolean;
+    projectsProcessed: number;
+    projectsSucceeded: number;
+    projectsFailed: number;
+    mainPullRequestUrl?: string;
+    projects: ProjectSummary[];
+    error?: string;
+}
+
+/**
+ * Summary of a project's processing results
+ */
+export interface ProjectSummary {
+    name: string;
+    success: boolean;
+    error?: string;
+    workitemsProcessed: number;
+    filesWritten: number;
+    pullRequestUrl?: string;
+    gitPatch?: string;
+}

src/functions/jira-to-test-spec/tsconfig.json

@@ -0,0 +1,18 @@
+{
+  "compilerOptions": {
+    "target": "ES2020",
+    "module": "CommonJS",
+    "outDir": "dist",
+    "strict": true,
+    "esModuleInterop": true,
+    "forceConsistentCasingInFileNames": true,
+    "skipLibCheck": true
+  },
+  "include": [
+    "src/**/*"
+  ],
+  "exclude": [
+    "node_modules",
+    "dist"
+  ]
+}

src/functions/prompts-to-test-spec/src/services/project-service.ts

@@ -65,10 +65,10 @@ export class ProjectService {
 
         // Parse workitem content
         const titleMatch = content.match(/## (.*)/);
-        const jiraMatch = content.match(/- \[[ x]\] Jira: (.*)/);
-        const implementationMatch = content.match(/- \[[ x]\] Implementation: (.*)/);
-        const pullRequestUrlMatch = content.match(/- \[[ x]\] Pull Request: (.*)/);
-        const activeMatch = content.match(/- \[([x ])\] Active/);
+        const jiraMatch = content.match(/- \[[x]\] Jira: (.*)/);
+        const implementationMatch = content.match(/- \[[x]\] Implementation: (.*)/);
+        const pullRequestUrlMatch = content.match(/- \[[x]\] Pull Request: (.*)/);
+        const activeMatch = content.match(/- \[([x])\] Active/);
 
         // Extract description (everything between title and first metadata line)
         let description = '';
@@ -90,7 +90,7 @@ export class ProjectService {
 
         // Determine if workitem is active
         // If the Active checkbox is missing, assume it's active
-        const isActive = activeMatch ? activeMatch[1] === 'x' : true;
+        const isActive = activeMatch ? activeMatch[1] === 'x' : false;
 
         return {
             name: fileName.replace('.md', ''),

src/functions/prompts-to-test-spec/src/services/project-workitems-service.ts

@@ -201,7 +201,6 @@ export class ProjectWorkitemsService {
             + `WORK ITEM METADATA:\n`
             + `Name: ${workItem.name}\n`
             + `Title: ${workItem.title}\n`
-            + `Path: ${workItem.path}\n`
             + `Jira refs: ${workItem.jiraReference}\n`
             + `Active: ${workItem.isActive}\n`
             + `--- START OF WORK ITEM CONTENT\n`

src/functions/shared/src/services/__tests__/gemini-file-system-service.test.ts

@@ -132,4 +132,213 @@ describe('GeminiFileSystemService', () => {
       expect(fs.readFileSync).not.toHaveBeenCalled();
     });
   });
+
+  describe('grepFiles', () => {
+    beforeEach(() => {
+      // Mock fs.readdirSync to return a list of files and directories
+      (fs.readdirSync as jest.Mock).mockImplementation((dirPath) => {
+        if (dirPath === 'root') {
+          return [
+            { name: 'src', isDirectory: () => true, isFile: () => false },
+            { name: 'file1.txt', isDirectory: () => false, isFile: () => true }
+          ];
+        } else if (dirPath === 'root/src') {
+          return [
+            { name: 'nested', isDirectory: () => true, isFile: () => false },
+            { name: 'file2.ts', isDirectory: () => false, isFile: () => true }
+          ];
+        } else if (dirPath === 'root/src/nested') {
+          return [
+            { name: 'file3.js', isDirectory: () => false, isFile: () => true }
+          ];
+        }
+        return [];
+      });
+
+      // Mock fs.readFileSync to return content with the search string
+      (fs.readFileSync as jest.Mock).mockImplementation((filePath) => {
+        if (filePath === 'root/file1.txt') {
+          return 'This is file1 with documentRule in it';
+        } else if (filePath === 'root/src/file2.ts') {
+          return 'File2 content\ndocumentRule: test\nMore content';
+        } else if (filePath === 'root/src/nested/file3.js') {
+          return 'File3 content without the term';
+        }
+        return '';
+      });
+
+      // Mock path.resolve to return the same path (for canonicalPath)
+      (path.resolve as jest.Mock).mockImplementation((p) => p);
+
+      // Mock path.relative to return relative paths
+      (path.relative as jest.Mock).mockImplementation((base, full) => {
+        return full.replace(`${base}/`, '');
+      });
+    });
+
+    it('should find matches in files with the search string', () => {
+      const results = geminiFileSystemService.grepFiles('root', 'documentRule');
+
+      expect(results.length).toBeGreaterThan(0);
+      expect(results.some(r => r.file === 'file1.txt')).toBe(true);
+      expect(results.some(r => r.file === 'src/file2.ts')).toBe(true);
+      expect(results.some(r => r.content.includes('documentRule'))).toBe(true);
+    });
+
+    it('should handle the problematic "**/*" pattern efficiently', () => {
+      const results = geminiFileSystemService.grepFiles('root', 'documentRule', '**/*');
+
+      expect(results.length).toBeGreaterThan(0);
+      // Verify we found matches in both root and nested directories
+      expect(results.some(r => r.file === 'file1.txt')).toBe(true);
+      expect(results.some(r => r.file === 'src/file2.ts')).toBe(true);
+
+      // Verify we didn't process files without matches unnecessarily
+      // This is hard to test directly, but we can check that the function returns
+      // and doesn't hang or consume excessive resources
+    });
+
+    it('should respect the maxResults limit', () => {
+      // Create a mock that returns many matches
+      (fs.readFileSync as jest.Mock).mockImplementation(() => {
+        return 'documentRule\ndocumentRule\ndocumentRule\ndocumentRule\n'.repeat(200);
+      });
+
+      const results = geminiFileSystemService.grepFiles('root', 'documentRule');
+
+      // The maxResults is set to 500 in the implementation
+      expect(results.length).toBeLessThanOrEqual(500);
+    });
+
+    it('should throw an error if search string is not provided', () => {
+      expect(() => {
+        geminiFileSystemService.grepFiles('root', '');
+      }).toThrow('Search string is required');
+    });
+  });
+
+  describe('listFiles', () => {
+    beforeEach(() => {
+      // Mock fs.existsSync to return true for directories
+      (fs.existsSync as jest.Mock).mockReturnValue(true);
+
+      // Mock fs.readdirSync to return a list of files and directories
+      (fs.readdirSync as jest.Mock).mockImplementation((dirPath) => {
+        if (dirPath === 'root/src') {
+          return [
+            { name: 'nested', isDirectory: () => true, isFile: () => false },
+            { name: 'file1.ts', isDirectory: () => false, isFile: () => true },
+            { name: 'file2.js', isDirectory: () => false, isFile: () => true }
+          ];
+        } else if (dirPath === 'root/src/nested') {
+          return [
+            { name: 'deep', isDirectory: () => true, isFile: () => false },
+            { name: 'file3.ts', isDirectory: () => false, isFile: () => true }
+          ];
+        } else if (dirPath === 'root/src/nested/deep') {
+          return [
+            { name: 'file4.js', isDirectory: () => false, isFile: () => true }
+          ];
+        } else if (dirPath === 'root/node_modules') {
+          return [
+            { name: 'package', isDirectory: () => true, isFile: () => false }
+          ];
+        } else if (dirPath === 'root/node_modules/package') {
+          return [
+            { name: 'file.js', isDirectory: () => false, isFile: () => true }
+          ];
+        }
+        return [];
+      });
+
+      // Mock path.resolve to return the same path (for canonicalPath)
+      (path.resolve as jest.Mock).mockImplementation((p) => p);
+
+      // Mock path.relative to return relative paths
+      (path.relative as jest.Mock).mockImplementation((base, full) => {
+        return full.replace(`${base}/`, '');
+      });
+    });
+
+    it('should list files in a directory', () => {
+      const results = geminiFileSystemService.listFiles('root', 'src');
+
+      expect(results.length).toBe(2);
+      expect(results).toContain('file1.ts');
+      expect(results).toContain('file2.js');
+    });
+
+    it('should list files matching a pattern', () => {
+      const results = geminiFileSystemService.listFiles('root', 'src', '*.ts');
+
+      expect(results.length).toBe(1);
+      expect(results).toContain('file1.ts');
+      expect(results).not.toContain('file2.js');
+    });
+
+    it('should recursively list files with "**" pattern', () => {
+      const results = geminiFileSystemService.listFiles('root', 'src', '**/*.ts');
+
+      expect(results.length).toBe(2);
+      expect(results).toContain('file1.ts');
+      expect(results).toContain('nested/file3.ts');
+      expect(results).not.toContain('file2.js');
+      expect(results).not.toContain('nested/deep/file4.js');
+    });
+
+    it('should handle the problematic "**/*" pattern efficiently', () => {
+      const results = geminiFileSystemService.listFiles('root', 'src', '**/*');
+
+      expect(results.length).toBeGreaterThan(0);
+      // Verify we found files in both root and nested directories
+      expect(results).toContain('file1.ts');
+      expect(results).toContain('file2.js');
+      expect(results).toContain('nested/file3.ts');
+      expect(results).toContain('nested/deep/file4.js');
+    });
+
+    it('should skip node_modules directory', () => {
+      // Set up a mock that includes node_modules
+      (fs.readdirSync as jest.Mock).mockImplementation((dirPath) => {
+        if (dirPath === 'root') {
+          return [
+            { name: 'src', isDirectory: () => true, isFile: () => false },
+            { name: 'node_modules', isDirectory: () => true, isFile: () => false }
+          ];
+        }
+        // Return the same mocks as before for other paths
+        return [];
+      });
+
+      const results = geminiFileSystemService.listFiles('root', '', '**/*');
+
+      // Verify node_modules was skipped
+      expect(results.every(path => !path.includes('node_modules'))).toBe(true);
+    });
+
+    it('should respect the maxResults limit', () => {
+      // Create a mock that returns many files
+      (fs.readdirSync as jest.Mock).mockImplementation(() => {
+        const files = [];
+        for (let i = 0; i < 2000; i++) {
+          files.push({ name: `file${i}.ts`, isDirectory: () => false, isFile: () => true });
+        }
+        return files;
+      });
+
+      const results = geminiFileSystemService.listFiles('root', 'src');
+
+      // The maxResults is set to 1000 in the implementation
+      expect(results.length).toBeLessThanOrEqual(1000);
+    });
+
+    it('should throw an error if directory does not exist', () => {
+      // Mock fs.existsSync to return false
+      (fs.existsSync as jest.Mock).mockReturnValue(false);
+
+      expect(() => {
+        geminiFileSystemService.listFiles('root', 'nonexistent');
+      }).toThrow('Directory not found: nonexistent');
+    });
+  });
 });

src/functions/shared/src/services/__tests__/project-service.test.ts

@@ -98,6 +98,8 @@ describe('ProjectService', () => {
 - [x] Target branch: main
 - [x] AI guidelines: docs/AI_GUIDELINES.md
 - [x] Jira component: project-component
+- [x] Jira labels: label1,label2,label3
+- [x] Jira project: PROJECT
 - [x] Write paths: src/*, test/*
 - [x] Read paths: docs/*, config/*
 `;
@@ -118,6 +120,8 @@ describe('ProjectService', () => {
         targetBranch: 'main',
         aiGuidelines: ['docs/AI_GUIDELINES.md'],
         jiraComponent: 'project-component',
+        jiraLabels: ['label1', 'label2', 'label3'],
+        jiraProject: 'PROJECT',
         remoteDataUris: [],
         writePaths: ['src/*', 'test/*'],
         readPaths: ['docs/*', 'config/*']
@@ -148,6 +152,8 @@ Some other content that doesn't match the expected format.
         targetBranch: undefined,
         aiGuidelines: undefined,
         jiraComponent: undefined,
+        jiraLabels: undefined,
+        jiraProject: undefined,
         remoteDataUris: [],
         writePaths: undefined,
         readPaths: undefined

src/functions/shared/src/services/gemini-file-system-service.ts

@@ -335,20 +335,52 @@ export class GeminiFileSystemService {
         }
 
         const results: string[] = [];
+        const maxResults = 1000; // Limit the number of results to prevent excessive processing
+
+        // Track visited directories to prevent infinite recursion
+        const visitedDirs = new Set<string>();
 
         // Helper function to recursively list files in a directory
-        const listFilesInDirectory = (currentPath: string, basePath: string) => {
+        const listFilesInDirectory = (currentPath: string, basePath: string, depth: number = 0) => {
+            // Prevent excessive recursion
+            if (depth > 50 || results.length >= maxResults) {
+                return;
+            }
+
+            // Prevent revisiting the same directory (can happen with symlinks)
+            const canonicalPath = path.resolve(currentPath);
+            if (visitedDirs.has(canonicalPath)) {
+                return;
+            }
+            visitedDirs.add(canonicalPath);
+
             try {
                 const entries = fs.readdirSync(currentPath, {withFileTypes: true});
 
                 for (const entry of entries) {
+                    if (results.length >= maxResults) {
+                        return;
+                    }
+
                     const entryPath = path.join(currentPath, entry.name);
                     const relativePath = path.relative(basePath, entryPath);
 
                     if (entry.isDirectory()) {
-                        // If pattern includes ** (recursive glob), recurse into subdirectories
-                        if (pattern && pattern.includes('**')) {
-                            listFilesInDirectory(entryPath, basePath);
+                        // Skip node_modules and .git directories
+                        if (entry.name !== 'node_modules' && entry.name !== '.git') {
+                            // If pattern includes ** (recursive glob), recurse into subdirectories
+                            if (pattern && pattern.includes('**')) {
+                                // For "**/*" pattern, we need to be more selective to avoid excessive recursion
+                                if (pattern === "**/*") {
+                                    // For this common pattern that causes high CPU usage, be more selective
+                                    // Only recurse if we haven't found enough results yet
+                                    if (results.length < maxResults / 2) {
+                                        listFilesInDirectory(entryPath, basePath, depth + 1);
+                                    }
+                                } else {
+                                    listFilesInDirectory(entryPath, basePath, depth + 1);
+                                }
+                            }
                         }
                     } else if (entry.isFile()) {
                         // Check if the file matches the pattern
@@ -390,20 +422,24 @@ export class GeminiFileSystemService {
         const results: Array<{ file: string, line: number, content: string }> = [];
         const maxResults = 500;
 
+        // Prepare search regex once (outside the file processing loop)
+        const inFilePattern = searchString.replace(/\*/g, '.*'); // Convert * to .*
+        const searchRegex = new RegExp(`.*${inFilePattern}.*`);
+
+        // Track visited directories to prevent infinite recursion
+        const visitedDirs = new Set<string>();
+
         // Helper function to search in a file
         const searchInFile = (filePath: string, relativePath: string) => {
             try {
                 const content = fs.readFileSync(filePath, 'utf-8');
                 const lines = content.split('\n');
 
-                const pattern = searchString.replace(/\*/g, '.*'); // Convert * to .*
-                const regex = new RegExp(`.*${pattern}.*`);
-
                 for (let i = 0; i < lines.length; i++) {
-                    if (results.length > maxResults) {
+                    if (results.length >= maxResults) {
                         return;
                     }
-                    if (regex.test(lines[i])) {
+                    if (searchRegex.test(lines[i])) {
                         results.push({
                             file: relativePath,
                             line: i + 1, // 1-based line numbers
@@ -417,12 +453,24 @@ export class GeminiFileSystemService {
         };
 
         // Helper function to recursively search in a directory
-        const searchInDirectory = (dirPath: string, baseDir: string) => {
+        const searchInDirectory = (dirPath: string, baseDir: string, depth: number = 0) => {
+            // Prevent excessive recursion
+            if (depth > 50 || results.length >= maxResults) {
+                return;
+            }
+
+            // Prevent revisiting the same directory (can happen with symlinks)
+            const canonicalPath = path.resolve(dirPath);
+            if (visitedDirs.has(canonicalPath)) {
+                return;
+            }
+            visitedDirs.add(canonicalPath);
+
             try {
                 const entries = fs.readdirSync(dirPath, {withFileTypes: true});
 
                 for (const entry of entries) {
-                    if (results.length > maxResults) {
+                    if (results.length >= maxResults) {
                         return;
                     }
 
@@ -432,8 +480,18 @@ export class GeminiFileSystemService {
                     if (entry.isDirectory()) {
                         // Skip node_modules and .git directories
                         if (entry.name !== 'node_modules' && entry.name !== '.git') {
+                            // Only recurse if pattern requires it
                             if (!pattern || pattern.includes('**')) {
-                                searchInDirectory(fullPath, baseDir);
+                                // For "**/*" pattern, we need to be more selective to avoid excessive recursion
+                                if (pattern === "**/*") {
+                                    // For this common pattern that causes high CPU usage, be more selective
+                                    // Only recurse if we haven't found enough results yet
+                                    if (results.length < maxResults / 2) {
+                                        searchInDirectory(fullPath, baseDir, depth + 1);
+                                    }
+                                } else {
+                                    searchInDirectory(fullPath, baseDir, depth + 1);
+                                }
                             }
                         }
                     } else if (entry.isFile()) {

src/functions/shared/src/services/gemini-service.ts

@@ -73,9 +73,6 @@ ${description}
 *Note: This is a mock PR description generated during dry run. No actual Gemini API call was made.*`;
         }
 
-        const generativeModel = this.vertexAI.preview.getGenerativeModel({
-            model: this.model,
-        });
 
         // Prepare the git patch section if available
         let gitPatchSection = '';
@@ -104,7 +101,13 @@ Keeps the description concise but informative
 
 The pull request description should be ready to use without further editing.
 `;
+        return await this.generateText(prompt);
+    }
 
+    async generateText(prompt: string) {
+        const generativeModel = this.vertexAI.preview.getGenerativeModel({
+            model: this.model,
+        });
         const result = await generativeModel.generateContent({
             contents: [
                 {

src/functions/shared/src/services/project-service.ts

@@ -120,6 +120,8 @@ export class ProjectService {
         const repoUrlMatch = infoContent.match(/- \[[x]\] Repo url: (.*)/);
         const targetBranchMatch = infoContent.match(/- \[[x]\] Target branch: (.*)/);
         const jiraComponentMatch = infoContent.match(/- \[[x]\] Jira component: (.*)/);
+        const jiraLabelsMatch = infoContent.match(/- \[[x]\] Jira labels: (.*)/);
+        const jiraProjectMatch = infoContent.match(/- \[[x]\] Jira project: (.*)/);
         const aiGuidelinesMatch = infoContent.match(/- \[[x]\] AI guidelines: (.*)/);
         const remoteDataMatch = infoContent.match(/- \[[x]\] Remote data: (.*)/);
         const writePathsMatch = infoContent.match(/- \[[x]\] Write paths: (.*)/);
@@ -128,6 +130,7 @@ export class ProjectService {
         const remoteUris = remoteDataMatch ? remoteDataMatch[1].trim().split(',') : [];
         const writePaths = writePathsMatch ? writePathsMatch[1].trim().split(',').map(path => path.trim()) : undefined;
         const readPaths = readPathsMatch ? readPathsMatch[1].trim().split(',').map(path => path.trim()) : undefined;
+        const jiraLabels = jiraLabelsMatch ? jiraLabelsMatch[1].trim().split(',').map(label => label.trim()) : undefined;
 
         const project: Project = {
             name: projectName,
@@ -136,6 +139,8 @@ export class ProjectService {
             repoUrl: repoUrlMatch ? repoUrlMatch[1].trim() : undefined,
             targetBranch: targetBranchMatch ? targetBranchMatch[1].trim() : undefined,
             jiraComponent: jiraComponentMatch ? jiraComponentMatch[1].trim() : undefined,
+            jiraProject: jiraProjectMatch ? jiraProjectMatch[1].trim() : undefined,
+            jiraLabels: jiraLabels,
             aiGuidelines: aiGuidelinesMatch ? aiGuidelinesMatch[1].trim().split(',') : undefined,
             remoteDataUris: remoteUris,
             writePaths: writePaths,

src/functions/shared/src/services/repository-service.ts

@@ -157,6 +157,33 @@ export class RepositoryService {
         }
     }
 
+    /**
+     * Hard reset repository to a specific branch and clean untracked files
+     * @param repoDir Path to the repository
+     * @param branchName Name of the branch to reset to (usually 'main' or 'master')
+     * @throws Error if reset fails
+     */
+    async hardResetToCleanBranch(repoDir: string, branchName: string): Promise<void> {
+        const git = simpleGit(repoDir);
+        try {
+            // Checkout the specified branch
+            await git.checkout(branchName);
+
+            // Fetch latest changes
+            await git.fetch('origin', branchName);
+
+            // Hard reset to the remote branch
+            await git.reset(['--hard', `origin/${branchName}`]);
+
+            // Clean untracked files and directories
+            await git.clean('fd');
+
+            console.log(`Repository reset to clean state on branch ${branchName}`);
+        } catch (error) {
+            throw new Error(`Failed to reset repository to branch ${branchName}: ${error instanceof Error ? error.message : String(error)}`);
+        }
+    }
+
     /**
      * Configure git with credentials
      * @param repoDir Path to the repository

src/functions/shared/src/types.ts

@@ -8,6 +8,8 @@ export interface Project {
     repoHost?: string;
     repoUrl?: string;
     jiraComponent?: string;
+    jiraProject?: string;
+    jiraLabels?: string[];
     targetBranch?: string;
     aiGuidelines?: string[];
     remoteDataUris?: string[];

src/prompts/jira-to-test-spec/AI.md

@@ -0,0 +1,73 @@
+This file describes the AI guidelines for operations in this directory.
+
+## Directory structure
+
+- <project>/: A single project repository
+    - INFO.md: Project information, including where the code is hosted
+    - AI.md: AI guidelines for the project
+
+### File format
+
+File format is markdown.
+It contains checkboxes, that must only be checked if the information is available and provided.
+
+#### Project info file format
+
+A project info file follows the following format:
+
+```markdown
+## <Project name>
+
+- [ ] Repo host: <repo host url, eg https://gitea.fteamdev.valuya.be/ or https://github.com/organizations/Ebitda-SRL>
+- [ ] Repo url: <url of the project repository>
+- [ ] Target branch: <target branch for the PR>
+- [ ] AI guidelines: <path to ai guidelines md file in the project repo>
+- [ ] Remote data: <url to remote data to include in prompt>
+- [ ] Jira component: <component of the project in jira>
+- [ ] Jira labels: <labels of the tickets in jira, comma-separated>
+- [ ] Jira project: <JIRA project name>
+- [ ] Write paths: <comma-separated list of path filters (globs) to which the agent can write>
+- [ ] Read paths: <comma-separated list of path filters (globs) from which the agent can read>
+
+```
+
+#### Work item prompt file format
+
+A work item prompt file follows the following format:
+
+```markdown
+## <workitem name>
+
+<short paragraphs describing the workitem, with line wrapping>
+
+- [ ] Jira: <reference of the jira ticket with a link>
+- [ ] Implementation: <reference of the implementation within the project repo, optionally with a link>
+- [ ] Active
+
+### Log
+
+<log to be filled as the workitem is processed, implementation logs will be automatically added to this section>
+
+```
+
+The active checkbox is optional and should be checked if the workitem is active. Inactive workitems should be ignored.
+In the absence of the active checkbox, the workitem is assumed to be active.
+
+### Credentials
+
+This section describes credentials to use when interacting with various apis and services.
+
+The actual credentials are provided in the environment variables.
+
+#### Jira
+
+#### Github
+
+- [ ] host: https://github.com/organizations/Ebitda-SRL
+
+#### Gitea
+
+- [x] host: https://gitea.fteamdev.valuya.be
+    - credential type: username/password
+    - username variable: GITEA_USERNAME
+    - password variable: GITEA_PASSWORD

src/prompts/jira-to-test-spec/nitro-back/AI.md

@@ -0,0 +1,64 @@
+## Workitem implementation
+
+Your task is to understand the business requirements of the work item, with respect to the existing codebase,
+and rephrase them as test specifications in the cucumber format.
+
+The requirements of the work item itself must NOT be implemented at this stage.
+
+- Work items for which the cucumber file already exists should be checked
+    - If the feature file appears consistent with the work item, it can be skipped and your task is done.
+    - If the feature file appears uncomplete, it can be updated
+        - Avoid updating scenarios that are still consistent with the work item.
+        - Prefer adding new scenarios for features omitted in the current feature file.
+- Updates which required filesystem changes should be committed before completing the task.
+  If no changes was required, commit should be skipped. 
+  The commit must contain AT MOST a single file: the .feature file.
+
+IMPORTANT: 
+- Start by understanding the work item business requirements with respect to the existing codebase.
+    - Use the filesystem functions at your disposal to navigate the codebase.
+    - Identify the resources involved and whether they exist or not in the codebase
+    - Investigate the involved resources for their lifecycle existing business logic implemented in the codebase.
+    - Identify how the requirements of the work item will impact the existing codebase
+- Then, identify test cases that could be used to guarantee proper implementation of the business requirements.
+    - Test the happy flow, but also test the error cases.
+- Then, describe the test specs complying with the work item as a cucumber feature spec file in the
+  `nitro-it/src/test/resources/workitems/` folder.
+    - Use the workitem prompt file name as the feature file name.
+    - Add comments in the feature file indicating
+        - The date/time/execution info of the job that created the work item
+        - The work item prompt file in this directory
+        - The jira ticket number, and a link to the jira ticket if applicable.
+  
+- DO NOT modify the codebase: If some API models, or endpoints are missing, do NOT add them.
+- DO NOT use ids, pseudo-identifiers, assumed values etc. Instead, inspect the codebase to
+  understand the lifecycle of the resources.
+    - DO NOT use 'Given a document exists with id XXX', but DO USE 'Given a document is uploaded'
+    - DO NOT use 'Given a customer exists with id XXX', but USE 'Given a customer is created'
+- Use business requirements. Try to write test cases focusing on high-level expectations. Write more specific test
+  specs if it appears warranted (specifics of the work item, sensitive or complex logic involved, etc.)
+    - DO NOT use 'Given this resource has status XXX, Then', but prefer 'Given this resource has been created, And that
+      operation A has been performed on it, And that operation B has been performed on it, Then'
+
+- This project contains the following modules:
+    - nitro-domain: contains the jpa domain entities
+    - nitro-domain-api: contains the api model, controller interfaces, and the openapi specification. The api resource
+      names are prefixed with "Ws"
+    - nitro-it: contains the integration tests
+    - nitro-core-services: contains the core services implementations
+    - nitro-domain-rest and nitro-domain-ws-utils: contains the api implementation
+
+- This project deals with state machines for documents, transactions, statements, field requests.
+    - "CustomerDocument" and "CustomerTransaction" are the main resources, each composed in part of an AccountingData.
+    - The hierarchy of tenancy has two levels: Trustee and Customer
+    - Explore DocumentStatus, DocumentTransition enums to grasp the document state machine
+    - Explore TestDocumentSortingService, TestDocumentIndexingService for utilities for sorting and indexing documents
+      during tests
+    - Explore TransactionStatus enum, TransactionStatusUpdateSingleton to grasp the transaction state machine
+    - Explore FieldIdentificationRequestStatus enum, FieldIdentificationValueStatus enum,
+      FieldIdentificationRequestStatusUpdateSingleton to grasp the field request state machine
+    - Explore FinancialAccountStatementStatus enum to grasp the financial account statement state machine
+
+- Inspect the existing business resources using the available filesystem functions
+    - look in nitro-domain for the domain entities
+    - look in nitro-core-services for the business services

src/prompts/jira-to-test-spec/nitro-back/INFO.md

@@ -0,0 +1,12 @@
+# Nitro-back
+
+Nitro backend server in quarkus
+
+- [x] Repo host: https://gitea.fteamdev.valuya.be/
+- [x] Repo url: https://gitea.fteamdev.valuya.be/cghislai/nitro-back.git
+- [x] Target branch: main
+- [ ] AI guidelines: nitro-it/src/test/resources/workitems/AI_DEFINITION.md
+- [x] Jira component: nitro
+- [x] Jira labels: backenders
+- [x] Jira project: NITRO
+- [x] Write paths: nitro-it/src/test/resources/workitems/**

src/prompts/jira-to-test-spec/prompts-to-test-spec.md

@@ -0,0 +1,3 @@
+This function creates test specs from jira tickets.
+
+

src/prompts/prompts-to-test-spec/nitro-back/AI.md

@@ -11,16 +11,18 @@ The requirements of the work item itself must NOT be implemented at this stage.
         - Avoid updating scenarios that are still consistent with the work item.
         - Prefer adding new scenarios for features omitted in the current feature file.
 - Inactive work items should have their feature file deleted.
+- Updates which required filesystem changes should be committed before completing the task.
+  If no changes was required, commit should be skipped. 
+  The commit must contain AT MOST a single file: the .feature file.
 
-IMPORTANT: Start by understanding the work item business requirements with respect to the existing codebase.
-    - IMPORTANT: Use the filesystem functions at your disposal to navigate the codebase.
+IMPORTANT: 
+- Start by understanding the work item business requirements with respect to the existing codebase.
+    - Use the filesystem functions at your disposal to navigate the codebase.
     - Identify the resources involved and whether they exist or not in the codebase
     - Investigate the involved resources for their lifecycle existing business logic implemented in the codebase.
     - Identify how the requirements of the work item will impact the existing codebase
-
 - Then, identify test cases that could be used to guarantee proper implementation of the business requirements.
     - Test the happy flow, but also test the error cases.
-
 - Then, describe the test specs complying with the work item as a cucumber feature spec file in the
   `nitro-it/src/test/resources/workitems/` folder.
     - Use the workitem prompt file name as the feature file name.
@@ -28,21 +30,16 @@ IMPORTANT: Start by understanding the work item business requirements with respe
         - The date/time/execution info of the job that created the work item
         - The work item prompt file in this directory
         - The jira ticket number, and a link to the jira ticket if applicable.
-    - Do NOT implement the requirements. If the work item mention missing endpoint, or asks to implement something,
-      do not implement it - just write test spec that tests their implementation (test-driven development).
-    - Do NOT modify the codebase: If some API models, or endpoints are missing, do NOT add them.
-    - Use business requirements. Try to write test cases focusing on high-level expectations. Write more specific test
-      specs if it appears warranted (specifics of the work item, sensitive or complex logic involved, etc.)
-        - Dont use 'Given this resource has status XXX', but prefer 'Given this resource has been created, And that
-          operation has been performed on it, And that other operation has been performed on it', etc.
-    - The test will be run against a real instance of the application by performing real http requests causing
-      real updates to the database. Dont use pseudo-identifiers, assumed values etc. Instead, inspect the codebase to
-      understand the lifecycle of the resources and use assertions for managing those resources in the .feature file.
-        - Dont use 'Given a document exists with id 453', but use 'Given a document is uploaded'
-    - Dont make assumptions—be explicit about what matters, but omit what does not matter
   
-- Updates which required filesystem changes should be committed before completing the work item. If no changes was
-  required, commit should be skipped. The commit must contain AT MOST a single file: the .feature file.
+- DO NOT modify the codebase: If some API models, or endpoints are missing, do NOT add them.
+- DO NOT use ids, pseudo-identifiers, assumed values etc. Instead, inspect the codebase to
+  understand the lifecycle of the resources.
+    - DO NOT use 'Given a document exists with id XXX', but DO USE 'Given a document is uploaded'
+    - DO NOT use 'Given a customer exists with id XXX', but USE 'Given a customer is created'
+- Use business requirements. Try to write test cases focusing on high-level expectations. Write more specific test
+  specs if it appears warranted (specifics of the work item, sensitive or complex logic involved, etc.)
+    - DO NOT use 'Given this resource has status XXX, Then', but prefer 'Given this resource has been created, And that
+      operation A has been performed on it, And that operation B has been performed on it, Then'
 
 - This project contains the following modules:
     - nitro-domain: contains the jpa domain entities

src/prompts/prompts-to-test-spec/nitro-back/workitems/2025-06-08-document-archvigin.md

@@ -13,270 +13,51 @@ Only users that are superAdmins may archive documents.
 
 - [ ] Jira: NITRO-0003
 - [ ] Implementation:
-- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/77
-- [x] Active
+- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/87
+- [ ] Active
 
 ### Log
 
-2025-06-09T17:36:52.736Z - Gemini updates
+2025-06-09T18:44:11.608Z - Gemini updates
+- started: Starting the work item implementation for document archiving. The work item is inactive, so I will check for and delete the corresponding feature file.
+- started: Checking for the existence of the feature file for the inactive work item.
+- started: Feature file found. Deleting the feature file as the work item is inactive.
+- done: Feature file deleted successfully.
+- started: Committing the deletion of the feature file.
+-  Delete file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/81
+
+
+2025-06-09T18:18:18.917Z - Gemini updates
+- started: Starting the process of managing the document archiving feature file based on the work item status.
+- started: Checking if the feature file for the inactive work item exists.
+- done: The work item is inactive, so the existing feature file needs to be deleted.
+- started: Deleting the feature file for the inactive work item.
+- done: Successfully deleted the feature file for the inactive work item.
+-  Delete file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/80
+
+
+2025-06-09T18:09:25.002Z - Gemini updates
+- started: Starting the process of handling the document archiving work item. The work item is inactive, so I will check for and delete the corresponding feature file.
+- started: Checking for the existence of the feature file for the inactive work item.
+- started: The work item is inactive, and a feature file for it exists. Deleting the feature file.
+- started: Feature file deleted. Committing the changes.
+- done: Feature file deleted and changes committed.
+- done: Successfully handled the inactive work item by deleting its feature file and committing the changes.
+-  Delete file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/79
+
+
+2025-06-09T18:07:06.863Z - Gemini updates
+- started: Understand Work Item Business Requirements and Codebase Exploration
+-  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/79
+
+
+2025-06-09T17:55:47.816Z - Gemini updates
 - started: Understand Work Item and Existing Codebase
-- started: List files in nitro-it/src/test/resources/workitems/ to check for existing feature file.
-- done: Existing feature file found. Reading its content.
-- started: Read the content of the existing feature file.
-- partially-done: The existing feature file is incomplete. It does not cover the rule that an ARCHIVED document cannot be COMPLETED afterwards. I will update the feature file to include this scenario.
-- started: Adding a new scenario to the feature file to cover the 'cannot be COMPLETED after ARCHIVED' rule.
-- done: Added a new scenario to the feature file to cover the 'cannot be COMPLETED after ARCHIVED' rule.
-- started: Commit the updated feature file.
-- done: Committed the updated feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-
-
-2025-06-09T17:26:12.606Z - Gemini updates
-- started: Starting to understand the work item and explore the codebase.
-- partially-done: Investigating CustomerDocumentStatus and its relation to archiving. Found ARCHIVED status and ARCHIVABLE_STATUSES list, which currently excludes TO_EXPORT, contradicting the work item. Need to find usages of ARCHIVABLE_STATUSES and existing archiving logic/endpoints.
-- started: Searching for usages of ARCHIVABLE_STATUSES to understand its impact.
-- partially-done: Found definition of ARCHIVABLE_STATUSES but no direct usages in Java files. This suggests it might be used indirectly or in other file types. Now searching for the 'dedicated endpoint' for archiving documents.
-- started: Searching for document archiving endpoints or related services in nitro-domain-api and nitro-domain-rest.
-- partially-done: Identified the current archiving endpoints. Now verifying the finality of ARCHIVED status and checking for transitions from ARCHIVED to COMPLETED. Also, need to investigate the handling of TO_EXPORT status during archiving and superAdmin checks.
-- started: Checking for transitions from ARCHIVED to COMPLETED in CustomerDocumentStatus and related transition logic.
-- partially-done: Identified the current archiving endpoints and their implementation. Now verifying the finality of ARCHIVED status and checking for transitions from ARCHIVED to COMPLETED. Also, need to investigate the handling of TO_EXPORT status during archiving and superAdmin checks.
-- started: Checking CustomerDocumentTransition for ARCHIVING transition details, specifically allowed initial states and possible target states.
-- partially-done: Understood the work item requirements and identified discrepancies with the current codebase regarding archiving from TO_EXPORT status. Formulating test specifications in Cucumber format.
-- started: Creating the Cucumber feature file for document archiving.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archiving.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/75
-
-
-2025-06-09T17:23:25.103Z - Gemini updates
-- started: Starting the work item by checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/75
-
-
-2025-06-09T17:16:51.495Z - Gemini updates
-- started: Starting the work item by checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
-
-
-2025-06-09T17:12:01.683Z - Gemini updates
-- started: Starting the work item by checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
-
-
-2025-06-09T17:05:04.707Z - Gemini updates
-- started: Starting the work item by checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/72
-
-
-2025-06-09T17:00:04.473Z - Gemini updates
-- started: Checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/71
-
-
-2025-06-09T16:53:02.580Z - Gemini updates
-- started: Checking for the existence of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:40:50.316Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:35:16.349Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:09:34.469Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:05:42.369Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:04:09.015Z - Gemini updates
-- started: Starting the work item by checking for the existence and content of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:58:18.462Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:50:39.335Z - Gemini updates
-- started: Verifying the existence and content of the feature file for document archiving.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:42:56.792Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: Feature file already exists. Checking its content.
-- started: Reading content of existing feature file.
-- done: Content of the feature file reviewed. It covers most of the requirements, but a scenario for preventing completion after archiving is missing. Also, comments need to be updated.
-- started: Updating comments in the feature file and adding a new scenario.
-- done: Comments in the feature file have been updated and a new scenario has been added.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:41:31.130Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: Feature file already exists. Checking its content.
-- started: Reading content of existing feature file.
-- done: Content of the feature file reviewed. It covers all the requirements.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:30:39.611Z - Gemini updates
-- started: Checking if the feature file for document archiving already exists.
-- done: The feature file already exists. Now, checking its content to ensure it covers all the requirements.
-- started: Reading the content of the feature file.
-- done: Content of the feature file reviewed. It covers all the requirements.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:28:34.070Z - Gemini updates
-- started: Verifying the existence and content of the feature file for document archiving.
-- done: The feature file already exists and its content covers all the requirements. Now, updating the comments in the feature file.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:23:52.364Z - Gemini updates
-- started: Verifying the existence and content of the feature file for document archiving.
-- done: The feature file already exists and its content covers all the requirements. Now, updating the comments in the feature file.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:21:44.468Z - Gemini updates
-- started: Verifying the existence and content of the feature file for document archiving.
-- done: The feature file already exists and its content covers all the requirements. Now, updating the comments in the feature file.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
-- done: The updated feature file has been committed.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:10:54.018Z - Gemini updates
-- started: Checking for existing feature file for document archiving.
-- done: Feature file already exists. Checking its content.
-- started: Reading content of existing feature file.
-- done: Content of the feature file reviewed. It covers all the requirements.
-- started: No changes required for the feature file as it already covers all requirements. Committing to confirm completion.
-- started: Starting to update comments in the feature file.
-- started: Updating comments in the feature file.
-- done: Comments in the feature file have been updated.
-- started: Committing the updated feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- started: Check for existing feature file for '2025-06-08-document-archvigin'
+- done: Existing feature file found. Checking consistency with work item.
+- started: Read content of existing feature file.
+- done: Existing feature file content read. Identifying missing scenarios.
+- started: Identify test cases and update feature file.
+- started: Add scenario for archiving a document and then attempting to complete it.
+- done: Added scenario for archiving a document and then attempting to complete it.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-08-document-archvigin.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/78

src/prompts/prompts-to-test-spec/nitro-back/workitems/2025-06-08-test.md

@@ -6,221 +6,16 @@ The nitro-back backend should have a /test endpoint implemented returning the js
 
 - [ ] Jira: NITRO-0001
 - [ ] Implementation:
-- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/77
-- [x] Active
+- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/87
+- [ ] Active
 
 ### Log
 
-2025-06-09T17:38:02.676Z - Gemini updates
-- started: Understanding the work item and existing codebase. Identifying relevant modules and how endpoints are defined.
-- started: The work item requires adding a new endpoint `/test` to the `nitro-back` backend. This endpoint should return the JSON object `{"test": "Hellow"}`. I need to find where the existing controllers are defined to understand how to add a new one.
-- started: Broadening the search for controller definitions to `nitro-core-services` and `nitro-domain-api` and looking for `@RequestMapping` or similar annotations.
-- done: The project uses JAX-RS for defining REST endpoints, indicated by the presence of `@Path` annotations. I need to create a new JAX-RS resource class in `nitro-domain-rest` to implement the `/test` endpoint.
-- started: Creating the Cucumber feature file for the new /test endpoint.
-- done: The Cucumber feature file has been created. Committing the changes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-
-
-2025-06-09T17:34:22.165Z - Gemini updates
-- started: Starting to understand the work item and check for existing feature file.
-- started: Feature file does not exist. Creating a new feature file for the work item.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-
-
-2025-06-09T17:26:56.910Z - Gemini updates
-- started: Understanding the work item and existing codebase by searching for "test" endpoint related code.
-- started: Checking for existing feature file for work item '2025-06-08-test'.
-- started: Creating new feature file for work item '2025-06-08-test'.
-- started: Committing the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/75
-
-
-2025-06-09T17:18:14.625Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The feature file is now compliant with the guidelines regarding comments.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/72
-
-
-2025-06-09T17:13:35.663Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The feature file is now compliant with the guidelines regarding comments.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/72
-
-
-2025-06-09T17:01:16.147Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/71
-
-
-2025-06-09T16:53:46.819Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:41:56.328Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- done: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T16:06:48.994Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:59:27.031Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:52:22.760Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
-- started: Reading the existing feature file content to update placeholders.
-- done: Successfully read the existing feature file content.
-- started: Updating the content of the Cucumber feature file with actual date/time and Jira link.
-- done: Successfully updated the content of the Cucumber feature file with actual date/time and Jira link.
-- started: Committing the updated Cucumber feature file.
-- done: Successfully committed the updated Cucumber feature file.
-- started: Re-evaluating compliance with guidelines. Identified that the date/time and Jira link in the feature file comments are placeholders and need to be updated.
-- done: The date/time and Jira link in the feature file comments are placeholders and need to be updated. This requires reading the file, updating its content, and writing it back.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:43:40.950Z - Gemini updates
-- started: Checking for the existence of the feature file for the work item.
-- done: The feature file does not exist. Creating the content for the Cucumber feature file.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:31:20.059Z - Gemini updates
-- started: Starting to create the Cucumber feature file for the work item.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- done: Completed creation and commit of the Cucumber feature file for the work item.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:29:14.706Z - Gemini updates
-- started: Starting to create the Cucumber feature file for the work item.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- done: Completed creation and commit of the Cucumber feature file for the work item.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:24:41.963Z - Gemini updates
-- started: Starting to create the Cucumber feature file for the work item.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- done: Completed creation and commit of the Cucumber feature file for the work item.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
-
-2025-06-09T15:11:33.033Z - Gemini updates
-- started: Starting to create the Cucumber feature file for the work item.
-- started: Creating the content for the Cucumber feature file.
-- done: Successfully created the content for the Cucumber feature file and wrote it to the specified path.
-- started: Committing the newly created Cucumber feature file.
-- done: Successfully committed the new Cucumber feature file.
-- done: Completed creation and commit of the Cucumber feature file for the work item.
--  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
+2025-06-09T18:07:51.509Z - Gemini updates
+- started: Check for existing feature file for work item "2025-06-08-test".
+- done: Feature file does not exist. Creating a new feature file for the work item.
+- started: Create the content for the new feature file.
+- done: Feature file created. Committing the changes.
+- started: Commit the new feature file.
+- done: New feature file committed successfully.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-08-test.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/79

src/prompts/prompts-to-test-spec/nitro-back/workitems/2025-06-09-NITRO-2957.md

@@ -9,138 +9,221 @@ Later when the 3 configuration case will be displayed too in the table -  (Fulls
 
 ---
 
-This ticket asks to
+This ticket asks to:
 
-- split the WsCustomerDocument model into different models with different permissions:
-    - The actual WsCustomerDocument should contain information accessible by the customer itself
-    - A new WsCustomerDocumentAdminConfiguration should contain information accessible by nitro admins
-    - Later, WsCustomerDocumentTrusteeConfiguration could contain information accessible by trustees
-- WsCustomerDocumentAdminConfiguration could contain
-    - amount of validation required - already existing
-    - type of configuration - or configuration template (fullspeed, partialspeed, nospeed)
+- split the WsCustomerDocument and WsCustomerTransaction models into different models with different permissions:
+    - The current models should contain information accessible by the customer itself
+    - New *AdminConfiguration should contain information accessible by nitro admins
+    - Later, *TrusteeConfiguration could contain information accessible by trustees
+- The WsAccountingData model could be migrated to either WsCustomerDocument or WsCustomerTransaction, if needed
+- *AdminConfiguration could contain
+    - the amount of validation required - a field already existing
+    - type of configuration - or configuration template (fullspeed, partialspeed, nospeed).
+      A field not yet existing.
 
 ---
 
 - [x] Jira:NITRO-2957 https://fiscalteam.atlassian.net/browse/NITRO-2957
 - [ ] Implementation:
-- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/77
-- [x] Active
-
+- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/87
+- [ ] Active
 
 ### Log
 
+2025-06-09T20:47:33.014Z - Gemini updates
+- started: Starting to process work item NITRO-2957. Checking if the feature file needs to be deleted.
+-  Delete file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/82
+
+
+2025-06-09T18:46:17.976Z - Gemini updates
+- started: Understand the work item business requirements with respect to the existing codebase.
+- started: Identify relevant models: WsCustomerDocument, WsCustomerTransaction, WsAccountingData in nitro-domain-api.
+- done: Identify relevant models: WsCustomerDocument, WsCustomerTransaction, WsAccountingData in nitro-domain-api.
+- started: Examine WsCustomerDocument.java, WsCustomerTransaction.java, and WsAccountingData.java.
+- done: Examine WsCustomerDocument.java, WsCustomerTransaction.java, and WsAccountingData.java.
+- started: Identify fields for splitting and new fields for admin configuration.
+- done: Identify fields for splitting and new fields for admin configuration.
+- started: Check if the feature file '2025-06-09-NITRO-2957.feature' already exists.
+- started: Feature file does not exist. Creating a new feature file for NITRO-2957.
+- done: Feature file created successfully.
+- started: Commit the new feature file.
+- done: New feature file committed successfully.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/80
+
+
+2025-06-09T18:11:04.125Z - Gemini updates
+- started: Understand the work item and existing codebase by locating relevant model definitions and permissions.
+- done: Identified existing models and the need for new admin-specific models. Outlined high-level test cases for customer and admin access, and new fields.
+- started: Create the Cucumber feature file for NITRO-2957.
+- done: Created the Cucumber feature file for NITRO-2957 with scenarios for customer and admin access to document and transaction configurations, including validation and configuration type fields.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/79
+
+
+2025-06-09T17:57:29.728Z - Gemini updates
+- started: Understanding the work item business requirements with respect to the existing codebase. This involves identifying relevant files, investigating existing business logic, and understanding the impact of the requirements.
+- started: Listing files in nitro-domain-api to locate WsCustomerDocument, WsCustomerTransaction, and WsAccountingData models.
+- started: Examining the content of WsCustomerDocument.java, WsCustomerTransaction.java, and WsAccountingData.java to understand their structure and identify fields that might need to be split or moved.
+- started: The WsAccountingData class contains several fields that could be considered configuration-related, such as `configured`, `glAccountActionWsRef`, `vatCodeActionWsRef`, and `thirdPartyOverrideActionWsRef`. The work item explicitly mentions that WsAccountingData could be migrated to either WsCustomerDocument or WsCustomerTransaction. However, the current task is to define test specifications, not to implement the changes. Given this, the `adminComment` from WsCustomerDocument clearly belongs in an AdminConfiguration model. The `configured`, `glAccountActionWsRef`, `vatCodeActionWsRef`, and `thirdPartyOverrideActionWsRef` fields from WsAccountingData also seem to fit the AdminConfiguration model, as they are likely set by admins to control accounting behavior. The `amount of validation required` is mentioned as an existing field, and `type of configuration (fullspeed, partialspeed, nospeed)` as a new one. My next step is to identify where 'amount of validation required' might exist. I'll search for 'validation' in the nitro-domain-api directory.
+- done: Finished investigating existing code for 'validation' and related fields. It seems 'validation' is a broad concept rather than a specific field for 'amount of validation required'. I will proceed with creating the feature file, representing 'amount of validation required' and 'type of configuration' conceptually within the new AdminConfiguration model.
+- started: Defining test specifications in Cucumber format. Creating a new feature file for the work item.
+- done: The feature file has been created. Now committing the changes.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/78
+
+
+2025-06-09T17:46:59.153Z - Gemini updates
+
+- started: Understanding the work item and exploring the existing codebase for WsCustomerDocument and related
+  configurations.
+- started: Searching for WsCustomerDocument in nitro-domain-api to understand its current structure.
+- started: Examining WsCustomerDocument.java for existing configuration fields.
+- started: Defining test specifications for WsCustomerDocumentAdminConfiguration in a Cucumber feature file.
+- started: Committing the new Cucumber feature file.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/77
+
 2025-06-09T17:39:25.149Z - Gemini updates
+
 - started: Understand the Work Item and Existing Codebase
 - started: Search for WsCustomerDocument in the codebase to understand its current definition and usage.
-- done: WsCustomerDocument is a central API model used across various services. The work item requires splitting it into customer-facing and admin-facing models, with new configuration types for admins. Need to identify existing 'validation' fields.
+- done: WsCustomerDocument is a central API model used across various services. The work item requires splitting it into
+  customer-facing and admin-facing models, with new configuration types for admins. Need to identify existing '
+  validation' fields.
 - started: Search for 'validation' related fields in WsCustomerDocument.java and related files.
-- partially-done: No direct 'validation' field found in WsCustomerDocument.java or WsCustomerDocumentController.java. Need to investigate how validation is handled, possibly through status or transitions.
+- partially-done: No direct 'validation' field found in WsCustomerDocument.java or WsCustomerDocumentController.java.
+  Need to investigate how validation is handled, possibly through status or transitions.
 - started: Search for 'status' and 'transition' related to WsCustomerDocument to understand validation flow.
-- partially-done: WsCustomerDocumentStatus enum exists. No direct WsCustomerDocumentTransition found. Transitions are likely handled by methods in WsCustomerDocumentController that change the status. Need to examine WsCustomerDocumentController for methods related to status changes, especially validation.
-- started: Examine WsCustomerDocumentController for methods that change document status, particularly those related to validation or approval.
-- done: WsCustomerDocumentController has methods for validation transitions, and WsCustomerDocumentStatus defines TO_VALIDATE and VALIDATED states. This confirms validation is a document lifecycle state. The work item requires moving 'amount of validation required' to a new WsCustomerDocumentAdminConfiguration and adding 'type of configuration' (fullspeed, partialspeed, nospeed).
-- started: Search for existing configuration related to document validation or processing speed in `nitro-core-services` and `nitro-domain` to understand how 'amount of validation required' is currently handled.
-- done: Identified that 'amount of validation required' is likely handled at the Customer level (Customer.java) and influences AccountingDataValidation. The 'type of configuration' (fullspeed, partialspeed, nospeed) are new concepts. Proceeding to define test scenarios and create the Cucumber feature file.
+- partially-done: WsCustomerDocumentStatus enum exists. No direct WsCustomerDocumentTransition found. Transitions are
+  likely handled by methods in WsCustomerDocumentController that change the status. Need to examine
+  WsCustomerDocumentController for methods related to status changes, especially validation.
+- started: Examine WsCustomerDocumentController for methods that change document status, particularly those related to
+  validation or approval.
+- done: WsCustomerDocumentController has methods for validation transitions, and WsCustomerDocumentStatus defines
+  TO_VALIDATE and VALIDATED states. This confirms validation is a document lifecycle state. The work item requires
+  moving 'amount of validation required' to a new WsCustomerDocumentAdminConfiguration and adding 'type of
+  configuration' (fullspeed, partialspeed, nospeed).
+- started: Search for existing configuration related to document validation or processing speed in `nitro-core-services`
+  and `nitro-domain` to understand how 'amount of validation required' is currently handled.
+- done: Identified that 'amount of validation required' is likely handled at the Customer level (Customer.java) and
+  influences AccountingDataValidation. The 'type of configuration' (fullspeed, partialspeed, nospeed) are new concepts.
+  Proceeding to define test scenarios and create the Cucumber feature file.
 - started: Create the Cucumber feature file for NITRO-2957.
 - done: Cucumber feature file created successfully.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
 
 2025-06-09T17:35:27.845Z - Gemini updates
+
 - started: Understand existing WsCustomerDocument and identify fields for admin configuration.
 - done: The feature file for NITRO-2957 does not exist. Proceeding to create it.
 - started: Creating the Cucumber feature file for NITRO-2957.
 - done: Successfully created the Cucumber feature file for NITRO-2957.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
 
 2025-06-09T17:27:54.415Z - Gemini updates
+
 - started: Understanding the work item business requirements with respect to the existing codebase.
 - started: Investigating the existing codebase for WsCustomerDocument in nitro-domain-api.
 - started: Examining the WsCustomerDocument.java file to understand its current structure.
-- done: Finished examining WsCustomerDocument.java. Identified fields that should be moved to WsCustomerDocumentAdminConfiguration.
+- done: Finished examining WsCustomerDocument.java. Identified fields that should be moved to
+  WsCustomerDocumentAdminConfiguration.
 - started: Defining test specifications in Cucumber format for the work item.
 - started: Creating the Cucumber feature file for the work item.
 - done: Created the Cucumber feature file.
 - started: Committing the new feature file.
 - done: Committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/75
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/75
 
 2025-06-09T17:19:05.314Z - Gemini updates
-- started: Understanding work item requirements and exploring existing codebase for WsCustomerDocument and related configurations.
+
+- started: Understanding work item requirements and exploring existing codebase for WsCustomerDocument and related
+  configurations.
 - started: Searching for WsCustomerDocument in nitro-domain-api to understand its structure and existing fields.
 - started: Examining the content of WsCustomerDocument.java to identify fields for splitting.
-- done: Confirmed that no direct fields for 'amount of validation required' or 'fullspeed, partialspeed, nospeed' exist in WsCustomerDocument. These will be part of the new WsCustomerDocumentAdminConfiguration.
-- started: Searching for existing configuration types like 'fullspeed', 'partialspeed', 'nospeed' in the codebase to ensure no conflicts and to understand existing patterns.
-- done: Confirmed that 'fullspeed', 'partialspeed', and 'nospeed' configuration types do not exist in the current codebase, indicating they will be new additions.
+- done: Confirmed that no direct fields for 'amount of validation required' or 'fullspeed, partialspeed, nospeed' exist
+  in WsCustomerDocument. These will be part of the new WsCustomerDocumentAdminConfiguration.
+- started: Searching for existing configuration types like 'fullspeed', 'partialspeed', 'nospeed' in the codebase to
+  ensure no conflicts and to understand existing patterns.
+- done: Confirmed that 'fullspeed', 'partialspeed', and 'nospeed' configuration types do not exist in the current
+  codebase, indicating they will be new additions.
 - started: Checking if the feature file for NITRO-2957 already exists.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
 
 2025-06-09T17:14:53.101Z - Gemini updates
-- started: Understanding work item requirements and exploring existing codebase for WsCustomerDocument and related configurations.
+
+- started: Understanding work item requirements and exploring existing codebase for WsCustomerDocument and related
+  configurations.
 - started: Searching for WsCustomerDocument in nitro-domain-api to understand its structure and existing fields.
 - started: Examining the content of WsCustomerDocument.java to identify fields for splitting.
 - started: Searching for existing fields related to 'amount of validation required' in nitro-domain-api.
-- done: Confirmed that no direct fields for 'amount of validation required' or 'fullspeed, partialspeed, nospeed' exist in WsCustomerDocument. These will be part of the new WsCustomerDocumentAdminConfiguration.
-- started: Searching for existing configuration types like 'fullspeed', 'partialspeed', 'nospeed' in the codebase to ensure no conflicts and to understand existing patterns.
-- done: Confirmed that 'fullspeed', 'partialspeed', and 'nospeed' configuration types do not exist in the current codebase, indicating they will be new additions.
+- done: Confirmed that no direct fields for 'amount of validation required' or 'fullspeed, partialspeed, nospeed' exist
+  in WsCustomerDocument. These will be part of the new WsCustomerDocumentAdminConfiguration.
+- started: Searching for existing configuration types like 'fullspeed', 'partialspeed', 'nospeed' in the codebase to
+  ensure no conflicts and to understand existing patterns.
+- done: Confirmed that 'fullspeed', 'partialspeed', and 'nospeed' configuration types do not exist in the current
+  codebase, indicating they will be new additions.
 - started: Checking if the feature file for NITRO-2957 already exists.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
 
 2025-06-09T17:06:19.488Z - Gemini updates
+
 - started: Understanding work item requirements and checking for existing feature file.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/72
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/72
 
 2025-06-09T17:02:03.255Z - Gemini updates
+
 - started: Understanding the work item business requirements for NITRO-2957 and checking for existing feature file.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/71
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/71
 
 2025-06-09T16:54:36.584Z - Gemini updates
+
 - started: Understanding the work item business requirements for NITRO-2957 and checking for existing feature file.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T16:42:34.047Z - Gemini updates
+
 - started: Checking if the feature file for NITRO-2957 already exists.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T16:37:00.098Z - Gemini updates
+
 - started: Starting the process of creating/updating the Cucumber feature file for work item NITRO-2957.
 - started: Checking if the feature file for NITRO-2957 already exists.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
@@ -149,64 +232,74 @@ This ticket asks to
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
 - done: Successfully created the Cucumber feature file for work item NITRO-2957 and committed the changes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T16:10:43.257Z - Gemini updates
+
 - started: Checking if the feature file for NITRO-2957 already exists.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T16:05:11.991Z - Gemini updates
+
 - started: Checking for existing feature file for NITRO-2957.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T16:00:24.672Z - Gemini updates
+
 - started: Checking for existing feature file for NITRO-2957.
 - done: Feature file does not exist. Creating a new feature file for NITRO-2957.
 - started: Creating the content for the new feature file.
 - done: Successfully created the content for the new feature file.
 - started: Committing the new feature file.
 - done: Successfully committed the new feature file.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T15:52:53.173Z - Gemini updates
+
 - started: Starting the creation/update of the Cucumber feature file for work item NITRO-2957.
 - done: Successfully created the Cucumber feature file for work item NITRO-2957 and committed the changes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T15:42:43.995Z - Gemini updates
+
 - started: Starting the creation of the Cucumber feature file for work item NITRO-2957.
 - done: Successfully created the Cucumber feature file for work item NITRO-2957 and committed the changes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T15:31:57.853Z - Gemini updates
+
 - started: Starting the creation of the Cucumber feature file for work item NITRO-2957.
 - done: Successfully created the Cucumber feature file for work item NITRO-2957 and committed the changes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T15:25:12.853Z - Gemini updates
+
 - started: Starting the creation of the Cucumber feature file for work item NITRO-2957.
 - done: Successfully created the Cucumber feature file for work item NITRO-2957.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
-
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
 
 2025-06-09T15:23:14.067Z - Gemini updates
+
 - started: Starting the implementation of work item NITRO-2957 by creating a Cucumber feature file.
-- partially-done: Failed to commit files due to a git lock. Please resolve this manually if this is a real environment. Proceeding as if commit was successful for simulation purposes.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61
+- partially-done: Failed to commit files due to a git lock. Please resolve this manually if this is a real environment.
+  Proceeding as if commit was successful for simulation purposes.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2957.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/61

src/prompts/prompts-to-test-spec/nitro-back/workitems/2025-06-09-NITRO-2973.md

@@ -23,27 +23,141 @@ Buttons to apply a default config for document and/or transaction
 This ticket asks to add new endpoints to apply/clear a customer config template. One targeting document configuration,
 another targeting transaction configuration.
 
-Once a template has been applied, WsConfigValue with specific keys should have specific values at the customer level.
+When a template is applied, a set of fields and ConfigValue with specific keys should have specific values at the
+customer level.
+
+Once a template has been applied, user can still overwrite configurations values afterwards (no syncing).
+
+The list of config to apply for each template is:
+
+| **Flag/Config**            | **Value**           | **Behavior**                                                                                              | **fullspeed** (full doc, 12)                                | **partialspeed** (doc indexed/exported or to _bac à merde_, 60)       | **nospeed** (no doc exported, some from _codaox_, 500)                     |
+|----------------------------|---------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| **Validation (doc)**       | 0 or n              | if 0 the doc is validated automatically<br>if n the doc must be validated                                 | 1                                                           | 1                                                                         | 0                                                                              |
+| **Indexation active**      | true/false/null     |                                                                                                           | true                                                        | true                                                                      | false                                                                          |
+| **Configuration active**   | true/false/null     |                                                                                                           | true                                                        | false                                                                     | false                                                                          |
+| **Export vers horus**      | true/false/null     |                                                                                                           | true/false - default true                                   | true/false - default false                                                | false                                                                          |
+| **Export vers odoo**       | true/false/null     |                                                                                                           | true/false - default true                                   | true/false - default false                                                | false                                                                          |
+| **auto_export_enabled**    | true/false/null     |                                                                                                           | false<br>⚠️ auto_export_enabled is true when no export is activated | false<br>auto_export_enabled is true when no export is activated           | true<br>auto_export_enabled is true when no export is activated              |
+| **import horus library**   | true/false/null     |                                                                                                           | false                                                       | false                                                                     | false                                                                          |
+| **import horus document**  | true/false/null     |                                                                                                           | true                                                        | false                                                                     | false                                                                          |
+| **mailbox accepted**       | true/false          |                                                                                                           | true                                                        | true                                                                      | false                                                                          |
+| **mailbox forwarded**      | true/false          |                                                                                                           | false                                                       | false                                                                     | true/false                                                                     |
 
 ---
 
 - [x] Jira:NITRO-29723 https://fiscalteam.atlassian.net/browse/NITRO-2973
 - [ ] Implementation:
-- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
-- [x] Active
+- [x] Pull Request: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/87
+- [ ] Active
 
 ### Log
 
+2025-06-09T20:48:25.693Z - Gemini updates
+- started: Understand the work item and check for existing feature file.
+- started: Check if the feature file for NITRO-2973 exists.
+- done: The feature file for NITRO-2973 exists. Since the work item is inactive, delete the feature file.
+- started: Delete the feature file for the inactive work item.
+- done: Successfully deleted the feature file.
+- started: Commit the deletion of the feature file.
+- done: Committed the deletion of the feature file.
+- done: Work item is inactive, deleted the corresponding feature file and committed the changes.
+- started: Report final outcome and end the session.
+-  Delete file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/82
+
+
+2025-06-09T18:48:28.947Z - Gemini updates
+- started: Understand the work item business requirements and existing codebase.
+- started: Investigate existing configuration management in the codebase, specifically for 'ConfigValue' and customer-level configurations.
+- started: Investigate how `Metadata` relates to customers.
+- partially-done: Confirmed that ConfigValue can be owned by a Customer via Metadata and ConfigValueOwnerType. Now investigating services that manage ConfigValues.
+- started: Investigate services that manage ConfigValues in nitro-core-services.
+- partially-done: ConfigValueDao provides basic CRUD for ConfigValue. Need to find higher-level services that manage customer configurations.
+- partially-done: Identified MetadataConfigService as a key service for managing customer configurations. Now investigating MetadataConfigService and CustomerConfigKey.
+- started: Investigate MetadataConfigService and CustomerConfigKey.
+- done: Understood the core requirements: new endpoints for applying/clearing configuration templates for documents and transactions at the customer level. Identified `MetadataConfigService` and `CustomerConfigKey` as central to managing these configurations. Noted missing `CustomerConfigKey` entries for 'Validation (doc)', 'mailbox accepted', and 'mailbox forwarded', and the need for a 'last applied template' tag. Will proceed with creating test specifications assuming these keys will be available.
+- done: Understood the core requirements: new endpoints for applying/clearing configuration templates for documents and transactions at the customer level. Identified `MetadataConfigService` and `CustomerConfigKey` as central to managing these configurations. Noted missing `CustomerConfigKey` entries for 'Validation (doc)', 'mailbox accepted', and 'mailbox forwarded', and the need for a 'last applied template' tag. Will proceed with creating test specifications assuming these keys will be available.
+- started: Check for existing feature file for NITRO-2973.
+- done: Feature file does not exist. Proceeding to create a new feature file with test specifications.
+-  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/81
+
+
+2025-06-09T18:21:39.180Z - Gemini updates
+
+- started: Understand Work Item and Explore Codebase
+- partially-done: Feature file does not exist. Need to create it. Start by exploring existing configuration files.
+- started: Search for 'ConfigValue' in nitro-domain and nitro-core-services to understand existing configuration
+  handling.
+- done: Finished initial exploration of ConfigValue. Now, investigate existing CustomerConfigKey and related
+  document/transaction configuration keys.
+- started: Investigate CustomerConfigKey and related document/transaction configuration keys.
+- done: Finished investigating CustomerConfigKey. Ready to create the feature file.
+- started: Create the new feature file for NITRO-2973.
+- done: Feature file created successfully.
+- started: Commit the new feature file.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/80
+
+2025-06-09T18:12:33.111Z - Gemini updates
+
+- started: Understand Work Item and Explore Codebase
+- started: List files in nitro-domain-api to find API definitions.
+- done: List files in nitro-domain-api to find API definitions.
+- started: Examine WsCustomerDocumentController.java for existing API structure.
+- done: Examine WsCustomerDocumentController.java for existing API structure.
+- started: Examine WsCustomerTransactionController.java for existing API structure.
+- done: Examine WsCustomerTransactionController.java for existing API structure.
+- started: Identify relevant existing API endpoints and models for configuration.
+- done: Identify relevant existing API endpoints and models for configuration.
+- started: Examine WsCustomerConfigController.java for existing configuration API.
+- done: Examine WsCustomerConfigController.java for existing configuration API.
+- started: Define test cases in Cucumber format for document and transaction configuration templates.
+- done: Define test cases in Cucumber format for document and transaction configuration templates.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/79
+
+2025-06-09T17:59:32.204Z - Gemini updates
+
+- started: Understand the work item and plan codebase exploration.
+- started: Starting codebase exploration to identify existing API structure and relevant domain entities/services.
+- started: Investigating WsCustomerDocumentController.java for endpoint structure.
+- partially-done: WsCustomerDocumentController.java reviewed. It has customer-specific paths. Now checking
+  WsCustomerTransactionController.java.
+- partially-done: WsCustomerTransactionController.java reviewed. It also has customer-specific paths. Now checking
+  WsCustomerConfigController.java for configuration handling.
+- partially-done: WsCustomerConfigController.java reviewed. It handles specific config settings, not generic templates.
+  New endpoints likely needed under customer/document and customer/transaction. Checking WsCustomerController for
+  sub-resource patterns.
+- done: Codebase exploration complete. Identified relevant controllers and determined the likely structure for new
+  endpoints. Proceeding to create the Cucumber feature file.
+- started: Creating the Cucumber feature file for NITRO-2973.
+- done: Cucumber feature file created successfully.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/76
+
 2025-06-09T17:29:21.353Z - Gemini updates
+
 - started: Starting to understand the work item and explore the codebase to identify relevant files and existing logic.
 - started: Searching for WsConfigValue to understand its structure and usage.
 - done: WsConfigValue is a key entity. Now investigating how customer-level configurations are handled.
-- started: Investigating existing customer-specific configuration handling, focusing on CustomerConfigKey and CustomerClientUtils.
-- done: CustomerConfigKey is an enum used for customer-specific configurations. Existing usage in `TestAppContext.java` and `CustomerClientUtils.java` confirms its relevance. New 'speed' related config keys will likely be added here. Next, I will investigate existing API definitions for customer configurations.
-- started: Investigating existing API definitions for customer and configuration controllers in `nitro-domain-api` to understand endpoint structure.
-- started: Examining `WsCustomerConfigController.java` and `WsAppConfigurationController.java` for existing configuration endpoints.
-- done: WsCustomerConfigController handles specific document and statement PDF composition configurations. WsAppConfigurationController is more generic, dealing with WsConfigValue objects and providing search/create/delete operations for them. The new endpoints will likely be similar to the existing WsCustomerConfigController paths, but for document and transaction 'speed' configurations. I will assume the new endpoints will be added to WsCustomerDocumentController and WsCustomerTransactionController or a new controller. I will also assume that the 'speed' configurations will be represented by new CustomerConfigKey entries. Now, I will define the test cases in Cucumber format.
+- started: Investigating existing customer-specific configuration handling, focusing on CustomerConfigKey and
+  CustomerClientUtils.
+- done: CustomerConfigKey is an enum used for customer-specific configurations. Existing usage in `TestAppContext.java`
+  and `CustomerClientUtils.java` confirms its relevance. New 'speed' related config keys will likely be added here.
+  Next, I will investigate existing API definitions for customer configurations.
+- started: Investigating existing API definitions for customer and configuration controllers in `nitro-domain-api` to
+  understand endpoint structure.
+- started: Examining `WsCustomerConfigController.java` and `WsAppConfigurationController.java` for existing
+  configuration endpoints.
+- done: WsCustomerConfigController handles specific document and statement PDF composition configurations.
+  WsAppConfigurationController is more generic, dealing with WsConfigValue objects and providing search/create/delete
+  operations for them. The new endpoints will likely be similar to the existing WsCustomerConfigController paths, but
+  for document and transaction 'speed' configurations. I will assume the new endpoints will be added to
+  WsCustomerDocumentController and WsCustomerTransactionController or a new controller. I will also assume that the '
+  speed' configurations will be represented by new CustomerConfigKey entries. Now, I will define the test cases in
+  Cucumber format.
 - started: Defining test cases in Cucumber format for the new endpoints.
-- done: Defined test cases in Cucumber format and saved to `nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.feature`.
--  Added file nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
+- done: Defined test cases in Cucumber format and saved to
+  `nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.feature`.
+- Added file
+  nitro-it/src/test/resources/workitems/2025-06-09-NITRO-2973.featurePR: https://gitea.fteamdev.valuya.be/cghislai/nitro-back/pulls/73
 

src/prompts/test-spec-to-test-implementation/nitro-back/AI.md

@@ -1,15 +1,24 @@
-Implement tests according to the cucumber ".feature" files.
+## Tests implementation
+
+Your task is to implement the step definitions of cucumber .feature files; using the existing services available
+for integration tests in the codebase.
 
 - Iterate over cucumber ".feature" definition files in the `nitro-it/src/test/resources/workitems/` directory.
-- For each of them create all required files to implement the tests.
+- Check if they are implemented. When they do, skip to the next.
+
 - Use quarkus apis and best practices
 - All files and all their method must be correctly implemented, without any TODO or stub or placeholder.
 - The code produced must be ready for test driven development without any adaptation required.
-- The tests are business-driven integration tests
-- Implement services that perform actual http requests to the api.
 - IMPORTANT: Dont use mocks, stubs, fakes, placeholders, simulations, or any other technique to avoid complete
   implementations
 
+IMPORTANT:
+- Start by understanding the work item business requirements with respect to the existing codebase.
+  - Use the filesystem functions at your disposal to navigate the codebase.
+  - Identify the resources involved and whether they exist or not in the codebase
+  - Investigate the involved resources for their lifecycle existing business logic implemented in the codebase.
+  - Identify how the requirements of the work item will impact the existing codebase
+  
 - This project contains the following modules:
     - nitro-domain: contains the jpa domain entities
     - nitro-domain-api: contains the api model, controller interfaces, and the openapi specification. The api resource