<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Malaikawahid on Medium]]></title>
        <description><![CDATA[Stories by Malaikawahid on Medium]]></description>
        <link>https://medium.com/@malaikawahid1122?source=rss-96d098535264------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u-d3gzwq4OaKo5oP5MrupQ.png</url>
            <title>Stories by Malaikawahid on Medium</title>
            <link>https://medium.com/@malaikawahid1122?source=rss-96d098535264------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:49:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@malaikawahid1122/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Connecting Jira and ServiceNow: What I Learned from Exploring Getint Integration]]></title>
            <link>https://medium.com/@malaikawahid1122/connecting-jira-and-servicenow-what-i-learned-from-exploring-getint-integration-17dc1b1ffcbf?source=rss-96d098535264------2</link>
            <guid isPermaLink="false">https://medium.com/p/17dc1b1ffcbf</guid>
            <category><![CDATA[it-service-management]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[system-integration]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Malaikawahid]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 11:46:44 GMT</pubDate>
            <atom:updated>2026-11-17T11:46:44.575Z</atom:updated>
            <content:encoded><![CDATA[<p>When an Connecting Jira and ServiceNow: What I Learned from Exploring Getint Integration</p><p>IT incident requires a software fix, the work often moves between two teams operating in completely different systems. ServiceNow handles the incident, while Jira tracks the development work. Both teams may be making progress, but keeping their records aligned can become an unnecessary administrative burden.</p><p>I recently explored this challenge while collaborating with <strong>Getint</strong>, an integration platform that connects tools such as Jira, ServiceNow, and Azure DevOps.</p><p>As a Business Analyst and Solution Architect, I was particularly interested in understanding how integration decisions affect business processes, data consistency, and team collaboration.</p><p>Rather than approaching the exercise as a simple technical connection, I wanted to understand what makes an integration genuinely useful in day-to-day operations.</p><h3>The Real Challenge Isn’t Connecting Two Systems</h3><p>Jira and ServiceNow serve different purposes.</p><p>ServiceNow is commonly used by IT service management teams to handle incidents, service requests, and operational activities. Jira, meanwhile, supports development teams in planning, tracking, and resolving technical work.</p><p>Consider an incident reported through ServiceNow that requires a code change.</p><p>The support team creates an incident, while the development team creates a corresponding Jira issue. Without integration, someone must manually communicate progress between the two systems.</p><p>This introduces several risks:</p><ul><li>Inconsistent ticket statuses across teams.</li><li>Delayed communication about fixes and investigations.</li><li>Duplicate data entry and administrative effort.</li><li>Limited visibility into the overall resolution process.</li></ul><p>The objective of integration should therefore be more than transferring information. It should establish a reliable connection between two workflows while allowing each team to retain ownership of its responsibilities.</p><h3>Exploring Getint Through a Practical Scenario</h3><p>For my exploration, I used a <strong>Jira Cloud test project, a ServiceNow Personal Developer Instance, and Getint’s standalone integration workspace</strong>.</p><p>The scenario focused on a payment-processing incident that required investigation by the development team.</p><p>I configured a controlled workflow in which a qualifying ServiceNow incident could create a corresponding Jira bug. The integration was scoped to a specific test project and filtered incident records rather than synchronizing everything indiscriminately.</p><p>During the pilot, I verified three important behaviors:</p><p><strong>1. Record creation:</strong> A ServiceNow incident successfully generated a corresponding Jira bug, carrying across its summary and description.</p><p><strong>2. Status synchronization:</strong> Moving the Jira bug to <em>In Progress</em> updated the linked ServiceNow incident to the corresponding state.</p><p><strong>3. Comment synchronization:</strong> An engineering comment entered in Jira appeared as a private work note in ServiceNow.</p><p>These results demonstrated how selected information could move between platforms without requiring teams to manually reproduce every update.</p><p>However, the exercise also highlighted several important architectural considerations.</p><h3>Three Lessons That Stood Out</h3><h3>1. Field Mapping Is a Business Decision</h3><p>It is tempting to assume that fields with similar names should automatically synchronize.</p><p>In practice, this requires more thought.</p><p>For example, Jira and ServiceNow may represent priority differently. ServiceNow can calculate priority using impact and urgency, while Jira may use a separate priority scale.</p><p>Similarly, a completed Jira issue does not necessarily mean that the related ServiceNow incident should be closed.</p><p>The key lesson is to <strong>define field ownership and synchronization rules before configuring mappings</strong>.</p><p>An integration should support the business process, not accidentally redefine it.</p><h3>2. Bidirectional Synchronization Requires Boundaries</h3><p>Getint supports configurable one-way and two-way synchronization, but not every field needs to move in both directions.</p><p>In my pilot, Jira engineering comments were configured to appear as private ServiceNow work notes, while private ServiceNow notes were excluded from synchronization back to Jira.</p><p>This distinction matters because information intended for internal technical discussions should not automatically become visible to other audiences.</p><p>For production implementations, organizations should also validate attachment permissions, sensitive information handling, and conflicting updates.</p><p><strong>More synchronization does not necessarily mean better integration.</strong></p><p>The goal is to exchange the right information with the right people.</p><h3>3. Testing Should Validate the Workflow, Not Just the Connection</h3><p>A successful connection test confirms that two applications can communicate. It does not prove that the complete business workflow behaves correctly.</p><p>During my exploration, Getint’s reporting functionality helped verify record creation and subsequent synchronization events.</p><p>This reinforced the importance of checking actual record behavior rather than relying exclusively on configuration screens.</p><p>Before production deployment, I would also recommend testing excluded records, conflicting updates, attachment handling, failed permissions, and incident reopening.</p><p>A reliable integration needs both technical validation and business acceptance.</p><h3>Where Getint Fits Into the Picture</h3><p>One of the useful aspects of Getint is its configurable approach to cross-platform synchronization.</p><p>Instead of building and maintaining a custom integration entirely through APIs, teams can define record relationships, field mappings, synchronization directions, filters, and workflow rules through the integration platform.</p><p>This can reduce the amount of custom integration development required, although organizations still need to consider permissions, governance, maintenance, and process ownership.</p><p>My experience reinforced an important principle: <strong>integration platforms provide the technical mechanism, but successful integration still depends on sound process design.</strong></p><h3>Final Thoughts</h3><p>Exploring Jira–ServiceNow integration gave me an opportunity to connect technical configuration with the broader architectural decisions that influence how enterprise systems operate together.</p><p>The biggest takeaway was that integration success should not be measured solely by whether records synchronize.</p><p>It should be measured by whether teams can collaborate more effectively, maintain accurate information, and resolve issues without unnecessary manual coordination.</p><p>For anyone planning a similar integration, I recommend starting with a small, controlled workflow, validating the synchronization rules, and expanding only after the business and technical behavior is understood.</p><h3>Want to Explore the Complete Setup?</h3><p>I documented the detailed configuration process, field mappings, workflow settings, screenshots, testing results, and troubleshooting considerations in my guest article published on Getint’s official blog.</p><p><strong>Read the complete guide:</strong> <a href="https://www.getint.io/blog/best-way-to-connect-jira-and-servicenow">Best Way to Connect Jira and ServiceNow: An Expert’s Guide to the Getint Integration App</a></p><p><em>Disclosure: This article draws on my hands-on exploration conducted as part of a content collaboration with Getint.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17dc1b1ffcbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>