> ## Documentation Index
> Fetch the complete documentation index at: https://learn.cleftnotes.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Jira issues from Cleft notes

> Automatically turn Cleft voice notes and checkboxes into tracked Jira issues for engineering teams

Transform your team's voice-captured ideas and feedback into properly tracked engineering issues in Jira. Perfect for developers, engineering managers, and product teams who want to eliminate manual data entry.

<Note type="success">
  **✅ Public Template** — Ready to use now with Cleft Plus
</Note>

## Install Template

<Card title="Create Jira issues from Cleft notes" icon="bolt" href="https://zapier.com/webintent/create-zap?template=255679510" aria-label="Install Zapier template to create Jira issues from Cleft notes">
  One-click installation. No Jira experience needed. Takes 2 minutes to set up.
</Card>

## What It Does

Automatically create Jira issues from Cleft notes when you capture action items as checkboxes. Perfect for converting customer feedback, feature requests, bug reports, and meeting notes directly into your engineering workflow without manual transcription.

## How It Works

This template follows a simple 7-step automation pattern:

<Steps>
  <Step title="Capture in Cleft">
    Create a voice note or text note in Cleft with your ideas, feedback, or action items
  </Step>

  <Step title="Add Checkboxes">
    Format action items as checkboxes:

    ```markdown theme={null}
    - [ ] Implement dark mode toggle
    - [ ] Fix login button styling
    - [ ] Add keyboard shortcuts
    ```
  </Step>

  <Step title="Tag with 'tasks'">
    Add the **tasks** tag to your note. This is your human review checkpoint—review the checkboxes before issues are created in Jira.
  </Step>

  <Step title="Note Saved">
    When you save the note, the automation triggers immediately
  </Step>

  <Step title="Extract Checkboxes">
    Python code automatically extracts all unchecked checkboxes from your note
  </Step>

  <Step title="Create for Each Item">
    The system loops through each checkbox and creates a separate Jira issue
  </Step>

  <Step title="Issues Appear in Jira">
    Each checkbox becomes a new Jira issue in your project, ready for the team
  </Step>
</Steps>

## Setup Requirements

Before installing, make sure you have:

<div role="group" aria-label="Setup requirements">
  * ✅ **Cleft Plus** subscription (required)
  * ✅ **Jira Cloud** account with project access
  * ✅ **Zapier** account (free tier works)
  * ✅ Permission to create issues in your Jira project
</div>

## Installation Steps

1. **Click the Install Template button** above (opens Zapier)
2. **Sign in** with your Cleft account (or create one)
3. **Select your Jira workspace** and target project
4. **Review the field mapping**:
   * Summary: Checkbox text
   * Project: Your selected project
   * Issue Type: Task or Bug (customizable)
5. **Turn on the Zap** and you're done!

**Important**: When creating a note, add the **tasks** tag to trigger automation. This gives you a chance to review items before they sync to Jira as issues.

## Use Cases

### 1. Customer Interview → Feature Backlog

Voice record a customer interview in Cleft, noting feature requests as checkboxes. Within seconds, each request becomes a backlog item in Jira that engineering can estimate and schedule.

**Time saved**: 30 minutes per interview (eliminates typing)

### 2. Product Feedback Session → Sprint Planning

During a weekly product review, capture feedback in Cleft with checkboxes for action items. Your team gets 5-10 new Jira issues automatically, ready for the next sprint planning session.

**Time saved**: 40 minutes per session (no manual issue creation)

### 3. Support Escalations → Engineering Queue

Support team voice-logs critical bugs directly in Cleft with reproducible steps as checkboxes. Engineering sees the issues in Jira immediately, prioritized and ready to investigate.

**Time saved**: 20 minutes per batch (eliminating Jira form filling)

## Customization

<Accordion title="Change Trigger to All Notes" role="button" aria-expanded="false">
  By default, only notes tagged with **tasks** will trigger automation (your human review checkpoint). To trigger from every note instead:

  1. Open the Zap in Zapier
  2. Edit the trigger step
  3. Remove the "tags contains tasks" filter
  4. Save and turn on

  Now every note with checkboxes will auto-sync to Jira, with no review step.
</Accordion>

<Accordion title="Customize Issue Fields" role="button" aria-expanded="false">
  By default, checkboxes become issue summaries. You can customize:

  * **Project**: Change which Jira project receives issues
  * **Issue Type**: Use Bug, Task, Story, or Epic
  * **Labels**: Auto-tag all issues (e.g., "from-cleft", "voice-capture")
  * **Assignee**: Auto-assign to team members
  * **Priority**: Set default priority for all issues

  To customize, open the Zap in Zapier and edit the "Create Jira Issue" step.
</Accordion>

<Accordion title="Add Filters for Specific Notes" role="button" aria-expanded="false">
  Want only certain notes to create issues? Add a filter step:

  1. In Zapier, add a Filter between "Note Created" and "Extract Checkboxes"
  2. Filter by note title, content, or tags
  3. Only notes matching your criteria will create Jira issues

  Example: Only process notes tagged with "bugs" or containing "critical"
</Accordion>

<Accordion title="Link Issues Back to Cleft" role="button" aria-expanded="false">
  Include your note's link in the Jira issue description so engineers can see the full context:

  1. Edit the "Create Issue" step in Zapier
  2. In the Description field, add:
     ```
     Source note: [Link to Cleft note]
     ```
  3. This gives your team full context without context-switching
</Accordion>

## Checkbox Format Guide

For Jira to create issues, use this exact format in Cleft:

```markdown theme={null}
- [ ] Issue title here
- [ ] Another issue to track
- [ ] And one more
```

**Important**:

* Start each line with a dash and space: `- `
* Include empty brackets: `[ ]` (not `[x]`)
* Each checkbox becomes a separate Jira issue
* Completed checkboxes (`[x]`) are skipped

## Troubleshooting

<AccordionGroup>
  <Accordion title="No issues are being created" role="button" aria-expanded="false">
    **Check these items:**

    1. **Zap is ON**: Open Zapier and verify the Zap toggle is ON (blue)
    2. **Checkbox format**: Confirm you used `- [ ] text` (with space after dash)
    3. **Jira connection**: Verify Jira is properly connected to your Zapier account
    4. **Project permissions**: Ensure your Jira account can create issues in that project
    5. **Zap runs**: Check Zapier's "Runs" tab to see if the automation even triggered
  </Accordion>

  <Accordion title="Wrong project is receiving issues" role="button" aria-expanded="false">
    1. Open the Zapier Zap editor
    2. Go to the "Create Jira Issue" step
    3. Check the Project field—make sure it's set to the correct project
    4. Save and test again
  </Accordion>

  <Accordion title="Issues have blank titles" role="button" aria-expanded="false">
    This means your checkboxes don't match the expected format. Make sure each line:

    * Starts with `- ` (dash and space)
    * Has `[ ]` (empty brackets)
    * Has text after the brackets

    **Correct**: `- [ ] Fix button styling`
    **Wrong**: `- [ ]` (empty), `- [ ] ` (just spaces), `[ ] Fix button` (missing dash)
  </Accordion>

  <Accordion title="Zap turned off unexpectedly" role="button" aria-expanded="false">
    Zapier may pause your Zap if it encounters repeated errors. Common causes:

    * Cleft account disconnected
    * Jira project permissions changed
    * Jira API limit exceeded

    **Fix**: Reconnect your accounts in Zapier and turn the Zap back on.
  </Accordion>

  <Accordion title="Creating too many issues" role="button" aria-expanded="false">
    If every note is creating issues and you only want certain notes:

    1. Add a Filter step in Zapier (between trigger and code step)
    2. Filter by note title, tags, or content
    3. Only matching notes will create issues

    Example: Only process notes with title containing "bugs"
  </Accordion>
</AccordionGroup>

## Advanced Tips

<Tabs>
  <Tab title="Batch Processing">
    You can create many issues at once! Add 10+ checkboxes to a single note, and each will become a separate Jira issue. Useful for processing meeting notes or feedback sessions with multiple action items.
  </Tab>

  <Tab title="Auto-Labeling">
    In the Jira "Create Issue" step, add a label like `from-cleft` to all auto-created issues. This makes it easy to filter and audit issues that came from voice capture vs manual creation.
  </Tab>

  <Tab title="Different Issue Types">
    By default, checkboxes become Tasks. You can create different issue types for different scenarios:

    * 🐛 Bug reports (use Bug type)
    * ✨ Feature requests (use Story type)
    * 🎯 Engineering tasks (use Task type)

    Just create separate Zaps with different settings!
  </Tab>

  <Tab title="Team Assignment">
    Assign issues to specific team members automatically:

    1. Add an assignee field in the Zapier step
    2. Map it to a specific person or use a custom field
    3. All new issues will be assigned automatically
  </Tab>
</Tabs>

## Template Details

* **Template ID**: 255679510
* **Status**: ✅ Public (live and ready)
* **Trigger Type**: Note Created (immediate)
* **Target Platform**: Jira Cloud
* **Prerequisites**: Cleft Plus, Jira account, Zapier account
* **Setup Time**: \~2 minutes
* **Annual Time Savings**: \~15-20 hours (depending on volume)

## Perfect For

* 👨‍💻 **Engineering teams** capturing bugs and feature requests
* 📋 **Product managers** feeding customer feedback into backlog
* 🎯 **Team leads** organizing action items from meetings
* 🔧 **DevOps teams** logging infrastructure tasks and improvements

## Related Templates

<CardGroup cols={2} role="group" aria-label="Similar project management templates">
  <Card title="GitHub Issues" href="/user-guides/integrations/github/zaps/create-github-issues-from-cleft-notes" aria-label="Create GitHub issues from Cleft notes">
    For open-source and developer-first workflows
  </Card>

  <Card title="Trello" href="/user-guides/integrations/trello/zaps/create-trello-cards-from-cleft-notes" aria-label="Create Trello cards from Cleft notes">
    For visual, Kanban-style project management
  </Card>

  <Card title="Asana" href="/user-guides/integrations/asana/zaps/create-asana-tasks-from-cleft-notes" aria-label="Create Asana tasks from Cleft notes">
    For complex project workflows with dependencies
  </Card>

  <Card title="ClickUp" href="/user-guides/integrations/clickup/zaps/create-clickup-tasks-from-cleft-notes" aria-label="Create ClickUp tasks from Cleft notes">
    For all-in-one workspace management
  </Card>
</CardGroup>

## Need Help?

* 💬 **Cleft Support**: [Contact our support team](https://support.cleftnotes.com)
* 🐛 **Report an Issue**: [File a bug report](https://github.com/CleftAI/Cleft-RN/issues)

***

Ready to turn voice notes into tracked issues? [Install the Jira template now →](https://zapier.com/webintent/create-zap?template=255679510)