JIRA Integration
We currently have a custom menu script for integrating with Jira in our system. However, this setup requires manual initiation of the script for each individual request. This manual step has become burdensome, especially when our technicians are required to create a Jira request for every incident falling under specific categories, subcategories, and items.
To streamline and automate this process, we can utilize the guidance provided in this article. It's important to note that this article is divided into two parts. The first part focuses on creating a Jira ticket, while the second part deals with updating the created Jira ticket. Both of these parts can be configured separately to address specific needs, or they can be used in combination to create a comprehensive solution. This approach will reduce the need for manual intervention and enhance efficiency in managing Jira integration within our system.
Prerequisites:
Create an additional request field for storing the Jira ticket ID, and make sure to add this field into the necessary templates.
The script uses the request subject and the content in the description to generate the Jira ticket.
Steps to configure
- Download the attached scripts and login to SDP Portal.
- Goto Admin > Developer Space > Global Functions > New: Copy paste the contents from GF_JIRA_configuration.txt
- Update the url and password (Base64 Encoded)
- For Jira OP, use the username and password. For Jira Cloud, use the username and API token.
- You can generate the base64 password using: https://mixedanalytics.com/tools/basic-authentication-generator/
- Goto Admin > Developer Space > Request Custom Function > New: Copy paste the contents from CF_JIRACreate.txt
- In the script, modify the API field name of the additional field to store the newly created Jira ticket ID.
- Goto Admin > Developer Space > Request Custom Function > New: Copy paste the contents from CF_JIRAUpdate.txt
- In the script, modify the API field name for the additional field that stores the Jira Ticket ID
- Set up two custom triggers to facilitate the creation and updating of requests from SDP to JIRA.
- When an SDP request is generated, meeting specific criteria, invokes the custom trigger. This trigger, in turn, invokes the custom function responsible for creating the Jira ticket.
- When an SDP request undergoes an update and the JIRA ticket additional field is not empty, it invokes a custom trigger. Subsequently, this trigger invokes a custom function responsible for updating the corresponding Jira ticket.
New to ADSelfService Plus?
Related Articles
Azure DevOps Integration
Feature: Azure DevOps Integration <--> ServiceDeskPlus (Plugin Model) --> Create a new work-item in Azure DevOps when a request is created in SDP --> Update SDP request status when a Azure DevOps work-item status is updated --> Updating Comments ...Slack Integration
This is a sample python script that is used to post request details from ServiceDesk Plus into Slack.Slack is a cloud-based team collaboration tool that allows team members to communicate without the use of emails or group SMS. Use Case: Lets assume ...Microsoft SCCM Integration for ServiceDesk Plus and AssetExplorer
Microsoft System Center Configuration Manager (SCCM) integration helps you fetch workstation details from SCCM and add them to ServiceDesk Plus or AssetExplorer. How does it work? The SCCM integration tool connects directly to the SCCM SQL ...Opmanager Integration - Create downtime schedule in Opmanager from a change request in ServiceDesk Plus.
This script will invoke the OPManger API to set downtime of assets using the schedule time and the assets / business views chosen in a change request on ServiceDesk Plus. Execution steps: 1. Download and copy the script and xml file into the ...ServiceNow Integration
Establishing two-way communication between ServiceDesk Plus and ServiceNow is done in 4 steps. It can be achieved using Python scripts by installing Python runtime in builds older than 11120 but with newer builds, it can be done with Deluge scripts ...