Capabilities
| Feature | Description |
|---|---|
| Issue Sync | Import Jira issues to Products |
| AI Chat Integration | Manage Jira issues using natural language |
| Project Mapping | Link Jira projects to Products |
| Status Sync | Map Jira statuses to Kanban columns |
| Field Mapping | Sync standard and custom fields |
| Sprint Tracking | View sprint progress and velocity |
Kasava currently supports Jira Cloud only. Jira Server and Jira Data Center are not supported at this time.
Connecting Jira
What You Can Do Once Connected
After connecting Jira, you can:- Sync Jira issues to Products - Link Jira projects to Kasava Products for unified views
- Use AI chat for issue management - Create and update issues using natural language
- View issues in Kanban - See Jira issues organized by status
- Track sprints - View sprint progress alongside other work
Linking Jira to a Product
To sync Jira issues with a specific Kasava Product:Field Mapping
When issues sync between Jira and Kasava:| Jira Field | Kasava Field |
|---|---|
| Status | Kanban column |
| Assignee | Assignee |
| Labels | Labels |
| Priority | Priority |
| Sprint | Sprint |
| Story Points | Story points |
| Epic | Parent issue |
Issue Types
Jira issue types are preserved:| Jira Type | Display in Kasava |
|---|---|
| Story | Story |
| Bug | Bug |
| Task | Task |
| Epic | Epic |
| Sub-task | Sub-task |
Status Mapping
Jira workflow statuses map to Kanban columns based on status category:| Jira Status Category | Kanban Column |
|---|---|
| To Do | To Do |
| In Progress | In Progress |
| Done | Done |
Custom Workflows
For projects with custom Jira workflows, you can configure status mapping in Product settings:- Open Product settings
- Go to “Status Mapping”
- Map each Jira status to a Kasava column
- Save changes
Working with Sprints
Jira sprints sync with Kasava Products:- View active sprint progress - See what’s being worked on now
- Filter by sprint - Focus on specific sprint issues
- Track velocity - Monitor team throughput over time
Using Jira in AI Chat
Once connected, you can manage Jira issues using natural language in Kasava’s chat: Example commands:- “Create a Jira bug for the payment processing error”
- “Show me all open Jira issues in the current sprint”
- “What’s the status of the API redesign epic?”
- “Move PROJ-123 to In Progress”
@kasava Commands in Issues
Use@kasava mentions in Jira issue comments to trigger AI-powered actions directly from your workflow.
How It Works
- Add a comment on any Jira issue with
@kasavafollowed by a command - Kasava detects the mention via webhooks
- The AI processes your request using the issue context
- Results are posted as a reply comment on the issue
Available Commands
| Command | Description |
|---|---|
@kasava summarize | Summarize the issue discussion |
@kasava collapse | Collapse lengthy discussions into a summary |
@kasava archive | Archive discussion with a summary |
Command Arguments
Filter the analysis with natural language:Jira
@kasava commands currently support summarization-focused actions. Additional commands like plan, design-doc, and others are available on GitHub, Linear, and Asana integrations.Authorization
Jira workspace members in your Kasava organization can use commands. The user adding the comment must have access to the issue.Managing the Connection
To manage your Jira connection:
From the management dialog, you can:
- View connection status
- See the connected Atlassian site
- Disconnect the integration
Disconnecting Jira
Disconnecting Jira removes Kasava’s access to your Jira site. Any linked Products will no longer sync with Jira projects. Your Jira data is not deleted.
Troubleshooting
Project not appearing in the list
Project not appearing in the list
Ensure you have access to the project in Jira. Check that your Atlassian OAuth token is still valid. Try disconnecting and reconnecting the integration.
Issues not syncing to my Product
Issues not syncing to my Product
Verify that the Jira project is linked to your Product in Product settings. Check that the sync is enabled and the connection shows as active.
OAuth authorization failed
OAuth authorization failed
Status changes not reflecting
Status changes not reflecting
Some Jira workflows have required fields or conditions for status transitions. If a transition fails, check the workflow requirements in Jira.
Permissions
Kasava requests these Jira permissions during OAuth:| Permission | Purpose |
|---|---|
| Read Jira work | View issues, projects, sprints, and boards |
| Write Jira work | Create and update issues |
| Read user information | Access user profiles for assignee mapping |
Security
- OAuth tokens are encrypted at rest
- Tokens are never exposed in the UI
- Disconnect anytime from Kasava or Atlassian’s settings
- No passwords stored