Jira Service Management Data Center
Portal self-service and agent-side knowledge capture for JSM Data Center.
CORA AI in the customer portal deflects tickets with grounded Confluence answers. The Article Generator helps agents turn resolved requests into KB articles your portal agent can search next time.
Also on Atlassian Cloud? CORA – AI Support Agent · Article Generator (Cloud)
Portal self-service
CORA AI in the customer portal with Confluence-backed answers in your branded experience.
1 / 4

Status at a glance
Customers ask for recent requests. CORA reads portal tickets and summarizes status.
2 / 4

Open requests in chat
Summaries, deadlines, and descriptions captured in chat, then opened as JSM requests.
3 / 4
From chat to ticket
When self-service is not enough, CORA walks customers through the right request type.
4 / 4
Customer portal
CORA AI for portal visitors: Confluence-backed self-service before agents take the ticket.
Portal chat (customers)
- Embedded in the JSM customer portal with the same login customers already use.
- Knowledge answers from Confluence with search, rerank, and citations.
- Create and manage service requests in natural language when self-service is not enough.
- Portal and service desk context validated server-side.
- Streaming chat with visible search and reasoning steps.
- Multilingual support for search and responses.
Turn resolved tickets into knowledge
Resolved tickets become reusable KB articles. Built for agents and KB owners in Jira, not for portal customers.
Knowledge loop
Two sides of one product
Portal chat reads the KB; Article Generator writes to it from resolved work, so the portal agent improves over time.
Resolved ticket → Article Generator → Confluence KB → Portal CORA AI chat
Article Generator
Agents draft Confluence KB pages from resolved issues. Preview before publish.
Agents and support staff
Article Generator
Publish KB drafts from resolved work. Preview before Confluence publish.
- Jira issue panel for agents. Generate drafts from resolved service requests only.
- Ticket-to-KB automation: structured how-to HTML from issue fields and comments, not generic web content.
- Preview title, labels, and body before one-click publish to a configured Confluence space.
- Privacy by design: customer PII excluded; optional source-request metadata is agent/issue fields only.
- Per-project article destinations: admins map each JSM project to a Confluence space.
- Same CORA stack as portal chat: plugin auth, self-hosted backend, Confluence write.
Built for agents; customer PII is excluded from generated content by default. Generation is available on resolved issues only.
Architecture at a glance
JSM plugin
Hosts chat UI and gateway to JSM APIs with signed user assertions.
CORA backend
Agent, Confluence retrieval, and LLM, typically self-hosted beside Jira.
Trust model
Permissions flow through Jira/JSM; admin config stays behind administrator roles.
Contact us
Share your JSM and Confluence versions, portal scope, and how you want to combine deflection and KB capture.