# Jira Tool

The Jira Tool allows DinoAI to access information from your Jira tickets, bringing task requirements and issue details directly into your development workflow.

This tool connects development work to Jira, enabling DinoAI to understand requirements, resolve tickets, and implement features based on information stored in Jira.

{% hint style="info" icon="plug-circle-plus" %}
**Requires Jira integration.** Before using this tool, make sure you've connected your Jira account in Paradime. See [Connecting Jira](https://docs.paradime.io/app-help/documentation/dino-ai/tools-and-features/jira-tool) to Paradime for setup instructions.
{% endhint %}

### Capabilities

The Jira Tool fetches ticket content and converts it into a format DinoAI can reason over and act on. Specifically, it:

* Fetches details from Jira tickets using issue keys or URLs
* Extracts task requirements and acceptance criteria
* Helps resolve bugs and errors documented in tickets
* Associates code changes with specific Jira issues

### Using the Jira Tool

1. Open DinoAI in the right panel of the Code IDE
2. Enter the Jira issue key or URL you want to reference (e.g., `FEAT-123` or a full Jira URL)
3. Add your prompt describing what you want DinoAI to do with the ticket information
4. Grant permission when DinoAI asks to access the Jira ticket
5. Review and implement DinoAI's suggested actions

{% @arcade/embed flowId="E3Ih9rBz9Aw06XAsKh7b" url="<https://app.arcade.software/share/E3Ih9rBz9Aw06XAsKh7b>" %}

### Example Use Cases

#### Implementing a Feature from a Ticket

**Prompt**

{% code overflow="wrap" %}

```
I need to implement the feature described in FEAT-456. Can you help me get started?
```

{% endcode %}

**Result:** DinoAI extracts the requirements from the ticket, suggests an implementation approach, and helps create the necessary models or code changes to satisfy the acceptance criteria.

#### Resolving a Production Issue

**Prompt**

{% code overflow="wrap" %}

```
I have a production branch that failed this morning. Details are in Jira ticket PROD-123. Can you help me resolve it?
```

{% endcode %}

**Result:** DinoAI accesses the ticket details, analyzes the error information, and guides you through creating a fix branch, modifying the necessary files, and testing the solution.

### Working with Other Tools

The Jira Tool works well alongside DinoAI's other capabilities to support your full development workflow:

* Combine with the **Terminal Tool** to create branches using Jira-based naming conventions (e.g., `feature/JIRA-123`) and reference ticket IDs in commit messages
* Combine with the **Confluence Tool** to cross-reference ticket requirements against linked specification pages
* Use alongside **Git Lite** to commit implementation work that traces back to a specific Jira issue

You'll need appropriate Jira permissions to access tickets. DinoAI will request permission each time it needs to access Jira information.

### Best Practices

* **Use exact ticket references** — Include the precise Jira issue key or URL in your prompt to ensure DinoAI accesses the correct ticket
* **Ensure ticket quality** — DinoAI works best with well-documented tickets that include clear descriptions, acceptance criteria, and relevant context
* **Verify suggestions** — Always review DinoAI's interpretation of requirements before implementing, especially for complex or ambiguous tickets
* **Combine with the Terminal Tool** — Let DinoAI help with the full workflow from implementation to testing, using the ticket as the source of truth throughout


---

# Agent Instructions: 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:

```
GET https://docs.paradime.io/app-help/documentation/dino-ai/tools-and-features/jira-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.