Skip to main content

​
Overview

Issue creation is Ziggy’s core feature. Mention Ziggy in any Slack message or thread, and it will create a complete Jira issue with:
  • Structured summary and description
  • Appropriate issue type (Bug, Task, Story, Improvement)
  • Priority level
  • Context from the thread
  • Link back to the Slack conversation

​
Basic Usage

Mention Ziggy with a description of what you need:

​
Trigger Words

Ziggy recognizes these action words:
  • create
  • open
  • file
  • report

​
Specifying Details

​
Priority

Include priority naturally:
Priority levels: Highest, High, Medium, Low, Lowest

​
Project

Override the default project inline:

​
Assignee

Assign the issue during creation:

​
Thread Context

When you mention Ziggy in a thread, it reads:
  1. The root message
  2. All replies in the thread
  3. Files and images shared
This context is used to:
  • Extract requirements and acceptance criteria
  • Identify reproduction steps for bugs
  • Capture decisions and constraints discussed

​
What Gets Created

​
For Bugs

  • Summary - Clear bug title
  • Description:
    • Context / Background
    • Steps to reproduce
    • Expected vs actual behavior
    • Environment details (if mentioned)
  • Attachments - Screenshots and files from the thread
  • Slack link - Permalink to the original conversation

​
For Tasks / Stories

  • Summary - Clear task title
  • Description:
    • Context / Background
    • Requirements
    • Acceptance criteria
    • Open questions (if any)
  • Attachments - Relevant files from the thread
  • Slack link - Permalink to the original conversation

​
Duplicate Detection

Ziggy can check for similar existing issues before creating new ones. This is off by default for faster results, but you can turn it on in the Home tab under settings. When enabled:
  1. Ziggy searches for similar issues before creating
  2. If potential duplicates are found, Ziggy shows them to you
  3. You can choose to view them or create anyway
This adds a few seconds to each request but helps keep your backlog clean.

​
Examples

Thread:
User: The app crashes when I upload a PDF Dev: What device? User: iPhone 14, iOS 17 User: [screenshot.png]
Message:
Result: Bug with repro steps, device info, and screenshot attached
Message:
Result: Story with requirements and acceptance criteria, marked High priority
Thread:
PM: We need to update the API docs before launch @mike can you handle this?
Message:
Result: Task assigned to Mike with context from the thread