1. Overview

...

Table of Contents
style none

1. Overview

There shall be a Jira app that can be configured to enable bi-directional sync between Jira and ServiceNow.

• In Jira, admin should be able to give SNOW credentials (API access) to connect the two systems.

• Once connected, admin should be able to map the 1) project 2) issue type and 3) individual fields in Jira to that in SNOW

• Upon mapping admin should be able to do unidirectional (create and update) or bidirectional (create and update) sync of tickets.

• Updates should include field updates, status updates, comments etc.

(This is based on information collected so far. We are still doing requirement analysis with customer).

1.1 Business Requirement

Business needs a plugin for Atlassian to delete the users in bulkfor ServiceNow connector for Atlassian Service Desk for seamlessly create/update Issues/Incidents in Jira SD and ServiceNow.

1.2 Pre-requisites

1. Jira Software as well as Jira Service Desk (Plugin is compatible with JSD too) should be installed and licensed.
2. Database should not be the default database, MySQL or PostgreSQL will work.
3. There should be some data, in terms of availability of Users and Groups in Jira.
4. The CSV to import users should have appropriate headers and there should not be spelling mistakes. (Test what happens when there are spelling mistakes)
5. Bulk User delete should be installed.
6. Bulk User delete functions in two different type of license: Understand the different options available when using Trial Version and when using the Paid version of the plugin.
7. On Trial Version: On one instance only 3 attempts are allowed, no matter how many Admin users are installing them after the first trial license has expired.

2. Proposed Solution

Plugin is intended to provides the facility to delete Jira-users in Bulk. Out of the box(OOB) Jira does not provide this feature.

3. Solution Description

3.1 Features

• Bulk User Delete Plugin is for Jira Admins who wants to delete unwanted Jira users in bulk from a single page without toggling between different Jira pages
• Plugin has basically two different functional pages. One is Users List page and Other is Upload page.
• User List Page
  • Users list page displays list of users and each page will display maximum of 2000 users. If the Jira instance has more than that 2000 users, then it will display navigation options(next page and previous pages).
  • Users list page has provided select and deselect option, so that Admins can easily select and deselect users whom they want to delete. 
  • A pop-up box for confirmation appears before actual deletion, so that Jira Admins can abort or proceed with the deletion process.
  • A deletion status page appears which displays detailed status  (no. of users deleted, no. of users not deletion, justification for not deleting) as in Success and Failure of the Deletion process.
  • Editing of Users details can also be done from User List page.
  • Users list page gives Admins provision to search for particular User in Jira, using the text search box
  • User list page give an option to filter available users based on the Jira Groups they belong.
  • A button to directly reset the applied filter, which clears the search value and applied group filters.
  • An option to export list of users (Selected Users or All Users of Jira). A direct button to export CSV of selected users or all users, and saves the exported CSV too on your local instance.
• Upload Page
  • It facilitates user to upload a proper CSV file(Username, full name, Jira-groups, Email Addresses) of Users which are there in the Jira instance, along with the delete button
  • Delete button on Upload page deletes the users from Jira whose details matches in the uploaded CSV.
  • A confirmation dialog box appears before actual deletion of uploaded CSV, which provides a second chance to Admins to re-think on their decision.
  • Deletion status page displays the detailed status.

3.2 User and Roles 

...

1. ServiceNow user registration for integration
2. Local Jira SDK configuration/Installation
3. Listing the APIs required for ServiceNow integration

2. Proposed Solution

Plugin is intended to provides the facility to create/update incident in ServiceNow . Also, ServiceNow configuration is required to push the incident create/updates to Jira SD.

3. Solution Description

3.1 Features

3.2 User and Roles 

Jira Administrator privileges are required to install/access the plugin.

3.3 Supported Field Type Mapping 

3.3 Supported Field Mapping Configuration for SAP Dev Instant

Image Added

3.4 Supported Field Mapping for SAP Dev Instant

3.4 API details for mapping between Jira field options and Service now field options

{
    "update": {
        "comment": [
            {
                "add": {
                    "body": "Comment added when resolving issue"
                }
            }
        ]
    },
    "transition": {
        "id": "2"
    }
}

 Header: 
Authorization: Basic c3Zpc2h3YWthcm1hOnN2aXNod2FrYXJtYQ==
X-Atlassian-Token: no-check
Content-Type: multipart/form-data; 

form-data:

name="file"; filename="Assig.PNG"
Content-Type: image/png