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, allowing DinoAI to understand requirements, fix issues, and implement features based on information stored in Jira.

Setting Up Jira Integration

Prerequisite

You must add Jira as an integration in your Paradime environment for the Jira Tool to work properly.

Step 1: Gather Your Jira Information

In Jira:

1. Base URL: Get your Jira Base URL (e.g., https://acme.atlassian.net)
2. API Token:

   • Visit the api tokens section of Jira
   • Select "Create API token"

   • Provide a name for your token (e.g., "Paradime DinoAI")

   • Copy/save the generated token

3. User Email:

   • Use the email associated with your Jira user account

   • This must be the email used to create the API token

Step 2: Configure in Paradime

Configure these values as environment variables in your Paradime environment:

Capabilities

Capability	What It Does
Access Ticket Information	Fetch details from Jira tickets using issue keys or URLs
Extract Requirements	Understand task requirements and acceptance criteria
Fix Reported Issues	Help resolve bugs and errors documented in tickets
Track Work Implementation	Associate code changes with specific Jira issues

Using the Jira Tool

1. Open DinoAI in the left panel of the Code IDE

2. Select the Jira tool from the tools menu

3. Enter the Jira issue key or URL you want to reference (e.g., "FEAT-123" or a full Jira URL)

4. Add your prompt explaining what you want DinoAI to do with the ticket information

5. Grant permission when DinoAI asks to access the Jira ticket

6. Review and implement DinoAI's suggested actions

Example Use Cases

Summarizing Documentation

• Prompt: "I need to implement the feature described in FEAT-456. Can you help me get started?"

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

Extracting Information

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

• 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 Git Branches

The Jira Tool works seamlessly with DinoAI's Terminal capabilities to:

1. Create branches using standard Jira-based naming conventions (e.g., feature/JIRA-123)

2. Reference ticket IDs in commit messages

3. Track changes back to specific requirements or issues

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

---

Best Practices

1. Use clear ticket references - Include the exact Jira issue key or URL in your prompt

2. Ensure ticket quality - DinoAI works best with well-documented Jira tickets that include clear descriptions

3. Verify suggestions - Always review DinoAI's interpretation of requirements before implementing

4. Combine with Terminal tool - Let DinoAI help with the full workflow from ticket to implementation to testing