Create Ticket

Goal

• Ticket is created in issue tracker system.

Prerequisites

• ticket-tools

  skill available

• scratch

  skill available

Input

Before creating

1. Title - see guidelines below.
2. Description - see guidelines below.
3. Type - Story, Task, Bug, Sub-task, or system equivalent.
4. Parent - Epic or grouping context; ask if required by target project.
5. Assignee - assign to self, user, or project default.
6. Sprint - none (backlog), current, or future.
7. Priority - Low, Medium, High, or system equivalent.
8. Metadata - project or system dependent custom fields like Team, Labels.

Title Guidelines

• Concise
• Must focus on the goal, not the solution.
• For features/tasks: imperative mood.
• For bugs: describe the current state (the issue), not the desired behavior or proposed fix.

Description Guidelines

• Tone: Professional, objective, direct.
• Focus: Focus on the problem and the goal, not the proposed solution. For bugs, describe the issue, not the fix.
• Details: Sufficient for immediate implementation without extra clarification.
• Structure:
  • Paragraphs for logical context.
  • Lists for requirements, tasks, or options.
  • Code blocks for logs, code snippets, configs, or command outputs.
  • References or links to files, pull requests, docs, or other tickets.

Bug Description Template

• Pre-conditions: Required system state, environment, user account, or configuration.
• Steps to Reproduce (STR): Numbered actions triggering the bug.
• Actual Result (AR): Incorrect behavior with error logs or messages.
• Expected Result (ER): Correct expected behavior.

Create

scratch

Skill(skill: "scratch", args: "write ticket-description md")

<description_file_path>

ticket-tools

FIELDS_JSON

{"assignee": "self", "priority": "High", "labels": ["bug"]}

Skill(skill: "ticket-tools", args: "create <PROJECT_KEY> <TITLE> <description_file_path> [TYPE] [PARENT] [FIELDS_JSON]")

Output

ticket-tools