For Levare International, Jira was never meant to be a strategic decision.
It entered the organization as a requirement — one that came with a partnership and couldn’t be ignored.
Levare operates in the oil and gas industry, delivering industrial pumps, machinery, and field services across multiple regions. Behind that work sits a complex IT landscape, supporting ERP systems like Sage X3 and a growing number of internal and cross-company projects.
One of Levare’s key partners, a large French organization, required all collaboration and customer communication to take place in Jira Cloud. To remain compliant and continue working together, Levare introduced Jira internally, navigating approvals, compliance checks, and internal alignment along the way.
“As a customer, we were asked to be compliant with Jira. That’s why we introduced Jira Cloud within the company.”
— Maksim Iablokov, Information Systems Manager & PMO Lead at Levare
At first, this solved the immediate requirement.
But it also exposed a much deeper challenge.
source: https://marketplace.atlassian.com/apps/1223930/
Two Independent Jira Instances, One Shared Workflow
Levare and its partner were working in completely separate Jira Cloud environments. Each instance had its own users, workflows, and rules.
On the partner’s side, Jira was already operating at enterprise scale, with more than two thousand active users. On Levare’s side, Jira was intentionally lightweight, used by fewer than twenty people across IT and project management.
The teams needed to collaborate on the same work, but their systems didn’t share context.
Early attempts relied on semi-manual synchronization and technical workarounds. While functional at first, they required constant attention and didn’t scale as collaboration increased.
At the same time, many integration tools introduced a different kind of risk: pricing models tied to the number of users on the other side of the integration. For Levare, that alone ruled out a large part of the market.
Choosing a Jira Integration That Wouldn’t Become the Problem
Levare approached the decision pragmatically. They weren’t looking for a platform that would reshape their workflows. They needed an integration that would fit into an already complex environment and stay predictable over time.
Getint stood out early.
“Getint was almost the only company not pricing for additional Jira users on the other side of the integration.”
That pricing model made the solution viable. What followed confirmed it.
Levare’s team reviewed Getint’s documentation, explored the configuration logic, and built a proof of concept independently. There were no blockers, no unclear dependencies, and no need to rely heavily on support.
Over the course of an entire year, Levare contacted Getint’s support team only once — and resolved the issue internally before receiving a response.
“The documentation was quite handy for us to run our integration. We didn’t face any blocking questions.”
Designing an Integration That Matches Real Work
The final setup reflected how Levare actually operates.
Internally, the company runs two major Sage X3 projects — one in Mexico and one in Turkey. Both needed to be integrated with a single Jira project on the partner’s side, while still remaining clearly distinguishable.
Rather than building separate integrations or introducing unnecessary complexity, Levare used field-based logic and filters to route issues correctly. Additional fields helped identify project context, while mappings ensured consistency across issue types, priorities, and mandatory fields such as due dates.
All synchronization flowed through Getint’s mapping engine.
“Everything goes through mappings. If something is incorrect, it’s very easy to understand what field or value triggered it.”
Licensing constraints also shaped the solution. Providing Jira licenses for every partner contributor wasn’t realistic, so Levare introduced a single-assignee strategy that preserved visibility without inflating costs. The integration supported this approach without limitation.
Visibility, Logs, and Confidence Over Time
As the integration evolved, errors did appear — mostly when partner requirements changed or new fields were introduced. But they were never opaque.
Getint’s logs made it clear where issues occurred and why. For someone with an IT background, troubleshooting was straightforward and rarely disruptive.
“Every time, I was able to fix the issue without significant impact on collaboration.”
Over time, the configuration stabilized.
The last meaningful change was made in March. Since then, the integration has been running without intervention — no failed syncs, no operational noise, no dependency on support.
A Renewal Based on Experience, Not Promises
When the time came to renew the integration, the decision didn’t require debate.
By then, Getint had already been running in production for a full year. It supported multiple projects across countries, adapted to evolving partner requirements, and continued to work quietly in the background.
The renewal wasn’t driven by new features or future roadmaps. It was driven by trust built through daily use.
“Since that time, everything has been going very smoothly.”
— Maksim Iablokov, Levare
For Levare, renewing Getint meant continuing with a solution that had already proven itself — one that didn’t demand attention, but consistently delivered stability.
When the Best Integration Is the One You Don’t Think About
Today, Getint operates quietly behind Levare’s collaboration with its French partner. Tickets sync. Updates flow. Context remains intact across systems.
The integration doesn’t try to stand out.
It doesn’t require constant tuning.
It simply works.
For Levare, that’s what success looks like: an integration set up once, refined thoughtfully, and trusted enough to renew after a year of real-world use.
