# Project Defaults Source: https://docs.ziggy.sh/configuration/project-defaults Configure default Jira projects for your workspace and users ## Overview Ziggy uses a project resolution system to determine which Jira project to create issues in. You can set defaults using the **Home** tab in Slack. ## Project Resolution Priority When you create an issue, Ziggy determines the project in this order: 1. **Inline specification** - `Ziggy in PROJ: create a task` 2. **Default project** - Set via the Home tab 3. **Most active project** - Falls back to the most recently used project ## Setting Default Project Open the Ziggy **Home** tab in Slack and configure your default project there. This is where you manage all project settings. ## Inline Override Specify the project in your message to override any defaults: ``` Ziggy in BACKEND: create a bug for the API timeout ``` ``` Ziggy create a task in MOBILE for the app crash ``` ## Examples ### Scenario 1: Single-project team A small team all working on the same project: 1. Set default project to ACME in the Home tab 2. All team members create issues without specifying project 3. All issues go to ACME ### Scenario 2: Cross-team collaboration When creating an issue for another team: ``` Ziggy in MOBILE: create a bug for the iOS crash @mobileteam mentioned ``` The inline `in MOBILE:` overrides any defaults. ## Viewing Current Settings Check your current project configuration: ``` /ziggy status ``` Or open the Ziggy **Home** tab to see and change your defaults. # Slash Commands Source: https://docs.ziggy.sh/configuration/slash-commands All available Ziggy slash commands ## Overview Ziggy provides slash commands for configuration and status checks. These work in any Slack channel. ## Available Commands ### /ziggy connect Connect your Jira Cloud instance to Ziggy. ``` /ziggy connect ``` Opens the Jira OAuth flow. Once connected, your 14-day free trial begins. **Access:** All users *** ### /ziggy status View connection and subscription status. ``` /ziggy status ``` Shows: * Jira connection status * Connected Jira site * Default project * Subscription status and trial days remaining **Access:** All users *** ### /ziggy help Show available commands and usage examples. ``` /ziggy help ``` **Access:** All users ## Configuring Projects Use the **Home** tab in Slack to configure default projects, manage your subscription, and more. Open Ziggy in the Apps section of your Slack sidebar and click the **Home** tab. ## Command Reference | Command | Description | Access | | ---------------- | -------------------------------- | --------- | | `/ziggy connect` | Connect Jira to workspace | All users | | `/ziggy status` | View connection and subscription | All users | | `/ziggy help` | Show help message | All users | # Connecting Jira Source: https://docs.ziggy.sh/connecting-jira Link your Jira Cloud instance to Ziggy ## Requirements Before connecting Jira, ensure you have: * **Jira Cloud** — Ziggy works with Jira Cloud (not Jira Server or Data Center) * **Jira permissions** — You need permission to authorize third-party apps in your Jira instance ## Connect via OAuth In any Slack channel, type: ``` /ziggy connect ``` Click the authorization link. You'll be redirected to Atlassian to grant Ziggy access. Ziggy requests permission to: * Read and write issues * Read projects and issue types * Upload attachments * Read and write comments Once authorized, Ziggy will confirm the connection in Slack and start your 14-day free trial. ## Check connection status To verify your Jira connection at any time: ``` /ziggy status ``` This shows: * Connection status * Connected Jira site * Default project (if set) * Subscription status and trial days remaining ## Troubleshooting Ensure you have permission to authorize third-party apps in your Jira instance. Contact your Jira admin if needed. If you connected the wrong Jira instance, contact [support@ziggy.sh](mailto:support@ziggy.sh) to reset your connection. Ziggy can only access projects that the authorizing user has access to. Make sure you have the necessary Jira permissions. ## Security * Ziggy uses OAuth 2.0 for secure authentication * Credentials are encrypted at rest * Ziggy only accesses Jira when explicitly triggered by a user mention * All data is scoped to your workspace — no cross-tenant access # Add Comments Source: https://docs.ziggy.sh/features/comments Add comments to Jira issues from Slack ## Overview Add comments to existing Jira issues without leaving Slack. Great for adding updates, context, or decisions from ongoing conversations. ## Basic Usage ``` @Ziggy add a comment to PROJ-123 - testing is done, all good ``` ``` @Ziggy comment on BACKEND-456 saying we reviewed this and it's approved ``` ``` @Ziggy note on MOBILE-789 that the fix went out to production ``` ## Trigger Words * `add comment to` * `comment on` * `note on` ## How It Works 1. Ziggy extracts the issue key and comment text 2. The comment is formatted in Atlassian Document Format (ADF) 3. Comment is added to the Jira issue 4. Ziggy confirms the comment was added ## Examples ``` @Ziggy comment on PROJ-123 - we're blocked waiting for the API changes, should be unblocked next week ``` After a Slack discussion about approach: ``` @Ziggy add a comment to PROJ-456 - team decided to go with WebSockets instead of polling ``` ``` @Ziggy note on PROJ-789 that this just went to staging for QA ``` ## Tips * Keep comments concise but include enough context * Reference the Slack thread if the comment needs more background * Use comments to keep stakeholders updated on progress # Done Notifications Source: https://docs.ziggy.sh/features/done-notifications Get notified in Slack when issues are resolved ## Overview When a Jira issue created by Ziggy is resolved, Ziggy posts a notification back to the original Slack thread. This closes the loop and keeps everyone informed. ## How It Works 1. You create a Jira issue via Ziggy in a Slack thread 2. Someone resolves the issue in Jira (moves to "Done" or similar) 3. Ziggy detects the status change via webhook 4. A notification is posted to the original Slack thread ## Notification Message When an issue is resolved, you'll see: > ✅ **PROJ-123** is resolved. One less thing to worry about. > > \[View in Jira] The notification includes: * Issue key with link to Jira * "View in Jira" button for quick access ## Supported Statuses Ziggy sends notifications when issues transition to "Done" status. This works with: * Standard Jira "Done" status * Custom "Done" statuses in your workflow * Any status in the "Done" category ## Notes * Notifications only appear for issues created through Ziggy * The notification goes to the exact thread where the issue was created * Team members following the thread will see the update # File Attachments Source: https://docs.ziggy.sh/features/file-attachments Automatically attach files from Slack to Jira issues ## Overview When you create a Jira issue from a Slack thread, any files shared in that thread are automatically uploaded as attachments to the new issue. ## Supported Files Ziggy handles common file types: * **Images** — PNG, JPG, GIF, SVG * **Documents** — PDF, Word, Excel, PowerPoint * **Code** — Text files, logs, JSON * **Screenshots** — Pasted images in Slack ## How It Works 1. You share files in a Slack thread 2. When you ask Ziggy to create an issue, it detects all files in the thread 3. Files are downloaded from Slack and uploaded to the new Jira issue 4. Attachments appear in the issue's Attachments section ## Example **Thread:** > User: The button is misaligned on mobile > User: \[screenshot-1.png] > User: \[screenshot-2.png] > Dev: What browser? > User: Safari on iOS 17 **Command:** ``` Ziggy create a bug for this ``` **Result:** Bug created with both screenshots attached, plus repro details in the description. ## Notes * File uploads happen after the issue is created (non-blocking) * Large files may take a moment to upload * Files are only attached from the specific thread, not the entire channel # Issue Assignment Source: https://docs.ziggy.sh/features/issue-assignment Assign Jira issues to teammates from Slack ## Overview Assign or reassign existing Jira issues without opening Jira. Just mention the issue key and the person. ## Basic Usage ``` @Ziggy assign PROJ-123 to @john ``` ``` @Ziggy can you reassign BACKEND-456 to Sarah? ``` ``` @Ziggy give MOBILE-789 to @mike, he's taking over ``` ## Trigger Words * `assign` * `reassign` * `give` ## How It Works 1. Ziggy extracts the issue key and assignee name from your message 2. For Slack mentions, Ziggy looks up the user's email to find their Jira account 3. For plain names, Ziggy searches Jira users 4. The issue is assigned and Ziggy confirms the change ## User Matching Ziggy matches users in this order: 1. **Slack mention** (`@john`) - Uses the linked email to find the Jira user 2. **Name match** - Searches Jira users by display name Using Slack mentions is more reliable since it matches by email address. ## Examples ``` @Ziggy assign PROJ-123 to @sarah ``` > Assigns PROJ-123 to Sarah (matched by Slack email) ``` @Ziggy reassign BACKEND-456 to Mike Chen ``` > Searches for "Mike Chen" in Jira users and assigns ``` @Ziggy give MOBILE-789 to the mobile team lead ``` > Ziggy will ask for clarification if the name is ambiguous # Issue Creation Source: https://docs.ziggy.sh/features/issue-creation Create well-structured Jira issues from Slack conversations ## 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: ``` @Ziggy the checkout page is broken on mobile, can you file a bug? ``` ``` @Ziggy we need a task to update the onboarding flow ``` ``` @Ziggy can you open a story for the new dashboard Sarah mentioned? ``` ## Trigger Words Ziggy recognizes these action words: * `create` * `open` * `file` * `report` ## Specifying Details ### Priority Include priority naturally: ``` @Ziggy this is urgent - users can't reset their passwords ``` ``` @Ziggy low priority but we should track it - the footer link is wrong ``` Priority levels: Highest, High, Medium, Low, Lowest ### Project Override the default project inline: ``` @Ziggy bug in MOBILE - the app crashes when you upload a photo ``` ``` @Ziggy can you create a task in BACKEND for the API refactor? ``` ### Assignee Assign the issue during creation: ``` @Ziggy create a task for this and assign it to @sarah ``` ``` @Ziggy this is a bug for John - the login page is timing out ``` ## 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:** ``` @Ziggy can you file a bug for this? seems like it's only happening on iOS ``` **Result:** Bug with repro steps, device info, and screenshot attached **Message:** ``` @Ziggy we really need dark mode on the settings page - should include a toggle and respect system preferences. high priority ``` **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:** ``` @Ziggy create a task for this and assign to @mike ``` **Result:** Task assigned to Mike with context from the thread # Issue Search Source: https://docs.ziggy.sh/features/issue-search Find existing Jira issues without leaving Slack ## Overview Search your Jira backlog directly from Slack. Ziggy returns matching issues with key details so you can quickly find what you're looking for. ## Basic Usage ``` @Ziggy are there any issues about the login page? ``` ``` @Ziggy search for payment bugs ``` ``` @Ziggy check if someone already filed something about the API timeout ``` ## Trigger Words Ziggy recognizes these search actions: * `find` * `search` * `check` * `look for` ## Search Results Ziggy returns up to 5 matching issues with: * **Issue key** - Clickable link to Jira (e.g., PROJ-123) * **Summary** - Issue title * **Status** - Current workflow status * **Priority** - Issue priority level * **Assignee** - Who it's assigned to ## Examples ``` @Ziggy find any open bugs in MOBILE ``` ``` @Ziggy what's assigned to @sarah right now? ``` ``` @Ziggy check if there's already something about the checkout flow ``` ## Tips * Be specific with keywords to get better results * Use project keys to narrow scope: `@Ziggy find bugs in BACKEND` * Search before creating to avoid duplicates # Introduction Source: https://docs.ziggy.sh/index Turn Slack conversations into Jira tickets in seconds ## Say it in Slack. Ziggy handles Jira. Ziggy is a Slack agent that turns any message or thread into a complete, high-quality Jira ticket in about 10 seconds — with the right context, fields, and formatting. Install Ziggy and create your first ticket in 5 minutes. ## The Problem Teams waste hours on "work about work" inside Slack: * Bug reports appear in threads and never make it to Jira * PMs ask for feature changes that get lost in chat * Someone says "can you open a Jira?" and it doesn't happen — or it happens badly * Important thread context stays in Slack and never makes it into the ticket ## The Solution Create Jira issues without leaving Slack AI extracts requirements, acceptance criteria, and context automatically Captures the full conversation, not just a summary From Slack message to Jira ticket in \~10 seconds ## What Ziggy Creates When you ask Ziggy to create a ticket, it generates: * **Summary** — Clear, concise title (max 255 characters) * **Description** — Structured content with context, requirements, and acceptance criteria * **Issue Type** — Bug, Task, Story, or Improvement based on context * **Priority** — Extracted from the conversation or explicitly requested * **Attachments** — Files shared in the thread are automatically uploaded * **Slack Link** — Permalink back to the original conversation ## Explore Features Create well-structured Jira issues from any Slack message Find existing issues without leaving Slack Assign issues to teammates directly from Slack Add comments to existing issues # Quickstart Source: https://docs.ziggy.sh/quickstart Get Ziggy running in your Slack workspace in 5 minutes ## Three steps to your first Jira ticket Add Ziggy to your Slack workspace from [ziggy.sh](https://ziggy.sh). You'll need to authorize Ziggy to: * Read messages where Ziggy is mentioned * Post messages in channels * Access files shared in conversations In any Slack channel, type `/ziggy connect` and follow the OAuth flow to connect your Jira Cloud instance. Connecting Jira starts your 14-day free trial. In any Slack thread, mention Ziggy: ``` Ziggy create a task for this ``` Ziggy will read the thread context and create a complete Jira issue. ## What happens next Once you create your first ticket, Ziggy will: 1. React with an eyes emoji to acknowledge your request 2. Read the thread and gather context 3. Extract issue details using AI 4. Create the Jira issue 5. Post a confirmation with a link to the new issue ## Set your default project To skip the project selection step, set a default project in the Ziggy **Home** tab. Open Ziggy in the Apps section of your Slack sidebar and click **Home** to configure your default project. You can always override the default by specifying a project inline: `@Ziggy in PROJ: create a task` ## Next steps Learn all the ways to create issues See all available commands