Aident Loadout を通じて Jira Tools の Jira Create Issue を使用します。実行前に入力、出力、設定、料金、リスクを確認できます。
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…
labelsarrayList of labels to categorize the issue; new labels are created if they don't exist.
parentstringParent 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…
summary必須stringREQUIRED. 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').
assigneestringAccount 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_datestringExpected resolution date in YYYY-MM-DD format.
prioritystringPriority 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…
reporterstringAccount ID of the user reporting the issue. Defaults to the API request user if unspecified.
versionsarrayList of IDs for versions affected by this issue; versions must exist in the project.
sprint_idintegerID of the sprint to assign this issue to. The issue will be added to the specified sprint if provided.
componentsarrayList of component IDs (e.g., '10000'); components must already exist in the project.
issue_type必須stringREQUIRED. 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')…
descriptionDetailed 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…
data必須Data from the action execution
errorstringError if any occurred during the execution of the action
successful必須booleanWhether or not the action execution was successful or not
API キー接続。リスクレベル 2/5。
無料 Action