Jira
Your customers track every sprint, bug, and feature request in Jira. Askel connects to each customer's Jira Cloud instance once, then lets your product read issues, open tickets, and move work through board columns without any per-customer integration code on your end.
What you can do
Open and update issues in any project
Create, edit, and close Jira issues using project keys like PLAT-123 or BUG-456. Askel handles required-field validation and supports all standard issue types: Bug, Story, Task, Epic, and Sub-task.
Move issues through workflow transitions
Trigger named transitions such as Start Progress, Ready for Review, or Done rather than guessing status IDs. Askel fetches the available transitions for each issue before acting.
Read and write custom fields
Askel discovers the customer's custom fields at connect time, including Story Points, Sprint, Team, and any field ending in a numeric ID. High-confidence mappings are proposed automatically.
Query boards and sprints
List active and future sprints on any board, filter issues by sprint or assignee, and pull backlog counts. Useful for surfacing project health inside your product.
React to issue events via webhooks
Receive real-time notifications when an issue is created, transitioned, assigned, or commented on. Askel registers the webhook against the customer's instance and forwards events to your product.
Audit every read and write
Every Jira API call Askel makes is logged with the project key, issue key, payload, and response. Your team can inspect or replay any operation from the Askel dashboard.
Auto-filing support escalations as Jira issues
You sell a customer support platform to software teams. A new customer, Ridgeline Software, wants every ticket your platform marks as Escalated to appear automatically as a Jira bug in their PLAT project, assigned to the correct team based on the product area tag. Their engineers work entirely in Jira and do not want to log into another tool to triage customer-reported issues.
- 1
Connect once
Ridgeline's Jira admin generates an API token at id.atlassian.com, then pastes it along with their admin email into your product's settings page. Askel stores the credential and constructs the Basic auth header at request time.
- 2
Schema discovery
Askel reads Ridgeline's PLAT project: issue types, required fields, custom fields (including Product Area and Severity), and the full list of workflow transitions. A mapping draft appears within seconds.
- 3
Review the mapping
Your CS rep opens the mapping editor with Ridgeline on a call. The Product Area custom field (customfield_10042) maps to the product area tag from your platform, and Severity maps to your platform's priority levels.
- 4
Dry-run against recent tickets
Askel pulls the last 15 escalated tickets, runs the full mapping in read-only mode, and shows exactly which Jira issues would have been created, including how the Product Area field would be populated.
- 5
Go live
Activate the workflow. Every new Escalated ticket in your platform now creates a Bug in PLAT, pre-filled with the correct Product Area and Severity, and a comment linking back to the original support ticket.
Basic auth
Customer's Jira admin generates an API token at id.atlassian.com/manage-profile/security/api-tokens and pastes it into Askel along with the admin's email. Askel composes the Basic auth header at request time; the token never reaches your servers.
How Askel sits between your product and the customer's system
FAQ for Jira
Does this work with Jira Data Center or only Jira Cloud?+
What permissions does the API token need?+
What happens when a customer renames a custom field or removes a workflow transition?+
Can we scope the integration to specific Jira projects rather than the whole instance?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.