Jira Agent
Connect Junet to your Atlassian Jira instance to query projects, issues, and boards
Overview
The Jira Agent allows you to interact with your Atlassian Jira projects directly from the Junet chat interface. You can query projects, search for issues, view boards, and get real-time information about your work items.
Prerequisites
Before you begin, make sure you have:
- Jira Cloud or Server instance with administrator access
- Atlassian account with permission to create API tokens
- Your Atlassian Base URL (e.g.,
https://your-company.atlassian.net)
Step 1: Generate an Atlassian API Token
- Go to Atlassian Account Settings
- Log in with your Atlassian account
- Click Create API token
- Enter a label for your token (e.g., "Junet Integration")
- Click Create
- Copy the token immediately - you won't be able to see it again
Store your API token securely. Anyone with this token can access your Jira data.
Step 2: Enable the Jira Agent
- Open Junet and navigate to the chat interface
- Click on the Agent Settings icon (puzzle piece) in the top navigation
- Find Jira in the list of available agents
- Toggle the switch to Enabled
Step 3: Add a Jira Connection
- In the Jira Agent settings, click Add Connection
- Fill in the connection details:
Connection Name
Enter a descriptive name for this connection (e.g., "Company Jira" or "Development Team")
This name appears in chat results, so choose something recognizable.
Description (Optional)
Add a description to help users understand what this connection is for (e.g., "Main company Jira for all development projects")
Atlassian Base URL
Enter your Jira instance URL:
https://your-company.atlassian.net
Do not include trailing slashes or paths like /jira - just the base domain.
Atlassian Username
Enter the email address associated with your Atlassian account:
user@company.com
Atlassian API Key
Paste the API token you generated in Step 1.
Step 4: Configure User Groups (Optional)
If you want to restrict access to specific user groups:
- Click the User Groups dropdown
- Select one or more groups that should have access to this connection
- Leave empty to allow all users
Step 5: Configuration Options
Set as Default
Enable this option if you want this connection to be used by default when multiple Jira connections exist.
Enabled
Make sure this toggle is ON to activate the connection.
Step 6: Save and Test
- Click Create Connection
- The connection will be validated automatically
- If successful, you'll see a confirmation message
- The connection now appears in the list with status Enabled
Using the Jira Agent
Once configured, you can ask questions like:
- "Show me all open issues in project ABC"
- "What are the high priority bugs assigned to me?"
- "List all projects in Jira"
- "Show sprint board for project XYZ"
- "Find issues created this week"
- "What's the status of PROJ-123?"
The agent will search your connected Jira instance and return relevant information.
Managing Multiple Connections
You can add multiple Jira connections for different instances or teams:
- Click Add Connection again
- Configure each connection with unique credentials
- Use Set as Default to choose which connection is primary
- The agent will indicate which connection was used for each query
Troubleshooting
Authentication Failed
Problem: "Unable to authenticate with Atlassian"
Solutions:
- Verify your email address is correct
- Regenerate your API token and update the connection
- Check that your account has access to the Jira instance
- Ensure the Base URL is correct (no trailing slash)
No Results Found
Problem: Queries return no results
Solutions:
- Verify the project key or issue ID exists
- Check your Jira permissions - you can only see what you have access to
- Try a broader search query
- Ensure the connection is set to Enabled
Connection Timeout
Problem: "Request timed out"
Solutions:
- Check your internet connection
- Verify the Atlassian Base URL is accessible
- Try again in a few minutes - the Atlassian API may be temporarily unavailable
- Check if your organization has firewall rules blocking the connection
Wrong Connection Used
Problem: Agent uses the wrong Jira instance
Solutions:
- Check which connection is set as Default
- Specify the connection name in your query (if supported)
- Disable connections you're not currently using
Security Best Practices
Rotate API Tokens Regularly
- Generate a new API token every 90 days
- Update all connections using the old token
- Revoke the old token in Atlassian settings
Limit User Access
- Use User Groups to restrict sensitive Jira connections
- Create separate connections for different teams or departments
- Regularly audit who has access to each connection
Monitor Usage
- Check the Jira Agent logs for unusual activity
- Review API token usage in Atlassian settings
- Disable unused connections
Permissions
The Jira Agent respects your Jira permissions:
- You can only query projects you have access to
- Issue visibility follows your Jira security schemes
- Sensitive fields are only shown if you have permission
API Rate Limits
Atlassian enforces rate limits on API requests:
- Jira Cloud: ~300 requests per minute per user
- Jira Server: Depends on your configuration
If you hit rate limits, the agent will notify you. Wait a few minutes before trying again.
Data Privacy
- API tokens are stored encrypted in the Junet database
- No Jira data is cached permanently
- Query results are only visible to the user who made the request
- Jira data is fetched in real-time for each query
Updating a Connection
To modify an existing connection:
- Click the Edit icon next to the connection
- Update any fields (URL, username, API key, etc.)
- Click Save
- The connection will be re-validated
Deleting a Connection
To remove a connection:
- Click the Delete icon next to the connection
- Confirm the deletion
- The connection and its configuration are permanently removed
Deleting a connection cannot be undone. You'll need to reconfigure from scratch.
Support
If you encounter issues not covered in this guide:
- Contact your Junet administrator
- Check the Atlassian API documentation
- Review Jira Agent logs for error details