Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
title10.1 Steps for how it is works

Step 1: Follow the above steps to create configurations.

Mandatory mappings could be as follows,

Step 2: Create an issue in Jira then enter the project, issue type and all mapped fields like summary, description,

Step 3: Click on issue which you created and check the Service Now Id and Service Now incident number custom fields. If these fields are not empty then we can assume that the incident got created in ServiceNow.

Step 4: Check the same incident number(INC0010669) in Service Now. If the values of the mapped field are correct in an incident of Service Now then the configuration of integration is done.

Note: If you select “Update” under your preferences in Configurations,then Servicenow Incident number and Servicenow Id do not get generated and the Incident is not created in Servicenow.And it is shown as follows:

If you select “Create” under your preferences in Configurations, then Servicenow Incident number and Servicenow Id get generated and the Incident is created in Servicenow.It restricts updation of Incident

Step 4: Enjoy this seamless integration between Jira to ServiceNow (big grin)

11. Release Note:

Expand
title11.1 Version 1.0.0
  • Jira issue update feature on incident update in Service Now

  • Ability to save field mapping information between JIRA and service now fields

  • Ability to view field mapping information between JIRA and service now fields

  • Ability to delete field mapping information between JIRA and service now fields

  • Ability to add field value mappings

  • Ability to delete the field value mappings

  • Ability to create incident in service now whenever a ticket gets created in JIRA

  • Ability to update incident in service now whenever a ticket gets updated in JIRA

  • Ability to create comment in service now whenever a comment is put in JIRA

  • Ability to filter the records based on applied filters

  • Ability to paginate through the records based on applied filters

  • Ability to log the events to the screen

  • Ability to remove all the configurations for a client

  • Ability to add integration user

  • Ability to restrict the creation/updation of incident based on preference configurations.