The backoffice Jira integration interacts with BOSD Jira project.
This page lists the mappings between Jira object and backoffice ticket.
Common settings
Backoffice ticket | Jira Object | Description |
|---|---|---|
Service Desk | serviceDeskId = "6" | fixed, no need to provide |
Request Type | requestType.id = "124" | a fixed value for backoffice service desk, no need to provide (any input will be ignored) |
“customfield_10131”: { | Currently it’s two level structure, for example: Onboarding Query → Selfie / Photo. Open left link to get more types. | |
Customer ID | customfield_10128 | customer id |
Customer Channel | customfield_10132 | customer channel |
Customer Type | customfield_10133 | customer type |
Product Type | customfield_10134 | product type |
Responsible Team | customfield_10135 | responsible team for this ticket |
Interaction ID | customfield_10129 | interaction id |
Model details
TicketCreateDto (property with * is required)
Json | Type | Value | Desc |
projectKey* | string | “BOSD” | Backoffice project key (a fixed value) |
issueTypeName* | string | id = 10026 | Issue type of backoffice, fixed value. |
requestTypeName* | string | id = 124 | Request type of backoffice, fixed value. |
boRequestTypeOrderedList* | [string] | The backoffice request type, has a parent-child structure | |
summary* | string | The summary of a service request | |
description* | string | The description of a service request | |
customerId* | string | The customer id | |
customerChannel* | string | The customer channel | |
customerType* | string | The customer type | |
productType* | string | The product type | |
interactionId | string (Optional) | The interaction id | |
reporterId | string (Optional) | The reporter (Jira) account id | |
priority | string (Optional) | The priority |