시작
Kore.ai 대화형 플랫폼
챗봇 개요
자연어 처리(NLP)
봇 개념 및 용어들
빠른 시작 가이드
봇 빌더 접근 방법
사용 고지 사항 (영어)
Kore.ai 봇 빌더로 작업하기
봇 구축 시작하기
릴리스 정보
현재 버전 (영어)
이전 버전 (영어)

개념
디자인
스토리보드
대화 작업
개요
Using the Dialog Builder Tool
노드 유형
사용자 의도 노드
대화 노드
엔티티 노드
양식 노드
확인 노드
서비스 노드
봇 조치 노드
Service Node
WebHook 노드
스크립트 노드
노드 그룹화하기
Agent Transfer Node
사용자 프롬프트
음성 통화 속성
대화 관리
노드 및 전환
구성 요소 전환
컨텍스트 개체
이벤트 기반 봇 조치
지식 그래프
소개
지식 추출
지식 그래프 생성
봇에 지식 그래프 추가
그래프 생성
지식 그래프 작성
FAQ 추가
작업 실행
기존 소스에서 FAQ 구축
특성, 동의어 및 불용어
변수 네임스페이스 관리
수정
용어 편집 및 삭제
용어 편집 및 삭제
질문과 응답 편집
Knowledge Graph Training
지식 그래프 분석
봇 온톨로지 가져오기 및 내보내기
지식 그래프 가져오기
지식 그래프 내보내기
지식 그래프 생성
CSV 파일에서
JSON 파일
지식 그래프 생성
경고 작업
스몰 토크
Digital Skills
디지털 양식
Views
Digital Views
Panels
Widgets
기차
봇 성능 향상 – NLP 최적화
기계 학습
소개
모델 검증
기초 의미
지식 그래프 학습
특성
순위 및 해결
고급 NLP 설정
NLP 설정 및 지침
봇 인텔리전스
소개
컨텍스트 관리
컨텍스트 관리
대화 관리
다중 – 의도 탐지
엔티티 수정
기본 대화
정서 관리
어조 분석
Test & Debug
봇과 대화
발화 테스트
배치 테스트하기
대화 테스트
배포
채널 활성화
봇 게시
분석
봇 분석하기
Conversations Dashboard
Performance Dashboard
사용자 정의 대시보드
소개
맞춤형 메타 태그
사용자 정의 대시보드 생성 방법
Conversation Flows
NLP 지표
Containment Metrics
사용량 지표
스마트 봇
소개
범용 봇
소개
범용 봇 정의
범용 봇 생성
범용 봇 학습
범용 봇 커스터마이징
범용 봇용 추가 언어 활성화
스토어
Manage Assistant
플랜 및 사용량
Overview
Usage Plans
Support Plans
플랜 관리
봇 인증
다국어 봇
개인 식별 정보 삭제하기
봇 변수 사용
IVR 통합
일반 설정
봇 관리

방법
간단한 봇 생성하기
Design Conversation Skills
뱅킹 봇 생성
뱅킹 봇 – 자금 이체
뱅킹 봇 – 잔액 업데이트
Knowledge Graph (KG) 구축
스마트 경고를 예약하는 방법
Design Digital Skills
디지털 양식 설정 방법
디지털 보기 설정 방법
데이터 테이블에 데이터를 추가하는 방법
데이터 테이블 내 데이터 업데이트 방법
UI 양식에서 데이터 테이블에 데이터를 추가하는 방법
Train the Assistant
특성 사용 방법
의도와 엔티티에 대한 패턴 사용 방법
컨텍스트 전환 관리 방법
Deploy the Assistant
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼
Analyze the Assistant
사용자 정의 대시보드 생성 방법
사용자 지정 태그를 사용하여 봇 메트릭을 필터링하는 방법

API 및 SDK
API 참조
Kore.ai API 사용
API 목록
API 컬렉션
koreUtil Libraries
SDK 참조
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
소개
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼

관리
소개
봇 관리자 콘솔
대시보드
사용자 관리
사용자 관리
그룹 관리
역할 관리
봇 관리 모듈
등록
사용자 초대
사용자 등록을 위한 대량 초대 보내기
사용자 및 사용자 데이터 가져오기
Active Directory에서 사용자 동기화
보안 및 준수
싱글 사인 온 사용
보안 설정
Kore.ai 커넥터
봇 관리자용 분석
Billing (지원하지 않음)
  1. Integrations
  2. Using the JIRA Action Templates

Using the JIRA Action Templates

You can use the Prebuilt Action Templates from your JIRA integration to auto-create dialog tasks and test them using the Talk to Bot option.

Step to create a dialog task using the JIRA action templates:

  1. Go to Build > Conversation Skills > Dialog Tasks.
  2. Click Create a Dialog Task.
  3. On the Dialog Task pop-up, under the Integration, select the Jira option to view the action templates.
  4. If you have not configured any integration for your virtual assistant, you will see the Explore Integrations option. Once you click this option, you will be redirected to the Actions page to configure an integration for your VA. For more information, see Actions Overview.

JIRA Actions

The following Freshdesk actions are supported in this release:

Supported Tasks Description Method
Create an Issue Creates an issue in the JIRA system. POST
Get an Issue by ID Fetch an issue details with ID from the JIRA system. GET
Get all issues Retrieves all issues from the JIRA system. GET
Update an Issue Updates an issue in the JIRA system. PUT
Delete an issue Deletes an issue from the JIRA system. GET

Create an Issue

Steps to create an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Create an issue dialog task is added with the following components:
    • createIssue – A user intent to create an issue.
    • projectKey, summary, and issueTypeName – Entity nodes for creating the issue in the JIRA system.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • createIssueService – A bot action service to create an issue in an external integration. Click the Plus icon to expand to view the createIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:

      Sample Request:

      {
      "fields": {
      "summary": "messaging module is not working",
      "issuetype": {
      "name": "Bug"
      },
      "project": {
      "key": "DFJIIP"
      }
      }
      }

      To add one or more responses, scroll down and click the +Add Response button:
      Sample Response:

      {
      "id": "10000",
      "key": "ED-24",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10000",
      "transition": {
      "status": 200,
      "errorCollection": {
      "errorMessages": [],
      "errors": {}
      }
    • createdIssueInfoService – A bot action service to gather more details about an issue in an external integration. Click the Plus icon to expand to view the createdIssueInfoService bot action component properties.
    • createIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to create an issue as shown below:

Get an Issue by Key

Steps to find an issue using the key in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Get Issues by Key dialog task is added with the following components:
    • getIssuebyKey – A user intent to find an issue by key.
    • issueKey – Entity nodes for gathering the required issue details.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • getIssuebyKeyService – A bot action service to find an issue in an external integration. Click the Plus icon to expand to view the getIssuebyKeyService bot action component properties.
    • In the Component Properties window, to add one or more responses, scroll down and click +Add Response:

      Sample Response:

      {
      {
      "id": "10002",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "inwardIssue": {
      "id": "10004",
      "key": "PR-3",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-3",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "worklog": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/worklog/10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "comment": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "I did some work here."
      }
      ] }
      ] },
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "group",
      "value": "jira-developers",
      "identifier": "276f955c-63d7-42c8-9520-92d01dca0625"
      },
      "started": "2021-01-17T12:34:00.000+0000",
      "timeSpent": "3h 20m",
      "timeSpentSeconds": 12000,
      "id": "100028",
      "issueId": "10002"
      }
      ],
      "updated": 1,
      "timetracking": {
      "originalEstimate": "10m",
      "remainingEstimate": "3m",
      "timeSpent": "6m",
      "originalEstimateSeconds": 600,
      "remainingEstimateSeconds": 200,
      "timeSpentSeconds": 400
      }
      }
      }

    • getIssuebyKeyMessage – A message node with script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to find an issue by key as shown below:

Get All Issues

Steps to view all issues in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Get All Issues dialog task is added with the following components:
    • getAllIssues – A user intent to view all issues.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • getAllIssuesService – A bot action service to fetch all issues
      from an external integration. Click the Plus icon to expand to view the getAllIssuesService bot action component properties.
    • In the Component Properties window, to add one or more responses, scroll down and click +Add Response.

      Sample Response:

      {
      "expand": "names,schema",
      "startAt": 0,
      "maxResults": 50,
      "total": 1,
      "issues": [
      {
      "expand": "",
      "id": "10002",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10002",
      "key": "ED-1",
      "fields": {
      "watcher": {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/EX-1/watchers",
      "isWatching": false,
      "watchCount": 1,
      "watchers": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      }
      ] },
      "attachment": [
      {
      "id": 10000,
      "self": "https://your-domain.atlassian.net/rest/api/3/attachments/10000",
      "filename": "picture.jpg",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "key": "",
      "accountId": "5b10a2844c20165700ede21g",
      "accountType": "atlassian",
      "name": "",
      "avatarUrls": {
      "48x48": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=48&s=48",
      "24x24": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=24&s=24",
      "16x16": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=16&s=16",
      "32x32": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=32&s=32"
      },
      "displayName": "Mia Krystof",
      "active": false
      },
      "created": "2023-02-28T09:45:11.830+0000",
      "size": 23123,
      "mimeType": "image/jpeg",
      "content": "https://your-domain.atlassian.net/jira/rest/api/3/attachment/content/10000",
      "thumbnail": "https://your-domain.atlassian.net/jira/rest/api/3/attachment/thumbnail/10000"
      }
      ],
      "sub-tasks": [
      {
      "id": "10000",
      "type": {
      "id": "10000",
      "name": "",
      "inward": "Parent",
      "outward": "Sub-task"
      },
      "outwardIssue": {
      "id": "10003",
      "key": "ED-2",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/ED-2",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "description": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Main order flow broken"
      }
      ] }
      ] },
      "project": {
      "self": "https://your-domain.atlassian.net/rest/api/3/project/EX",
      "id": "10000",
      "key": "EX",
      "name": "Example",
      "avatarUrls": {
      "48x48": "https://your-domain.atlassian.net/secure/projectavatar?size=large&pid=10000",
      "24x24": "https://your-domain.atlassian.net/secure/projectavatar?size=small&pid=10000",
      "16x16": "https://your-domain.atlassian.net/secure/projectavatar?size=xsmall&pid=10000",
      "32x32": "https://your-domain.atlassian.net/secure/projectavatar?size=medium&pid=10000"
      },
      "projectCategory": {
      "self": "https://your-domain.atlassian.net/rest/api/3/projectCategory/10000",
      "id": "10000",
      "name": "FIRST",
      "description": "First Project Category"
      },
      "simplified": false,
      "style": "classic",
      "insight": {
      "totalIssueCount": 100,
      "lastIssueUpdateTime": "2023-02-28T09:45:09.984+0000"
      }
      },
      "comment": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/comment/10000",
      "id": "10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "body": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
      }
      ] }
      ] },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "created": "2021-01-17T12:34:00.000+0000",
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "role",
      "value": "Administrators",
      "identifier": "Administrators"
      }
      }
      ],
      "issuelinks": [
      {
      "id": "10001",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "outwardIssue": {
      "id": "10004L",
      "key": "PR-2",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-2",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      },
      {
      "id": "10002",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "inwardIssue": {
      "id": "10004",
      "key": "PR-3",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-3",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "worklog": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/worklog/10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "comment": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "I did some work here."
      }
      ] }
      ] },
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "group",
      "value": "jira-developers",
      "identifier": "276f955c-63d7-42c8-9520-92d01dca0625"
      },
      "started": "2021-01-17T12:34:00.000+0000",
      "timeSpent": "3h 20m",
      "timeSpentSeconds": 12000,
      "id": "100028",
      "issueId": "10002"
      }
      ],
      "updated": 1,
      "timetracking": {
      "originalEstimate": "10m",
      "remainingEstimate": "3m",
      "timeSpent": "6m",
      "originalEstimateSeconds": 600,
      "remainingEstimateSeconds": 200,
      "timeSpentSeconds": 400
      }
      }
      }
      ],
      "warningMessages": [
      "The value 'bar' does not exist for the field 'foo'."
      ] }
    • getAllIssuesMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to view all issues as shown below:

Update an Issue

Steps to update an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Update an Issue dialog task is added with the following components:
    • updateIssue – A user intent to update an issue.
    • issueKey, chooseField, updatedSummary, and newLabel – Entity nodes for updating the issue details.
    • prepareUpdateIssuePayloadScript – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the prepareUpdateIssuePayloadScript bot action component properties.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • updateIssueService – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the updateIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:

      Sample Request:

      {
      "update": {
      "summary": [
      {
      "set": "The updated summary"
      }
      ],
      "labels": {
      "add": "Label_to_add_without_space"
      }
      }
      }
    • getIssuebyKeyService – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the getIssuebyKeyService bot action component properties.
    • updateIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to update an issue as shown below:

Delete an Issue

Note: You can delete an issue only if the JIRA admin or owner of the JIRA project assigns you the permission to delete it. Otherwise, you will not be able to perform this action.

Steps to delete an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Delete an Issue dialog task is added with the following components:
    • deleteIssue – A user intent to delete an issue.
    • issueKey – Entity node to gather key to delete an issue.
    • getResourceIdService – A bot action service to delete a resource ID for an issue in an external integration.
    • deleteIssueService – A bot action service to delete an issue in an external integration. Click the Plus icon to expand to view the deleteIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:
    • deleteIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to delete an issue.

Using the JIRA Action Templates

You can use the Prebuilt Action Templates from your JIRA integration to auto-create dialog tasks and test them using the Talk to Bot option.

Step to create a dialog task using the JIRA action templates:

  1. Go to Build > Conversation Skills > Dialog Tasks.
  2. Click Create a Dialog Task.
  3. On the Dialog Task pop-up, under the Integration, select the Jira option to view the action templates.
  4. If you have not configured any integration for your virtual assistant, you will see the Explore Integrations option. Once you click this option, you will be redirected to the Actions page to configure an integration for your VA. For more information, see Actions Overview.

JIRA Actions

The following Freshdesk actions are supported in this release:

Supported Tasks Description Method
Create an Issue Creates an issue in the JIRA system. POST
Get an Issue by ID Fetch an issue details with ID from the JIRA system. GET
Get all issues Retrieves all issues from the JIRA system. GET
Update an Issue Updates an issue in the JIRA system. PUT
Delete an issue Deletes an issue from the JIRA system. GET

Create an Issue

Steps to create an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Create an issue dialog task is added with the following components:
    • createIssue – A user intent to create an issue.
    • projectKey, summary, and issueTypeName – Entity nodes for creating the issue in the JIRA system.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • createIssueService – A bot action service to create an issue in an external integration. Click the Plus icon to expand to view the createIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:

      Sample Request:

      {
      "fields": {
      "summary": "messaging module is not working",
      "issuetype": {
      "name": "Bug"
      },
      "project": {
      "key": "DFJIIP"
      }
      }
      }

      To add one or more responses, scroll down and click the +Add Response button:
      Sample Response:

      {
      "id": "10000",
      "key": "ED-24",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10000",
      "transition": {
      "status": 200,
      "errorCollection": {
      "errorMessages": [],
      "errors": {}
      }
    • createdIssueInfoService – A bot action service to gather more details about an issue in an external integration. Click the Plus icon to expand to view the createdIssueInfoService bot action component properties.
    • createIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to create an issue as shown below:

Get an Issue by Key

Steps to find an issue using the key in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Get Issues by Key dialog task is added with the following components:
    • getIssuebyKey – A user intent to find an issue by key.
    • issueKey – Entity nodes for gathering the required issue details.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • getIssuebyKeyService – A bot action service to find an issue in an external integration. Click the Plus icon to expand to view the getIssuebyKeyService bot action component properties.
    • In the Component Properties window, to add one or more responses, scroll down and click +Add Response:

      Sample Response:

      {
      {
      "id": "10002",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "inwardIssue": {
      "id": "10004",
      "key": "PR-3",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-3",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "worklog": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/worklog/10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "comment": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "I did some work here."
      }
      ] }
      ] },
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "group",
      "value": "jira-developers",
      "identifier": "276f955c-63d7-42c8-9520-92d01dca0625"
      },
      "started": "2021-01-17T12:34:00.000+0000",
      "timeSpent": "3h 20m",
      "timeSpentSeconds": 12000,
      "id": "100028",
      "issueId": "10002"
      }
      ],
      "updated": 1,
      "timetracking": {
      "originalEstimate": "10m",
      "remainingEstimate": "3m",
      "timeSpent": "6m",
      "originalEstimateSeconds": 600,
      "remainingEstimateSeconds": 200,
      "timeSpentSeconds": 400
      }
      }
      }

    • getIssuebyKeyMessage – A message node with script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to find an issue by key as shown below:

Get All Issues

Steps to view all issues in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Get All Issues dialog task is added with the following components:
    • getAllIssues – A user intent to view all issues.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • getAllIssuesService – A bot action service to fetch all issues
      from an external integration. Click the Plus icon to expand to view the getAllIssuesService bot action component properties.
    • In the Component Properties window, to add one or more responses, scroll down and click +Add Response.

      Sample Response:

      {
      "expand": "names,schema",
      "startAt": 0,
      "maxResults": 50,
      "total": 1,
      "issues": [
      {
      "expand": "",
      "id": "10002",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10002",
      "key": "ED-1",
      "fields": {
      "watcher": {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/EX-1/watchers",
      "isWatching": false,
      "watchCount": 1,
      "watchers": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      }
      ] },
      "attachment": [
      {
      "id": 10000,
      "self": "https://your-domain.atlassian.net/rest/api/3/attachments/10000",
      "filename": "picture.jpg",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "key": "",
      "accountId": "5b10a2844c20165700ede21g",
      "accountType": "atlassian",
      "name": "",
      "avatarUrls": {
      "48x48": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=48&s=48",
      "24x24": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=24&s=24",
      "16x16": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=16&s=16",
      "32x32": "https://avatar-management--avatars.server-location.prod.public.atl-paas.net/initials/MK-5.png?size=32&s=32"
      },
      "displayName": "Mia Krystof",
      "active": false
      },
      "created": "2023-02-28T09:45:11.830+0000",
      "size": 23123,
      "mimeType": "image/jpeg",
      "content": "https://your-domain.atlassian.net/jira/rest/api/3/attachment/content/10000",
      "thumbnail": "https://your-domain.atlassian.net/jira/rest/api/3/attachment/thumbnail/10000"
      }
      ],
      "sub-tasks": [
      {
      "id": "10000",
      "type": {
      "id": "10000",
      "name": "",
      "inward": "Parent",
      "outward": "Sub-task"
      },
      "outwardIssue": {
      "id": "10003",
      "key": "ED-2",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/ED-2",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "description": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Main order flow broken"
      }
      ] }
      ] },
      "project": {
      "self": "https://your-domain.atlassian.net/rest/api/3/project/EX",
      "id": "10000",
      "key": "EX",
      "name": "Example",
      "avatarUrls": {
      "48x48": "https://your-domain.atlassian.net/secure/projectavatar?size=large&pid=10000",
      "24x24": "https://your-domain.atlassian.net/secure/projectavatar?size=small&pid=10000",
      "16x16": "https://your-domain.atlassian.net/secure/projectavatar?size=xsmall&pid=10000",
      "32x32": "https://your-domain.atlassian.net/secure/projectavatar?size=medium&pid=10000"
      },
      "projectCategory": {
      "self": "https://your-domain.atlassian.net/rest/api/3/projectCategory/10000",
      "id": "10000",
      "name": "FIRST",
      "description": "First Project Category"
      },
      "simplified": false,
      "style": "classic",
      "insight": {
      "totalIssueCount": 100,
      "lastIssueUpdateTime": "2023-02-28T09:45:09.984+0000"
      }
      },
      "comment": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/comment/10000",
      "id": "10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "body": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
      }
      ] }
      ] },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "created": "2021-01-17T12:34:00.000+0000",
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "role",
      "value": "Administrators",
      "identifier": "Administrators"
      }
      }
      ],
      "issuelinks": [
      {
      "id": "10001",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "outwardIssue": {
      "id": "10004L",
      "key": "PR-2",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-2",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      },
      {
      "id": "10002",
      "type": {
      "id": "10000",
      "name": "Dependent",
      "inward": "depends on",
      "outward": "is depended by"
      },
      "inwardIssue": {
      "id": "10004",
      "key": "PR-3",
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/PR-3",
      "fields": {
      "status": {
      "iconUrl": "https://your-domain.atlassian.net/images/icons/statuses/open.png",
      "name": "Open"
      }
      }
      }
      }
      ],
      "worklog": [
      {
      "self": "https://your-domain.atlassian.net/rest/api/3/issue/10010/worklog/10000",
      "author": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "updateAuthor": {
      "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
      "accountId": "5b10a2844c20165700ede21g",
      "displayName": "Mia Krystof",
      "active": false
      },
      "comment": {
      "type": "doc",
      "version": 1,
      "content": [
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "I did some work here."
      }
      ] }
      ] },
      "updated": "2021-01-18T23:45:00.000+0000",
      "visibility": {
      "type": "group",
      "value": "jira-developers",
      "identifier": "276f955c-63d7-42c8-9520-92d01dca0625"
      },
      "started": "2021-01-17T12:34:00.000+0000",
      "timeSpent": "3h 20m",
      "timeSpentSeconds": 12000,
      "id": "100028",
      "issueId": "10002"
      }
      ],
      "updated": 1,
      "timetracking": {
      "originalEstimate": "10m",
      "remainingEstimate": "3m",
      "timeSpent": "6m",
      "originalEstimateSeconds": 600,
      "remainingEstimateSeconds": 200,
      "timeSpentSeconds": 400
      }
      }
      }
      ],
      "warningMessages": [
      "The value 'bar' does not exist for the field 'foo'."
      ] }
    • getAllIssuesMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to view all issues as shown below:

Update an Issue

Steps to update an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Update an Issue dialog task is added with the following components:
    • updateIssue – A user intent to update an issue.
    • issueKey, chooseField, updatedSummary, and newLabel – Entity nodes for updating the issue details.
    • prepareUpdateIssuePayloadScript – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the prepareUpdateIssuePayloadScript bot action component properties.
    • getResourceIdService – A bot action service to get a resource ID of a JIRA site.
    • updateIssueService – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the updateIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:

      Sample Request:

      {
      "update": {
      "summary": [
      {
      "set": "The updated summary"
      }
      ],
      "labels": {
      "add": "Label_to_add_without_space"
      }
      }
      }
    • getIssuebyKeyService – A bot action service to update an issue in an external integration. Click the Plus icon to expand to view the getIssuebyKeyService bot action component properties.
    • updateIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to update an issue as shown below:

Delete an Issue

Note: You can delete an issue only if the JIRA admin or owner of the JIRA project assigns you the permission to delete it. Otherwise, you will not be able to perform this action.

Steps to delete an issue in the JIRA integration:

  1. Refer to the Installing the JIRA templates section to install this template.
  2. The Delete an Issue dialog task is added with the following components:
    • deleteIssue – A user intent to delete an issue.
    • issueKey – Entity node to gather key to delete an issue.
    • getResourceIdService – A bot action service to delete a resource ID for an issue in an external integration.
    • deleteIssueService – A bot action service to delete an issue in an external integration. Click the Plus icon to expand to view the deleteIssueService bot action component properties.
    • In the Component Properties window, click the Edit Request link to edit the request parameters as shown below:
    • deleteIssueMessage – A message node with the script to display responses for various scenarios.
  3. Click the Train tab to complete the Dialog task training.
  4. Click the Talk to Bot icon to test and debug the dialog task.
  5. Follow the prompts in the VA console to delete an issue.
메뉴