Leon → Export via GraphQL
We read Leon data in a structured and efficient manner:
- Quote Requests
- Flight Requests
- Legs
- Changes & Status Changes
- Metadata
All data are uniquely identified and prepared for further processing.
Solutions
Leon ↔ Jira Integration — Flight Communications without double entry
Flight Communications — automated, structured, traceable
Airlines, AOCs and charter companies process a broad range of information from Leon every day: Flight Requests, Legs, Operational Changes, Timings and customer communication. This data must be transferred reliably, quickly and traceably into the operational workflows of Sales, Dispatch and Management.
This is precisely where Arkcanis’ Leon ↔ Jira integration comes in.
We connect Leon and Jira into an end‑to‑end flight processing workflow: structured, traceable and automated for the data we transfer. The transfer runs from Leon into Jira; writing back into Leon is set up for agreed fields after we have discussed it.
The data is pulled in short, fixed intervals — every two minutes in the standard configuration. A new flight request therefore appears in Jira while it is still being worked on in Leon. Existing issues are recognised by their identifier and updated rather than created a second time.
Leon remains your operational core system – Jira becomes the clear interface for daily work.
Functions at a Glance
- Export from Leon via GraphQL
- Automatic import into Jira (Issues + Leg subtasks)
- Pull in fixed intervals, matched by unique identifiers
- Intelligent mapping & duplicate prevention
- Complete history & auditability
- Automatic archiving
- Integration-ready for ETL, Leon2DB & dashboards
Where AOCs reach their limits today
Many AOCs still work with manual exports, Excel lists or scattered communication channels. The consequences:
- Non-transparent Flight Ops data
- Multiple data entry & error susceptibility
- Process breaks between Sales, Dispatch and Management
- Missing real-time updates on changes
- No unified “single source of truth”
- Unstructured communication with customers and internal departments
How the integration works
ETL, Mapping & Normalization
The data is automatically validated, cleansed, and processed incrementally.
Highlights:
- Repeated pull instead of a full import, bounded by the time window
- Duplicate prevention
- Consistent state management
- History & change tracking
Automatic import to Jira
Each flight request becomes a Jira issue, each leg a subtask.
Changes are synchronized automatically.
- Issue structures aligned with your process
- Comments, notes & updates are transferred
- Responsibilities clearly mapped
- No duplicate entry of the Leon data we transfer
Automatic Archiving of Closed Cases
Completed flights are archived automatically – including history, subtasks, and metadata.
Result: Jira stays clear and high-performing, and every transferred change is recorded in the issue.
Your added value – operational & strategic
Flight Ops
- Every leg visible on the same cycle, without manual export
- Reduced manual work
- Clear workflows & accountabilities
Sales & Charter
- Immediate visibility of new inquiries
- Trackable customer communication
- Faster quoting processes
Management
- Every transfer logged on the issue
- KPIs & reporting
- Stable end-to-end process management
Working together and scope of services
The integration works with Jira Cloud; it is not designed for Jira Data Center. We need a Leon account with API permissions, your Jira Cloud environment and a contact from flight ops who knows what the fields mean operationally. From that we derive the objects to transfer, the field mapping and the issue structure in Jira.
The transfer runs from Leon into Jira. Writing back into Leon is possible and is set up separately for the agreed fields — it is not part of the standard scope.
You receive the working integration, the field mapping as a document and a description of the archiving rules. Acceptance runs against real issues from your operation.
Setup, adjustments and ongoing services are listed separately in the proposal.
Not included: running the target environment on your side, changes to the flight operations system itself, and your Leon and Jira licences. Who operates the integration afterwards, and who follows up on changes in Leon or Jira, is agreed in advance.
Which data from Leon is actually needed, and how it can be analysed, is settled in Leon Engineering.
Let's talk about your project.
Tell us briefly what it is about – we will get back to you.