qo
Qovery
GitHub
console
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
staging
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(agent-task): refine creation flow (#2961) ## Summary Refine the Agent Task creation experience and keep the created service consistent with what the user configured. - Send the CPU, memory, storage, and GPU values displayed in the creation flow to the API - Instruct Jira and Linear coding agents to check the current issue status and whether it was already processed before starting work - Replace the dedicated “Need a specific agent?” card with a compact “Request a new template” action and feedback modal in the Agent use-cases header - Preconfigure Jira and Linear coding agents with a webhook trigger and Clone environment mode - Preconfigure the Build & deployment optimizer with a Monday 08:00 schedule in the user's local timezone - Enforce a single trigger per agent task while allowing users to replace a schedule with a webhook, or the reverse - Display Schedule when one is configured, otherwise Webhook, consistently in Settings, service lists, and Overview ## Testing - [x] Targeted Jest tests (88 tests across 10 suites) - [x] Formatting applied to changed files - [x] ESLint on changed files - [x] Git diff check ## PR Checklist - [x] I followed naming, styling, and TypeScript rules - [x] I performed a self-review (diff inspected, dead code removed) - [x] I titled the PR using Conventional Commits with a scope - [x] I only kept necessary comments, written in English - [x] I covered new business logic with tests (unit) - [ ] I confirmed CI is green (pending)
nx e2e console-e2e
⌘K
Succeeded
nx e2e console-e2e
Click to copy
Linux
4 CPU cores
read
access token used
c1117263
staging
GitHub
console
Workspace