Jira Integration
What Is It For?
- Manages the REST connection between the portal and Jira (URL, user, API token)
- Supplies project, issue type, labels, and custom-field mapping for the classic Jira form (
/jira-issue) - Works with the Features flag when the Support provider is Jira
- Is independent of Support Packages
Who Uses It?
- Portal administrators: To set up and verify the Jira connection
- Support / ITSM teams: To ensure requests land in the right Jira project
Access
- Portal → Settings → Jira Integration (
/admin/portal-jira-config) - Stored as
JiraConfig(active portal scope) - Saved with Save and Deploy
bilgi
This page is connection + classic Jira form settings. Enabling the support module, Built-in vs Jira provider, and Built-in SLA/category fields are on Portal → Settings → Portal → Support. Operations: Support Tickets.
How Built-in and Jira work together
Features → enableJiraIntegration ──► JIRA can be selected as Support provider
└──► Portal may seed jira-issue (Support Request) page
Jira Integration (this page) ──► URL / auth / project / type / labels / custom fields
└──► Portal /jira-issue create + list
Support tab (supportEnabled) ──► Portal “Support” menu visible
supportProvider ──► Support menu target: /support-ticket (Built-in) or /jira-issue (Jira)
| Setting | Role |
|---|---|
Features → Jira Integration (enableJiraIntegration) | Required to select Jira provider; when off, provider falls back to Built-in |
| Support → Enable + Provider | Shows Support menu; sets target route |
| This page (JiraConfig) | Connection used by classic /jira-issue |
uyarı
There are two flows:
- Built-in Support (
/support-ticket): Tickets are stored in Apinizer and managed from Manager Support Tickets. - Portal Support menu → Jira (
/jira-issue): Users use the classic Jira form; the issue is created directly in Jira. No ApinizerSupportTicketis created on this path.
“Every ticket is always stored in Apinizer” is not true for the Jira menu redirect.
Integration Fields
| Field | Required | Description |
|---|---|---|
| Status | — | Active/Passive. “Connected” badge uses status === true and a filled URL; classic create does not hard-gate REST on status |
| Jira API Url | Yes | e.g. https://your-org.atlassian.net (no trailing /) |
| Description | May be marked required in UI | Admin note only; not sent to Jira |
| Username | Yes | Atlassian email |
| API Token | Yes | Basic Auth password |
| Project Key | Yes | Used by classic /jira-issue create |
| Issue Type | Yes | e.g. Task |
| Category Custom Field ID | No | Portal category → Jira custom field |
| API Product Custom Field ID | No | |
| API Product Endpoint Custom Field ID | No | |
Jira Label (labelList) | No | Add with Enter; remove from table |
Support-tab Support project key / Issue type / Status mapping are separate (Support Ticket API / mapping). When the navbar sends users to /jira-issue, this page’s Project Key / Issue Type apply in practice.
Setup Summary
- Create an Atlassian API token.
- Enable Features → Jira Integration.
- Save URL, user, token, Project Key, Issue Type here (Save and Deploy).
- On the Support tab, enable the module and select Jira Integration (or stay on Built-in).
- Verify the flow from the portal Support menu.
Custom field IDs: Atlassian Custom Fields.
Legacy Names
| Legacy | Current |
|---|---|
| Portal Jira Config | Settings → Jira Integration |
| Portal menu “Support Requests” | Support and/or seeded Support Request (jira-issue) |
Related Pages
- Support Tickets
- API Portal Settings (Features + Support)