Page tree
Skip to end of metadata
Go to start of metadata


Each service desk you create with JIRA Service Desk is based on a JIRA project. If you have multiple teams within your business that respond to different types of requests, you'll likely want to manage these in separate projects (for example, an IT project, an office & supplies project, etc.). Each service desk can be designed to meet the specific needs for both the service desk team who manages the requests and the customers who make them.

For information on setting up JIRA users to use JIRA Service Desk, see How JIRA and JIRA Service Desk Work Together.


When you set up a service desk, you can either:

  • 새로운 service desk 프로젝트 생성 - This option is ideal if you have new internal processes that need to be managed through a central tool. JIRA Service Desk will create all the basic components of the service desk: a template Customer Portal, generic SLAs, and basic reports. JIRA Service Desk also provides the underlying JIRA features optimized for IT service desk requests: a workflow, fields, and issue types. All you need to do is customize them to meet your needs!
  • 기존 JIRA 프로젝트에 대한 service desk 생성 - This option is ideal if you've already been using JIRA in a help desk capacity (for example, to fill IT requests, etc.). When you create a service desk for an existing project, JIRA Service Desk uses the workflow, fields, permissions, and issue types you already have set up on the project as a basis for the flow of requests in the service desk.

JIRA Service Desk 에서 JIRA 프로젝트와 동작하는 방법

JIRA Service Desk lets you put the power of JIRA into the hands of your support agents (for example, by allowing them to move requests through complex workflows). However, the Customer Portal lets you present a simpler experience to your customers. In other words, customer portals let you map the components of JIRA to the information your customers will see and understand.

Each JIRA Service Desk project is based on a JIRA project. The request types within a service desk are based on JIRA issue types.


You use the Customer Portal screen to map request types to issue types and to customize how request types appear for customers. You also use this screen to add new request types or remove ones you don't need. For more information on designing a Customer Portal, see How JIRA and JIRA Service Desk Work Together

The workflows and fields associated with an issue type can also be customized on the Customer Portal. See Customizing the fields on a request type and Customizing the workflow status for a request type for more information. 


  • No labels