Jira

​

Introduction

• Robust Issue Tracking: Jira provides a powerful and customizable issue tracking system that allows teams to capture, organize, and track all types of work items, including bugs, tasks, user stories, and feature requests, ensuring comprehensive issue management throughout the project lifecycle.
• Agile Project Management: Jira is designed to support Agile methodologies like Scrum and Kanban, offering features such as Scrum boards, Kanban boards, sprint planning tools, and backlog management, enabling teams to effectively plan, execute, and track agile projects.
• Customizable Workflows: Jira allows for the creation of highly customizable workflows to match specific project needs and team processes. Workflows can be tailored to reflect different stages of work items, approval processes, and automated transitions, streamlining project workflows and improving efficiency.
• Comprehensive Reporting and Analytics: Jira provides a wide range of reporting and analytics features, offering real-time insights into project progress, team performance, issue resolution times, and other key metrics, enabling data-driven decision-making and continuous improvement.
• Seamless Integration Ecosystem: Jira integrates seamlessly with a vast ecosystem of Atlassian tools and third-party applications, including Confluence, Bitbucket, and various development and collaboration tools, creating a unified and connected DevOps environment.

​

Toolkit’s Account Setup and Configuration in Jira

1. Visit Atlassian Website: Open your web browser and navigate to the official Atlassian website: https://www.atlassian.com/software/jira.
2. Sign Up for Jira: Click on the “Try Jira free” or “Get it free” button to start the sign-up process for Jira.
3. Create an Atlassian Account: Follow the prompts to create an Atlassian account. You can sign up using your email address, Google account, or Apple account. For professional use, it’s recommended to use your company email address.
4. Choose a Workspace/Site Name: During the signup process, you will be asked to choose a workspace or site name for your Jira instance. Enter a suitable name for your workspace.
5. Set Up Your Project: Follow the remaining onboarding steps to set up your first Jira project. You will be prompted to choose a project template (e.g., Scrum, Kanban) and provide a project name.
6. Explore Jira Features: Once your Jira board is ready, explore the onboarding tips and familiarize yourself with Jira features, projects, boards, and navigation.

​

Generate an API Token

1. Log in to Jira: Access your Jira workspace by navigating to your Jira URL (e.g., your-workspace.atlassian.net) and logging in with your credentials.
2. Access Account Settings: Click on your profile avatar in the top right corner of the Jira interface. From the dropdown menu, select “Manage account”.
3. Navigate to Security Settings: In the Atlassian account settings page, navigate to the “Security” section in the left-hand sidebar.
4. Access API Tokens: Within the “Security” settings, locate the “API tokens” section and click on “Create and manage API tokens”.
5. Create API Token: On the “API tokens” page, click the “Create API token” button.
6. Name Your Token: In the “Create API token” dialog, enter a descriptive Label for your token, such as “ELITEA Integration Token” or “ELITEA Agent Access.” This label will help you identify the purpose of this token later.
7. Create Token: Click the “Create” button to generate the API token.
8. Securely Copy and Store Your API Token: Immediately copy the generated API token that is displayed in the pop-up window. This is the only time you will see the full token value. Store it securely in a password manager or, preferably, ELITEA’s built-in Secrets feature for enhanced security within ELITEA. You will need this API token to configure the Jira toolkit in ELITEA.

​

System Integration with ELITEA

​

Step 1: Create Jira Credentials

1. Navigate to Credentials Menu: Open the sidebar and select Credentials.
2. Create New Credential: Click the + Create button.
3. Select Jira: Choose Jira as the credential type.
4. Configure Credential Details:
   • Display Name: Enter a descriptive name (e.g., “Jira - Project Management”)
   • Base URL: Enter the base URL of your Jira instance (e.g., https://yourcompany.atlassian.net for Jira Cloud or https://jira.epam.com for Epam Jira)
   • Authentication Method: Choose your preferred authentication method:
     • Basic: Enter your username and API key
     • Bearer: Enter your token
5. Test Connection: Click Test Connection to verify that your credentials are valid and ELITEA can successfully connect to Jira
6. Save Credential: Click Save to create the credential. After saving, your Jira credential will be added to the credentials dashboard and will be ready to use in toolkit configurations. You can view, edit, or delete it from the Credentials menu at any time.

​

Step 2: Create Jira Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select Jira: Choose Jira from the list of available toolkit types.
4. Configure Toolkit Details:
   • Toolkit Name: Enter a descriptive name for your toolkit (e.g., “Jira Project Management”, “Development Team Jira”)
   • Description: Provide a brief description of the toolkit’s purpose (e.g., “Jira integration for automated issue tracking and project management”)
5. Configure Credentials:
   • In the Configuration section, select your previously created Jira credential from the Credentials dropdown
6. Configure Advanced Options:
   • PgVector Configuration: Select a PgVector connection for vector database integration
   • Embedding Model: Select an embedding model for text processing and semantic search capabilities
7. Configure Jira Settings:
   • Hosting Option: Select the appropriate hosting option:
     • Cloud: For Jira Cloud (e.g., atlassian.net)
     • Server: For self-hosted Jira Server or Data Center instances (e.g., https://jira.epam.com)
   • Advanced Settings:
     • Limit: Set the maximum number of issues to retrieve per request (default: 5)
     • API version: REST API version ( Currentl for jira cloud , you need to use 3 as api version, for Epam Jira version 2 )
     • Labels: Specify labels to apply to created or updated entities (comma-separated list e.g., alita,elitea)
     • Additional fields: Custom field IDs accessible within the toolkit (e.g., customfield_100450)
     • Custom Headers: Additional HTTP headers to include with API requests (JSON format e.g., {"X-Custom-Header": "value"})
     • Verify SSL: Enable SSL verification for secure connections (recommended: enabled)
8. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific Jira tools you want to enable. Enable only the tools your agents will actually use to follow the principle of least privilege
   • Make Tools Available by MCP - (optional checkbox) Enable this option to make the selected tools accessible through the external MCP clients to use the toolkit’s capabilities
9. Save Toolkit: Click Save to create the toolkit

​

Available Tools:

​

Testing Toolkit Tools

1. Select LLM Model: Choose a Large Language Model from the model dropdown in the Test Settings panel
2. Configure Model Settings: Adjust model parameters like Creativity, Max Completion Tokens, and other settings as needed
3. Select a Tool: Choose the specific Jira tool you want to test from the available tools
4. Provide Input: Enter any required parameters or test queries for the selected tool
5. Run the Test: Execute the tool and wait for the response
6. Review the Response: Analyze the output to verify the tool is working correctly and returning expected results

​

Step 3: Add Jira Toolkit to Your Workflows

​

In Agents:

1. Navigate to Agents: Open the sidebar and select Agents.
2. Create or Edit Agent: Either create a new agent or select an existing agent to edit.
3. Add Jira Toolkit:
   • In the “TOOLKITS” section of the agent configuration, click the “+Toolkit” icon
   • Select your configured Jira toolkit from the dropdown list
   • The toolkit will be added to your agent with the previously configured tools enabled

​

In Pipelines:

1. Navigate to Pipelines: Open the sidebar and select Pipelines.
2. Create or Edit Pipeline: Either create a new pipeline or select an existing pipeline to edit.
3. Add Jira Toolkit:
   • In the “TOOLKITS” section of the pipeline configuration, click the “+Toolkit” icon
   • Select your configured Jira toolkit from the dropdown list
   • The toolkit will be added to your pipeline with the previously configured tools enabled

​

In Chat:

1. Navigate to Chat: Open the sidebar and select Chat.
2. Start New Conversation: Click +Create or open an existing conversation.
3. Add Toolkit to Conversation:
   • In the chat Participants section, look for the Toolkits element
   • Click the “Add Tools” Icon to open the tools selection dropdown
   • Select your configured Jira toolkit from the dropdown list
   • The toolkit will be added to your conversation with all previously configured tools enabled
4. Use Toolkit in Chat: You can now directly interact with your Jira projects and issues by asking questions or requesting actions that will trigger the Jira toolkit tools.

​

Instructions and Prompts for Using the Jira Toolkit

​

Instruction Creation for Agents

• Direct and Action-Oriented: Employ strong action verbs and clear commands to initiate actions. For example, “Use the ‘search_using_jql’ tool…”, “Create an issue with…”, “Update issue with key…”.
• Parameter-Centric: Clearly enumerate each parameter required by the tool. For each parameter, specify:
  • Its name (exactly as expected by the tool)
  • The format or type of value expected
  • How the Agent should obtain the value – whether from user input, derived from previous steps in the conversation, retrieved from an external source, or a predefined static value
• Contextually Rich: Provide sufficient context so the Agent understands the overarching objective and the specific scenario in which each Jira tool should be applied within the broader workflow. Explain the desired outcome or goal for each tool invocation.
• Step-by-Step Structure: Organize instructions into a numbered or bulleted list of steps for complex workflows. This helps the Agent follow a logical sequence of actions.
• Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality. For example, “Conversation Starters: ‘Create a new bug issue’, ‘Search for issues assigned to me’, ‘What’s the status of project tasks?’”

1. State the Goal: Begin by clearly stating the objective you want to achieve with this step. For example, “Goal: To find all open issues assigned to the current user.”
2. Specify the Tool: Clearly indicate the specific Jira tool to be used for this step. For example, “Tool: Use the ‘search_using_jql’ tool.”
3. Define Parameters: Provide a detailed list of all parameters required by the selected tool. For each parameter:
   • Parameter Name: <Parameter Name as defined in tool documentation>
   • Value or Source: <Specify the value or how to obtain the value. Examples: "user input", "from previous step", "hardcoded value 'PROJECT-123'", "value of variable X">
4. Describe Expected Outcome (Optional but Recommended): Briefly describe the expected result or outcome after the tool is successfully executed. For example, “Outcome: The Agent will provide a list of all open issues assigned to the user.”
5. Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality.

1. Goal: Search for Jira issues using JQL to find specific issues based on user criteria.
2. Tool: Use the "search_using_jql" tool.
3. Parameters:
    - JQL Query: "Ask the user for search criteria or use predefined JQL like 'project = PROJECT AND status = \"In Progress\" AND assignee = currentUser()'"
4. Outcome: The Agent will provide a list of issues matching the JQL criteria.
5. Conversation Starters: 'Show me my open issues', 'Find all bugs in the project', 'Search for high priority tasks'

1. Goal: Create a new issue in Jira based on user requirements.
2. Tool: Use the "create_issue" tool.
3. Parameters:
    - Issue JSON: "Collect required information from user (summary, description, issue type, priority) and format as JSON"
4. Outcome: The Agent will create a new issue and provide the issue key and URL.
5. Conversation Starters: 'Create a new bug report', 'Add a task to the project', 'Report a new issue'

​

Chat Usage Examples by Tool Category

User: "Find all open bugs assigned to me in the DEMO project."

Agent Response: [Agent uses search_using_jql tool]

🔍 **JQL Search Results**:

**📋 Found 3 open bugs assigned to you**:

1. **DEMO-456** - "Login button not responsive on mobile"
   - **Status**: In Progress
   - **Priority**: High
   - **Assignee**: john.doe@company.com
   - **URL**: https://yourcompany.atlassian.net/browse/DEMO-456

2. **DEMO-789** - "Database connection timeout error"
   - **Status**: Open
   - **Priority**: Critical
   - **Assignee**: john.doe@company.com
   - **URL**: https://yourcompany.atlassian.net/browse/DEMO-789

Would you like me to get more details about any specific issue?

User: "Create a new bug report for the checkout process failing on Safari browser."

Agent Response: [Agent uses create_issue tool]

✅ **Issue Created Successfully!**

**🐛 New Bug Report Details**:
- **Issue Key**: DEMO-123
- **Summary**: "Checkout process failing on Safari browser"
- **Issue Type**: Bug
- **Priority**: High
- **Status**: Open
- **URL**: https://yourcompany.atlassian.net/browse/DEMO-123

**📝 Issue Description**:
Bug report for checkout process failure specifically occurring on Safari browser. Investigation needed to identify root cause and implement fix.

The issue is now ready for assignment and tracking!

User: "Add a comment to issue DEMO-123 saying that I've started investigating the Safari compatibility issue."

Agent Response: [Agent uses add_comments tool]

💬 **Comment Added Successfully!**

**Issue**: DEMO-123 - "Checkout process failing on Safari browser"
**Comment Added**: "Started investigating the Safari compatibility issue. Will check browser-specific JavaScript errors and CSS rendering differences."

You can view the updated issue at: https://yourcompany.atlassian.net/browse/DEMO-123

User: "Link issue DEMO-123 to DEMO-456 with 'Relates to' relationship."

Agent Response: [Agent uses link_issues tool]

🔗 **Issues Linked Successfully!**

**Link Created**:
- **Inward Issue**: DEMO-123 (Checkout process failing on Safari browser)
- **Outward Issue**: DEMO-456 (Login button not responsive on mobile)
- **Link Type**: Relates to

Both issues are now connected, showing their relationship in the issue view. This helps track related problems and their potential common solutions.

​

Troubleshooting

Limited Number of Issues Returned

Problem: When using JQL search or listing issues, the toolkit returns only a limited number of issues (e.g., not more than 5) even when more issues match the criteria.Symptoms:

• JQL searches return fewer results than expected
• Issue lists appear incomplete
• Large projects show only partial issue sets

Troubleshooting Steps:

1. Check Limit Configuration: In the toolkit configuration, locate the “Limit” field in the Advanced Settings section.
2. Increase Limit Value: Change the limit from the default value (typically 5) to a higher value that meets your needs (e.g., 50, 100, or 500).
3. Save Configuration: Save the toolkit configuration to apply the new limit.
4. Test Results: Run your JQL query or list operation again to verify more issues are returned.

Atlassian API Connection Issues (Too Many Redirects)

Error Message:

requests.exceptions.TooManyRedirects: Exceeded 30 redirects

Symptoms:

• Jira or Confluence tools refuse to connect
• Multiple redirect errors during connection attempts
• Some tools work while others fail (e.g., basic operations work but image-related tools fail)

Cause: The API version is set incorrectly or is null in the toolkit configuration. As of November 2025:

• Atlassian Cloud: API version 3
• EPAM Jira platform: API version 2

Troubleshooting Steps:

1. Check API Version: In the toolkit configuration, locate the “API version” field in the Advanced Settings section.
2. Set Correct Version: Update the API version to match your deployment:
   • For Atlassian Cloud instances: Set to 3
   • For EPAM Jira or self-hosted instances: Set to 2
3. Save Configuration: Save the toolkit configuration to apply the new API version.
4. Contact Support: If unsure about your deployment type, contact your system administrator or ELITEA support to confirm the correct API version.
5. Test Functionality: Note that some requests may work with both v2 and v3, so partial functionality doesn’t guarantee the configuration is correct. Test multiple tools to ensure full compatibility.

​

Support Contact

​

FAQ