> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/build/integration-overview/enterprise/jira.md).

# Atlassian JIRA

Seamlessly connect DarcyIQ with Atlassian JIRA to **create tickets, update issues, and track projects directly through natural conversation**. Transform meeting notes into tickets, workflow outputs into stories, and keep your entire team synchronized without leaving DarcyIQ.

{% hint style="success" %}
**Zero Context Switching**: Say "Create a JIRA ticket for the security issue we just discussed" and watch it appear in your project board instantly.
{% endhint %}

## Overview

The JIRA integration transforms how you manage projects by eliminating the friction between conversation and action.

| Capability                    | Function                                     | Business Impact              |
| ----------------------------- | -------------------------------------------- | ---------------------------- |
| **Natural Language Actions**  | Create and update tickets through chat       | 75% faster ticket creation   |
| **Automatic Ticket Creation** | Generate tickets from meetings and workflows | Never miss an action item    |
| **Real-Time Sync**            | Bi-directional updates between systems       | Always current information   |
| **Smart Field Mapping**       | AI understands JIRA fields and requirements  | Accurate ticket creation     |
| **Bulk Operations**           | Handle multiple tickets simultaneously       | Efficient project management |

## Key Features

### Ticket Management

Complete JIRA ticket lifecycle management through DarcyIQ:

| Action      | Natural Language Example                    | Result               |
| ----------- | ------------------------------------------- | -------------------- |
| **Create**  | "Create a bug ticket for the login issue"   | New ticket in JIRA   |
| **Update**  | "Update PROJ-123 status to In Progress"     | Status changed       |
| **Comment** | "Add comment to PROJ-456 with test results" | Comment added        |
| **Assign**  | "Assign PROJ-789 to John Smith"             | Assignee updated     |
| **Link**    | "Link PROJ-234 to PROJ-567"                 | Tickets linked       |
| **Search**  | "Show me all critical bugs this sprint"     | Filtered ticket list |

### Automatic Ticket Generation

DarcyIQ automatically creates tickets from various sources:

| Source               | Trigger                             | Ticket Type     |
| -------------------- | ----------------------------------- | --------------- |
| **Meetings**         | Action items identified             | Task or Story   |
| **Chat Discussions** | Explicit request or AI detection    | Any type        |
| **Workflows**        | Workflow completion with follow-ups | Configured type |
| **Activity Log**     | Task escalation                     | Task            |
| **Research Reports** | Identified opportunities            | Story or Epic   |

### Project Tracking

Monitor and manage your JIRA projects:

| Query Type           | Example                        | Information Returned               |
| -------------------- | ------------------------------ | ---------------------------------- |
| **Sprint Status**    | "Show current sprint progress" | Burndown, velocity, remaining work |
| **Team Workload**    | "Who has the most tickets?"    | Assignment distribution            |
| **Blockers**         | "List all blocked issues"      | Impediments requiring attention    |
| **Due Dates**        | "What's due this week?"        | Upcoming deadlines                 |
| **Release Planning** | "Show release 2.0 status"      | Version progress and issues        |

## Setup and Configuration

### Prerequisites

| Requirement        | Description                        | How to Obtain                 |
| ------------------ | ---------------------------------- | ----------------------------- |
| **JIRA Account**   | Active Atlassian JIRA instance     | Cloud or Server instance      |
| **API Token**      | Authentication credential          | Generate in Atlassian account |
| **Project Access** | Permissions to create/edit tickets | Admin configuration           |
| **User Account**   | JIRA user for integration          | Service account recommended   |

### Configuration Steps

{% stepper %}
{% step %}
**Generate API Token**

1. Log into your Atlassian account
2. Navigate to Account Settings → Security → API Tokens
3. Create new token with descriptive name
4. Copy token (shown only once)
   {% endstep %}

{% step %}
**Configure in DarcyIQ**

1. Go to Settings → Integrations → JIRA
2. Enter your JIRA instance URL
3. Provide username (email) and API token
4. Select default project
5. Map custom fields if needed
   {% endstep %}

{% step %}
**Test Connection**

1. Click "Test Connection"
2. Verify project list loads
3. Create test ticket
4. Confirm ticket appears in JIRA
   {% endstep %}

{% step %}
**Configure Automation**

1. Set rules for automatic ticket creation
2. Define field mappings
3. Configure notification preferences
4. Enable/disable features as needed
   {% endstep %}
   {% endstepper %}

## Using JIRA Integration

### Through Darcy Chat

Natural language commands for JIRA operations:

#### Creating Tickets

```
"Create a bug ticket: Login fails with SSO enabled"
"Make a story for implementing the new dashboard"
"Add a task to investigate the performance issue"
"Create an epic for Q4 product launch"
```

#### Updating Tickets

```
"Move PROJ-123 to In Review"
"Add 3 story points to PROJ-456"
"Set priority of PROJ-789 to Critical"
"Add Sarah as a watcher to PROJ-234"
```

#### Searching and Reporting

```
"Show me all my open tickets"
"List bugs found this week"
"What's the status of epic PROJ-100?"
"Find all tickets mentioning 'authentication'"
```

### From Meetings

Automatic ticket creation from meeting discussions:

| Meeting Context      | Ticket Generation        | Example                            |
| -------------------- | ------------------------ | ---------------------------------- |
| **Action Items**     | One ticket per action    | "John will review the code" → Task |
| **Bugs Discussed**   | Bug tickets with details | "Users report slow loading" → Bug  |
| **Feature Requests** | Story tickets            | "Customer wants dark mode" → Story |
| **Decisions**        | Documentation tickets    | "Decided to use AWS" → Task        |

### In Workflows

Configure workflows to interact with JIRA:

| Workflow Step    | JIRA Action            | Use Case           |
| ---------------- | ---------------------- | ------------------ |
| **Initiation**   | Create planning ticket | Project kickoff    |
| **Completion**   | Update ticket status   | Mark work complete |
| **Approval**     | Create review ticket   | Approval workflow  |
| **Exception**    | Create bug/issue       | Error handling     |
| **Notification** | Add comment            | Status updates     |

## Advanced Features

### Smart Ticket Creation

AI-enhanced ticket generation:

| Enhancement              | How It Works                            | Benefit            |
| ------------------------ | --------------------------------------- | ------------------ |
| **Context Extraction**   | Pulls relevant details from discussions | Complete tickets   |
| **Acceptance Criteria**  | Generates criteria from requirements    | Clear expectations |
| **Dependency Detection** | Identifies related tickets              | Proper linking     |
| **Effort Estimation**    | Suggests story points                   | Consistent sizing  |
| **Component Assignment** | Routes to right team                    | Efficient triage   |

### Bulk Operations

Handle multiple tickets efficiently:

| Operation            | Example Command                        | Result                 |
| -------------------- | -------------------------------------- | ---------------------- |
| **Mass Update**      | "Move all bugs to next sprint"         | Bulk sprint assignment |
| **Batch Creation**   | "Create tasks for each requirement"    | Multiple tickets       |
| **Group Transition** | "Close all completed stories"          | Status updates         |
| **Bulk Assignment**  | "Assign all UI tickets to design team" | Team distribution      |

### JQL Integration

Use JIRA Query Language through DarcyIQ:

```
"Run JQL: project = PROJ AND status = Open AND assignee = currentUser()"
"Find tickets matching: labels in (customer, priority) AND created >= -7d"
"Show: fixVersion = 2.0 AND type = Bug ORDER BY priority DESC"
```

{% hint style="info" %}
**Pro Tip**: Start by enabling automatic ticket creation from meetings - this alone will ensure no action item is ever lost. Then gradually expand to use natural language commands for daily ticket management.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.darcyiq.com/build/integration-overview/enterprise/jira.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.