Jira Service Management and Atlassian Service Collection

Jira Service Desk, Jira Service Management and Service Collection: understanding the evolution

The product formerly known as Jira Service Desk became Jira Service Management. In Cloud, the offer is now presented within Atlassian Service Collection, which brings together Jira Service Management, Customer Service Management, Assets and Rovo.

For an organization, the key point is to understand what the offer actually covers: service portal, ITSM processes, customer support, Assets repositories, AI assistance with Rovo, licensing, agents and operational governance.

Portal, requests, queues and SLAs

Ovyka configures portals, forms, request catalogues, queues, automations, SLAs, notifications and reports so agents and requesters work in a clear operating model.

• request catalogues and forms
• queues and automations
• SLAs, reporting and satisfaction measurement
• Confluence knowledge base

ITSM: incidents, changes, problems, requests and knowledge base

ITSM practices require understandable workflows, controlled roles, realistic SLAs, useful knowledge content and actionable reports. Ovyka helps structure these processes without overcomplicating the instance.

• incident management
• change management
• problem management
• request management and knowledge base

Service Collection: what is now included with JSM

Atlassian Service Collection frames the Cloud service management offer with Jira Service Management, Customer Service Management, Assets and Rovo. Ovyka helps you understand the useful scope, licenses, agents, customers and capabilities to activate at the right time.

• Jira Service Management for portals and ITSM processes
• Customer Service Management for customer support
• Assets for CMDB, equipment and services
• Rovo for AI assistance, search and service agents

Customer Service Management for customer support teams

Customer Service Management is aimed at teams handling customer requests, with needs around tracking, prioritization, visibility and service quality. Ovyka positions it with JSM to avoid separated models that complicate collaboration between support, IT and delivery.

Assets for CMDB, equipment and services

Assets structures the objects, services, equipment, dependencies or repositories needed for service management. Success depends on the data model, responsibilities and the level of detail that can actually be maintained.

• CMDB and service repositories
• equipment, applications and relationships
• data model and governance
• links with requests, incidents and changes

Rovo for AI assistance, search and service agents

Rovo can help find information, assist agents and accelerate some service paths. Ovyka recommends activating it progressively, with knowledge, permissions and data clean enough for AI to remain useful and governed.

Licenses, agents, customers and billing model

Commercial scoping must distinguish agents, customers, roles, license level, apps and capabilities that are actually useful. Ovyka helps arbitrate without oversizing the instance or losing operational needs.

• requirements framing and licensing choices
• configuration and administration practices
• user and administrator training
• recurring support and TMA (third-party application maintenance)

Migration, rationalization and continuous improvement

Ovyka can take over an existing Jira Service Desk or Jira Service Management instance, clean up portals, review workflows, secure Cloud migration, document operations and set up recurring support.