The opportunity to hear the opinion of an Atlassian Expert and experienced Jira Consultant such as Alex Ortiz, we are excited to share his insights about the Getint app.
Known as an influencer, followed by thousands on YouTube, Co-Founder of the Atlassian Builders’ Summit and Jira Life event, Alex is recognized for his in-depth and practical takes on all aspects of Jira. Recently, he turned his attention toward the Getint integration platform - purpose-built to connect Jira, Azure DevOps, ServiceNow, Salesforce, and more.
He plainly put it: “This app does it so easily, right? Getting two tools to talk to each other is a very, very hard problem to solve, and this team has managed to get that problem solved, and they do it in a very intuitive way.”
Let’s explore what especially stood out to him about Getint, and why his perspective matters.
Who Is Alex Ortiz, and Why His Opinion Counts
With a background in Jira administration and a following of thousands on YouTube, Alex is one of the most valued voices in the Atlassian ecosystem. His tutorials, reviews, and candid interviews with app vendors have helped Atlassian users worldwide make certain decisions.
What sets him apart is his practical approach - he’s not just showcasing features, but critically assessing whether tools solve real problems. And with Getint, that’s exactly what he saw: a focused, security-conscious integration platform that delivers on its promise.
The Getint Platform Through Alex’s Perspective
In the interview with Jacek Wizmur-Szymczak, Co-Founder of Getint, Alex emphasized that Getint stands out not by trying to be everything to everyone, but by maintaining a strong focus on dependable, hassle-free integrations tailored to Jira users’ real concerns. For him, integration isn’t only about syncing fields. It’s about people, processes, and adapting to real-world team needs which he observes daily.
He pointed out that security, documentation quality, and ease of setup are where Getint earns an excellence mark. Certified with SOC 2 Type II, ISO 27001 & 27018, and GDPR-compliant, the platform supports companies that deal with sensitive and regulated environments.
Some of his top takeaways included:
- Simpler tools are better - avoid adding more complexity.
- Pick vendors who truly understand customer needs and workflows.
- Meticulous planning and communication matter as much as the technical rollout.
- Leaning on automation reduces human error and accelerates resolution times.
Now, let’s walk through specific Getint integrations as specialist sees them, focusing on both functionality and user impact.
Real-World Examples: Highlights from Getint Reviews
1. Jira-ServiceNow integration
An intuitive setup experience
“What makes this application a little bit unique… number one is the user interface… number two is price. Usually, you have to buy two licenses, but with this app, it’s just one payment. You’re simply just paying for this ServiceNow app connector inside of Jira.”
Integrating Jira with ServiceNow can be extremely challenging - each has different data models and terminology. Alex honed in on Getint’s step-by-step configuration model, which makes robust integrations accessible, even to less technical users.
"The UI is very, very easy. It’s guiding you. It’s just super clear as to what’s expected and what the tool is enabling you to do in this case."
Easy deployment with Quick Build
The expert also recognizes - as an important option - the Quick Build feature for automating much of the integration process, resulting in faster, error-free launches.
He said: “all I have to do is sit back and enjoy the show for a couple of seconds, and Getint is gonna do the heavy lifting for me”.
True two-way sync
Getint powers bi-directional syncing of tickets, comments, and attachments, with advanced filtering (by user or assignment group) to control what flows between platforms. Alex demonstrated this by creating a Jira ticket, watching it seamlessly sync into ServiceNow, and vice versa.
Watch the full video review: ServiceNow Jira Integration
Implementation success story
Also, as an expert, Alex had the opportunity to tackle a real integration challenge for the company specialized in electronics manufacturing. He helped to sync ServiceNow (used for intake) with Jira (used for engineering work).
After struggling with a more complex solution that didn’t deliver, they switched to Getint - and saw immediate results. The platform allowed them to automate incident syncing, reduce manual work, and maintain existing workflows while giving leadership real-time visibility into both operational and project tasks. Alex’s involvement helped ensure the integration was clean, fast, and sustainable.
Seven Months Later: The Encore Review on Jira ServiceNow Connector
After living with the integration for over half a year, Alex returned with an encore review - bringing a long-term perspective on reliability and enterprise readiness:
“I’ve been using this actual integration for the last seven months. And I wanted to show you how easy and comfortable I am with the tool now because it really is a very easy-to-use tool for a team that is very reputable and has excellent customer service.”
One of the biggest additions in his follow-up was the difference between continuous sync and data migration:
“If you have a lot of data already inside of ServiceNow, then the data migration allows you to basically sync your data from ServiceNow into Jira. But when you do continuous sync, the moment you install the integration, any item created in ServiceNow, Jira now knows about it… So you’re essentially drawing a line in the sand.”
While Alex himself chose continuous sync for simplicity, he pointed out that Getint offers limited free migration of historical items, with options to expand depending on team needs.
He also went deeper into setup considerations. Although Jira admins can often manage configurations, ServiceNow’s complexity makes collaboration essential:
“On the Jira side, you don’t need admin rights per se, but I would highly recommend you use an account that has elevated access… And on the ServiceNow side, usually this is uncharted territory for Jira admins, so I always recommend having a ServiceNow admin on the call with you.”
Advanced Features That Make the Difference
In the encore review, we can learn about additional features that help teams fine-tune the integration:
- Selective comment syncing
“Not every comment needs to go to ServiceNow. You can set it so that only comments containing something like ‘external-’ get pushed across. That way Jira teams can keep private conversations internal while sending only the intentional ones over to ServiceNow.”
- Two-way attachment sync
“You can sync attachments both ways from Jira to ServiceNow or from ServiceNow to Jira. It’s all up to you.”
- Status mapping flexibility
“ServiceNow is way more complicated than Jira, so you definitely want to map your statuses carefully with the help of your ServiceNow admin.”
- Sync frequency
“This integration is on a cyclical 180-second loop. So every three minutes, you’re always going to have your integration running.”
Watch the full video review: Jira to ServiceNow Integration Guide | Setup, Mapping & Permissions
2. Jira-Azure DevOps integration
When reviewing Jira-Azure DevOps integration, Alex expresses how Getint efficiently syncs Jira Cloud with Azure DevOps, making day-to-day collaboration smooth for hybrid teams. He’s quick to draw the distinction between one-time migrations versus continuous syncing, urging the latter for organizations operating in tandem.
Leveraging JQL and project-based sync
Getint lets users set up integrations by project, simplifying troubleshooting and helping contain risks. Jira Expert especially values the granular control over what syncs, thanks to JQL filters.
“This custom JQL is where you’re able to control which issues actually come over or don’t… You can be very prescriptive here.”
Smart mapping for seamless workflows
A highlight is Getint's flexible mapping of statuses and issue types across platforms. Even if one side’s workflow is more complex, users can collapse multiple Jira statuses into a single Azure status with ease.
As Alex puts it, "If you run out of statuses to map on your destination tool, worry not. This tool is smart enough to let us map multiple statuses on one side to a single status on the other. So you can do multiple Jira statuses mapped to one Azure status, which is really cool."
Learn how to connect Jira with Azure DevOps step-by-step.
3. Jira-Salesforce Integration
Teams juggling Jira and Salesforce often get stuck in repetitive manual updates. In another one of his thorough video guides, Alex spotlights how Getint’s integration automates this workflow bottleneck.
He made the value proposition clear from the start:
“If your team’s using both Salesforce and Jira and the data needs to go back and forth and your team’s manually having to synchronize these two tools, then in this video I’m going to show you Getint.”
Continuous sync & data migration
In the tutorial, Getint is framed as a productivity accelerator - eliminating tedious, error-prone tasks.
“The continuous sync is if you have a team member that is working in both Salesforce and Jira, then you want the data to go either bidirectionally or one way... I’m going to be doing a continuous sync because I want my users to continue to use both tools. I want to basically create a single source of truth by synchronizing them. I don’t want my teams to have to leave their native tool.”
This approach allows teams to maintain their preferred workflows while ensuring data consistency across platforms.
Customization options
A key highlight that Co-Founder of Atlassian Builders' Summit points out, is the significant level of customization offered during the mapping stage. As he explained, “At this point, you can map any field in Jira, whether it’s a system field or a custom field to any system field or custom field inside of Salesforce as long as it’s available... You can select if comments are going to be synchronized both ways... And then you get to pick whether you want to delete attachments, if you want to do public attachments, or if you want to insert the attachments as a public comment.”
Such flexibility means organizations can adapt the integration setup to fit their specific workflows and business processes. Alex demonstrated this capability by showing how Jira issues - not just their primary data, but also comments and attachments - can be synced to Salesforce in a manner that matches the organization’s requirements. This ensures teams achieve seamless, tailored data exchange between platforms.
Check out the video review: Sync Jira & Salesforce in Minutes with Getint
The Value for Atlassian Community Members
Unlike traditional endorsements, Alex’s coverage of Getint reflects hands-on experience. He’s walked through real integrations, explored edge cases, and pushed features to test their limits.
What’s especially valuable is that Alex operates day-to-day in the Jira environment. His recommendations come from firsthand experience and serve as trusted guidance for peers seeking reliable ways to unify their toolkit.
A Platform Built for Jira Users Needs
Alex Ortiz’s review reaffirms what our team at Getint works hard to deliver: a practical, secure, and easy-to-use integration solution. Whether your team is connecting Jira to ServiceNow, Azure DevOps, Salesforce, or other tools, Getint offers the flexibility and precision to make it work - without compromising security or usability.
If you're managing multiple systems and looking to simplify your tech stack with trusted integrations, Getint is worth a serious look.
