Jira Tools

Jira Create Issue

Utilisez Jira Create Issue avec Jira Tools via Aident Loadout. Vérifiez les entrées, sorties, la configuration, le tarif et le risque avant exécution.

Action d'écritureNiveau de risque 2 sur 5Connexion par clé APIAction gratuite

Utiliser Jira Create Issue

Description du fournisseur

Creates a new Jira issue (e.g., bug, task, story) in a specified project. IMPORTANT: Different Jira projects may have custom required fields beyond the standard ones (summary, project_key, issue_type). If issue creation fails with 'field X is required', use JIRA_GET_CREATE_METAD…

App propriétaire

Jira Tools

Entrées requises

labelsarray

List of labels to categorize the issue; new labels are created if they don't exist.

parentstring

Parent issue key (e.g., 'PROJ-123') or issue ID. IMPORTANT: This field should ONLY be used when creating sub-task issue types (e.g., 'Sub-task', 'Subtask'). It is required for sub-tasks. Jira enforces strict hierarchy rules: standard issue types (Task, Story, Bug) can ONLY have…

summaryObligatoirestring

REQUIRED. Brief, descriptive title for the issue. This is the main headline that will appear in Jira (e.g., 'Fix login button not working', 'Add user profile page').

assigneestring

Account ID of the user to assign the issue to. Must be a valid Jira account ID in one of these formats: (1) Cloud format with tenant ID and UUID: '712020:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx', or (2) Legacy 24-character hex string: '5b10a2844c20165700ede21g'. IMPORTANT: Do NOT p…

due_datestring

Expected resolution date in YYYY-MM-DD format.

prioritystring

Priority level for the issue. Can be either a priority name or a valid priority ID from the Jira instance. IMPORTANT: Priority names are completely instance-specific and vary by Jira configuration (e.g., some instances use 'Highest'/'High'/'Medium'/'Low'/'Lowest', while others u…

reporterstring

Account ID of the user reporting the issue. Defaults to the API request user if unspecified.

versionsarray

List of IDs for versions affected by this issue; versions must exist in the project.

sprint_idinteger

ID of the sprint to assign this issue to. The issue will be added to the specified sprint if provided.

componentsarray

List of component IDs (e.g., '10000'); components must already exist in the project.

issue_typeObligatoirestring

REQUIRED. Type of the issue - must be valid for the target project as available types vary by project configuration. CRITICAL: Always use JIRA_GET_ISSUE_TYPES to check valid types for your project BEFORE creating issues. Can be either a type name (e.g., 'Task', 'Story', 'Epic')…

description

Detailed description of the issue. Accepts either: (1) A plain text or Markdown string (converted to ADF internally), or (2) A pre-formatted Atlassian Document Format (ADF) dict with keys 'type'='doc', 'version'=1, and 'content' array. When passing ADF directly, formatting is pr…

Jira Create Issue

Description du fournisseur

App propriétaire

Entrées requises

Sortie observable

Configuration et approbation

Tarifs et limites

Skills qui utilisent cette Action

Source officielle