Support & Ticketing

Jira Service Management Integration

Automated EV charging issue management for Jira Service Management — create issues from faults, manage workflows and link to OASIS HUB session data.

Activer Cette Extension Réserver une Démo

Le ProblèmeThe Problem

Pourquoi cette extension existe-t-elle ?

Engineering and operations teams at EV charging operators use Jira for issue tracking, but charging faults are reported manually — someone has to copy fault codes, session IDs and charger details into Jira by hand. This creates delays, missing context and no traceability between charging events and Jira issues.

La Solution

Ce que vous obtenez

Auto-create JSM issues from charging faults with fault code, charger ID and session ID
Issue lifecycle: create, update, transition and resolve issues via Jira REST API v3
Atlassian Document Format (ADF) support for rich descriptions and comments
Workflow transitions: move issues through custom workflows by transition name
Work log entries for time tracking on charging fault resolution
Customer management — driver profiles as JSM customer records
JQL search — query issues by session ID, charger ID or fault code
Atlassian API token authentication

🎯 Who is this for?

EV charging operators and CPOs using Jira Service Management for operations and technical support.

Activer Cette Extension Parcourir le Marketplace

🔌 Modular by design

Activez ou désactivez par tenant. Payez uniquement ce que vous utilisez. Toutes les extensions s'intègrent parfaitement.

Capacités Clés

Tout inclus

Fault-to-Issue Automation

Charging faults create JSM issues automatically with ADF-formatted descriptions including fault code, charger ID, session ID, location and driver info. Zero manual entry.

Workflow Transitions

Transition issues through custom JSM workflows by name — 'In Progress', 'Awaiting Parts', 'Done'. OASIS HUB can auto-resolve issues when faults clear.

Rich ADF Descriptions

All issue descriptions and comments use Atlassian Document Format — structured, readable content in Jira with proper headings, lists and code blocks.

Work Log Tracking

Log time spent on fault resolution directly from OASIS HUB. Full time tracking in Jira for SLA reporting and team capacity planning.

JQL Search

Search JSM issues by OASIS HUB session ID, charger ID or fault code using JQL. Find any issue from any charging event instantly.

API Token Auth

Atlassian API token authentication — configure your Jira base URL, email and API token. Enterprise-grade security with no OAuth redirect needed.

Cas d'Usage Réels

Voyez-le en action

Comment les opérateurs du monde entier utilisent cette extension pour résoudre des vrais problèmes et développer leur activité.

Charger fault creates JSM issue with full context

A charger reports a ground fault. OASIS HUB creates a JSM issue with fault code, charger ID, last session ID, location and affected driver — all in ADF format. Engineering team is assigned automatically.

Auto-resolve when fault clears

A charger comes back online after maintenance. OASIS HUB transitions the linked JSM issue to 'Done' automatically and adds a resolution comment with session restoration time.

SLA tracking for charging infrastructure

Operations team uses JSM SLA policies for charging faults. OASIS HUB creates issues with correct priority and labels — SLA clock starts immediately. Work logs track actual resolution time.

Étude de Cas

CPO achieves 99.2% fault traceability with Jira Service Management integration

A CPO with 500 chargers was losing track of fault resolution — issues created in Jira had no link to the original charging event. After enabling the JSM integration, every fault has a Jira issue with session ID, charger ID and fault code. Fault traceability improved from 61% to 99.2%.

99.2%

Fault traceability

-75%

Issue creation time

500

Chargers monitored

Manual Jira entries