> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/dino-ai/copilot/use-cases/fixing-errors-with-jira.md).
# Fixing Errors with Jira
Streamline the process of fixing production issues by connecting ticket information directly to your development workflow.
Context switching between Jira tickets, error logs, and your development environment slows down debugging and resolution. DinoAI can access Jira ticket details, analyze errors, and guide you through the fix process all in one interface.
### Example Prompt
> *Help me fix the issue described in PROD-123*
{% hint style="info" %}
**Prerequisite**: You must [add Jira as an integration](/app-help/documentation/dino-ai/tools-and-features/jira-tool.md#setting-up-jira-integration) in your Paradime environment for the Jira Tool to work properly.
{% endhint %}
***
### Step-by-Step Instructions
1. [**Set up Jira integration**](/app-help/documentation/dino-ai/tools-and-features/jira-tool.md#setting-up-jira-integration) (if not already configured):
2. **Open DinoAI** by clicking the DinoAI icon (🪄) in the left panel
3. **Select the** [**Jira tool**](/app-help/documentation/dino-ai/tools-and-features/jira-tool.md) from the tools menu
4. **Enter the Jira ticket ID** (e.g., "PROD-123") in your prompt
5. **Optional*****:*** [**Add context**](/app-help/documentation/dino-ai/context.md) about what you want to do with the ticket information
6. **Review/Accept the changes** to create the file in your project
7. **Test the solution** to ensure it resolves the issue
8. **Commit and push** the changes with a reference to the ticket ID
{% @arcade/embed url="" flowId="E3Ih9rBz9Aw06XAsKh7b" %}
***
#### How It Works
After you enter your prompt:
1. DinoAI accesses your Jira ticket using the provided credentials
2. It analyzes the ticket details, including description, comments, and attachments
3. It identifies the issue type, severity, and any error logs or context
4. If configured, DinoAI applies any relevant [.dinorules](/app-help/documentation/dino-ai/dino-rules.md) preferences
5. It provides a structured plan to resolve the issue with appropriate Git workflow
***
### Key Benefits
* **Reduced Context Switching**: Access ticket information without leaving your IDE
* **Guided Troubleshooting**: Receive step-by-step instructions for resolving issues
* **Integrated Git Workflow**: Create branches, commit changes, and push fixes in one workflow
* **Knowledge Integration**: Combine ticket requirements with your project's context
* **Traceability**: Maintain connections between code changes and ticket references
---
# 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.paradime.io/app-help/products/dino-ai/copilot/use-cases/fixing-errors-with-jira.md?ask=&goal=
```
`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.