Jira

Azure DevOps

Integration

MercuryWorks: Jira—Azure DevOps Integration

When MercuryWorks needed to securely collaborate with two external clients across Azure DevOps, they turned to Getint for a controlled, bidirectional sync. With strict filters, field-level mapping, and near real-time automation, the team was able to connect one monolithic backlog with two client instances—without compromising data privacy. This case study shows how MercuryWorks used Getint to maintain clarity, control, and confidence at scale.

Find Out how we did it!

Client Overview

Industry:

ITSM

Company size:

SMB

Location:

United States

KEY STAKEHOLDER

Donald Bickel

Partner, Business Lead at MercuryWorks

Leading U.S.-based software consultancy
Specializes in secure custom web applications and data platforms
Focused on innovation, scalability, and long-term client partnerships
Supports enterprise clients across various industries with Azure DevOps
IT operations span multiple internal and client-facing teams requiring secure collaboration

Scope of Work

Multi-Instance Azure DevOps Synchronization

Set up secure, bidirectional integration between MercuryWorks and two client-side Azure DevOps instances to streamline collaboration.

Advanced Field Mapping and Filtering

Applied custom field-level mapping and rule-based filters to control data visibility and meet privacy requirements.

No-Code Configuration Interface

Empowered internal teams to manage integration logic independently using Getint’s intuitive visual rule builder.

Reliable Performance and Scalability

Delivered a robust sync solution built for high-speed agile workflows and future scalability.

Integration Objective

MercuryWorks aimed to connect its internal Azure DevOps project with two client-side Azure DevOps instances to enable secure, bidirectional collaboration. The primary goal was to ensure accurate and filtered data exchange across environments—minimizing manual handoffs while maintaining strict control over visibility and information flow.

Data Integration Specifics

Issue Types:

The integration covered a range of issue types, including:

Epics
Features
Product Backlog Items
Bugs

Field Mapping:

Custom field mappings were established to enable precise synchronization across Azure DevOps instances. Key mappings included:

Title and Description
Acceptance Criteria and Effort
State, Area Path, and Iteration
Repro Steps and Attachments

Scripting and Custom Development Support

MercuryWorks leveraged Getint’s no-code rule builder and expert support to configure advanced filtering and logic, aligning the integration with their internal collaboration and security standards.

Success Metrics

The integration’s success was defined by

Secure Data Collaboration

Sensitive project data shared across instances with full control and privacy.
Near Real-Time Synchronization

Instant updates across all environments, reducing delays and miscommunication.
Granular Field Control

Selective syncing of fields and issue types ensured clarity and compliance.
No-Code Admin Flexibility

Internal teams managed sync rules without requiring developer resources.

Vendor Selection Process

Initially, MercuryWorks evaluated several marketplace tools for Azure DevOps integration. Getint stood out for its visual rule builder, no-code setup, and the ability to handle complex sync requirements across multiple environments—without the need for external platforms or custom scripting.

Why Getint Stood Out?

During the vendor selection process, Getint emerged as the preferred choice due to:

Built-in Integration

No need for an external hub, ensuring easier maintenance

User-Friendly Interface

Accessible for standard Jira administrators, with straightforward configuration

Reliability and Low Maintenance

Set-and-forget functionality

Cost-Effectiveness

Balanced pricing for the value delivered

Responsive Support

Prompt and effective assistance during setup and troubleshooting

800 000 +

Active Users

5 000 +

Installations

3.8 / 4

Rating

7 mln

Integrations Daily

Our Certifications

What We Accomplished

Secured Integration Without Overexposure

Each client only sees data explicitly permitted by MercuryWorks through strict field-level filters and direction settings.

Field-Level Mapping for Agile Collaboration

Mapped complex fields like Area Path, Repro Steps, and Attachments—allowing full backlog visibility without manual duplication.

Reliable Automation, Near Real-Time Sync

Getint’s sync engine delivered stable, almost real-time updates across all environments—even under high velocity agile sprints.

Zero-Code Setup and Scalable Control

MercuryWorks leveraged Getint’s visual rule builder to configure integrations in-house without development delays.

What Key Stakeholder Say

“Using Getint has been great, and the granularity on what we can sync along with rules on what gets synchronized exceeds our expectations.”

Donald Bickel

Partner, Business Lead at MercuryWorks

Conclusion

Getint’s integration solution has empowered MercuryWorks to collaborate securely and efficiently across multiple Azure DevOps environments.

The success of this implementation highlights Getint’s flexibility and strength in supporting enterprise-grade, multi-instance integrations.

Schedule a Free Demo with our Integration Expert

Discover how seamless and efficient integrations can be with a personalized demo. Our expert will walk you through the process, tailor the session to your specific needs, and answer any questions you have about connecting your tools effectively.

Book a Demo Call

Frequently asked questions

Have questions? 
We've got you!

Our comprehensive FAQ section addresses the most common inquiries about our integrations, setup process, pricing, and more - making it easy to find the answers you need quickly.

Can you sync a single Azure DevOps project with multiple clients?

Yes. Getint allows a one-to-many setup, syncing one project with multiple external Azure DevOps environments.

Is it possible to apply filters per connection?

Absolutely. You can create unique sync rules for each connection, defining exactly what gets shared and in which direction.

Do I need to code to manage this integration?

No coding is required—everything is managed through Getint’s intuitive no-code visual rule builder.

What fields can be synced in Azure DevOps?

You can sync core and custom fields, including attachments, area paths, iterations, and nested items like Repro Steps.

What made Getint the right tool for this project?

Its ability to offer granular control, secure filters, near real-time sync, and a clean setup without third-party infrastructure.

Experience a smarter way to integrate & synchronize.

Discover the power of seamless connections, bridging your favorite tools for optimized workflow and productivity. Unleash the potential of unified platforms with Getint.

Book a Demo