- 방법 - JIRA Service Desk Server 에서 고객 포털 URL 커스터마이즈 하기
- 방법 - JIRA Service Desk 고객 일괄 생성하기
- 방법 - JIRA Service Desk 라이센스 입력하기
- 방법 - JIRA 와 Service Desk에서 Glossary 혹은 Canned Responses 구현하기
- 방법 - Service Desk 사용중지 혹은 제거하기
- 방법 - ServiceDesk 프로젝트 탐색 사이드바에서 지식베이스 항목 숨기기/제거하기
- 방법 - SLA 이름변경하기
- 방법 - 익명사용자를 위해 JIRA Service Desk에서 Knowledge Base 링크하기
- 방법 - 회사, 조직, 혹은 클라이언트에 의한 SLA 구현하기
What's the difference between JIRA Software and JIRA Service Desk?
JIRA Software is purpose built specifically for software teams. JIRA Software combines powerful developer tool integrations with the most important elements of agile development.
JIRA Service Desk is purpose built for your IT and service teams, providing them with everything they need out of the box for incident, change and problem management.
Each JIRA application (JIRA Software, JIRA Service Desk, JIRA Core) is built on the JIRA platform. The JIRA platform provides a set of base functionality that is shared across all JIRA applications, such as issues, workflows, search, email, and more. You can extend and modify this functionality via the integration points provided by the JIRA platform, including the JIRA REST APIs, webhooks, plugin modules, etc.
Who are agents in JIRA Service Desk?
Agents are users who help resolve customer requests, which appear as issues in JIRA Service Desk.
An agent consumes one JIRA Service Desk license.
Who are customers in JIRA Service Desk?
Customers are users who create requests through the customer portal or by email. Customers do not have access to the service desk project view used by JIRA administrators or JIRA Service Desk agents. Customers can:
Customers do not require a JIRA Service Desk license or JIRA user license, so you aren't limited to a certain number of customers who can create requests through your service desk.
What's agent-based pricing?
Let's define: Who's an agent and who's a customer?
An agent is anyone responding to an incoming ticket. You only pay for agent licenses, and nothing else.
A customer is anyone who submits a ticket to your service desk team. They can be employees, external end users, anyone who needs help from your team.
What can JIRA Software or JIRA Core users do in JIRA Service Desk if they do not have an agent license?
JIRA application users without a JIRA Service Desk license (e.g. JIRA Software developers) can assist your team of agents on issues by working in the unlicensed view of a service desk project.
These users can:
These users cannot:
Still have questions on how roles and licensing works? Read on.
Do I need JIRA Software?
While coupling JIRA Service Desk with JIRA Software is the best way to use JIRA Service Desk, it's not a deal breaker. You can use JIRA Service Desk as a standalone product.
Do I need to have the same number of JIRA Software and JIRA Service Desk licenses?
No, you do not need to have the same number of JIRA Software and JIRA Service Desk licenses. You can select and pay for what you need with each product.
Does JIRA Service Desk include a knowledge base?
JIRA Service Desk can be integrated with Confluence's knowledge base capabilities, so agents can create, view, and share knowledge articles directly from the service desk issue they're working on. The knowledge articles your team creates help customers find solutions before raising requests in the customer portal or help center.
Add Confluence to JIRA Service Desk and help your customers help themselves. KB articles are free to read through JIRA Service Desk. Only pay for Confluence users who author content or articles.
Do my customers need a Confluence license?
|JIRA Service Desk customers that consume knowledge base articles from the portal do not need a confluence license. Confluence licenses are only required for those who author knowledge base articles, such as agents and administrators.|
Can I extend my trial?
How can I customize my JIRA Service Desk?
|JIRA Service Desk comes with a customizable customer-facing site called the customer portal, where your customers submit and track requests. You can also set up custom request types and brand your portal. You can even create multiple service desks for a variety of teams. Learn more here.|