SCP 11.0 and Jira integration

SCP 11.0 and Jira integration

Integration Steps

 

In SCP 11.0, JIRA administrator credentials and server URL configuration fields will not be available in the Jira.xml file. They must be configured on the current integration page.

Follow the below steps to move the integration files to the appropriate directories.


Note: If you are already using JIRA integration with any customizations in earlier versions,  please take a backup of the customized files and move the files as mentioned below and then update the customization changes in the new files.  
 
  • Move the Jira.xml file present inside [SCP_Home]/actionplugins/jira/conf/ to [SCP_Home]/integration/conf/ directory.
  • Move the jiraimpl.jar file present inside [SCP_Home]/actionplugins/jira/ to [SCP_Home]/integration/lib/ directory.
  • Move all the integration files present inside [SCP_Home]/actionplugins/jira/resources/ to [SCP_Home]/integration/resources/ directory. (This is not required if you have already done this in earlier versions)
  • Make the custom changes (if any) to the Jira.xml and restart the SCP server.


Configuring JIRA settings in SupportCenter Plus:
 

  • Go to Admin >> Integrations >> JIRA or Global Settings --> Integrations --> JIRA (if multiple portals)
  • Enter the Server name and Server Port where the JIRA application is currently running and choose between HTTP and https protocol settings.
  • Enter the JIRA administrator credentials (username/password) and Save the configuration. The password will be encrypted and saved securely in Database.

    For configuring JIRA On Demand settings,

    Enter the JIRA administrator credentials (username/API Key) and Save the configuration.
     
  • Click 'Save' to save the settings.

Note: All other configurations other than username and password are still in Jira.xml.




Steps to create JIRA action menu:
 

  • Create a new custom menu for Jira ticket creation under Admin   >   Request Custom Menu   >   Add New Menu.
  • Menu Name   >   Create_JIRA_UI_Ticket (If you want to change the menu name then changes has to be done in Jira.xml too as the configurations are internally mapped)
  • Description   >   Optional
  • Associates Roles   >   Select the Technician Roles who should get access to this menu (Options: All Roles or 'Selected Roles')
  • Associate Templates   >   Select the Templates, under which this menu should be displayed (Options: 'All Templates', 'All Incident Templates, 'All Service Templates' (or) 'Selected Templates')
  • Custom Html File   >   Create_Jira_Ticket.html (Make sure the HTML file is present under [SCP_Home]/Integration/resources/ directory.)
  • Action Type   >   Select Execute Class   >   com.servicedeskplus.integration.JiraActionImplementation (Make sure the jar file is present under [SCP_Home]/integration/libdirectory.)

                  New to ADSelfService Plus?

                    • Related Articles

                    • Jira Integration

                      Jira Integration JIRA Integrates with ServiceDesk Plus MSP using "Request Custom Menu". Sample Implementation is already done and bundled with our application. You need to change field names as per your requirement in JIRA.xml. So When a ticket is ...
                    • JIRA integration - Issue Types are not loaded

                      Post the JIRA is integrated with SDP MSP , the Projects data gets populated. However the other field - Issue Types will not show any values. To fix this follow the below steps The api call is used to fetch the issue types is ...
                    • 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 ...
                    • SCP 11.0 and above API documentation

                      SCP has a variety of APIs using which you can integrate 3rd party tools with our application. We have inbuilt API documentation. Please login to the application as administrator -> go to Admin -> General -> API -> Documentation to refer to the same. ...
                    • SCP upgrade from 11.0 to 14.0 prerequisites

                      Before migration to scp version 14 below 2 points has to be done in scp 11027 1. Back up password should not be default i.e SCP123!, it should be updated 2. TLSv1, TLSv1.1 has to be added under the file /home/jre/lib/security/java.security file ( ...