OpsHub - Enterprise class Integration and Migratio Atlassian Partner

Hi @Rani Shwaiki Since you’re hitting a blank screen and timeout error after clicking "Get Started," it’s likely something is breaking in the OAuth flow or the app permissions handshake. Here’s how the setup should work with Atlassian’s GitHub for Jira app: * Go to Jira Cloud > Apps > Find new apps * Search for GitHub for…

Hi ibm.kustagi@mercedes-benz.com If your goal is to integrate Azure DevOps (ADO) work items into Jira so they appear on Jira Plans—especially for a specific ART—then native import options may not suffice for ongoing, real-time visibility or long-term scale. Here’s what to consider: * Can your teams see real-time updates…

Hi @Dorene Watson You’ve highlighted a critical challenge with enterprise-scale integration striking the right balance between security, scalability, and manageability. When dealing with hundreds of projects across both Jira and GitLab, maintaining fine-grained access control without creating administrative overhead is no…

Hi @Vimal G Yes, it’s possible to integrate Jira and Salesforce using just their REST APIs—no add-ons required. Add-ons are not robust and reliable way for integrations, due to: * Excess coding – you will have to almost code the whole sync to integrate comments, attachments, links, formatted content, conflict. Literally…

Hi @Suvidhaa Meenachipuram Subramani Absolutely — migrating both Jira and Confluence to the Cloud is a big move, but planning ahead makes all the difference. What to do: * Start with a health check: Clean up unused projects, spaces, and users before migration. * Use Atlassian’s Cloud Migration Assistants: These tools help…

Hi @Vikrant Yadav Unless both the Jira cloud instances are administered by your org, another problem with plug-ins is they typically require admin access and enabling user email public visibility, which are huge security risks for enterprises.. Other problems with plugins are: * Excess coding – you will have to almost code…

Hi @Eyal Taylor Yep, the Jira Cloud Migration Assistant (JCMA) is a solid place to start—but it comes with a few caveats. Here’s what to keep in mind: * Field templates need to be same for that project in both Jira instances * Team in source Jira won’t be able to work on issues till the time migration is going on. There…

Hi @Gomathi Sundarraj Jira Cloud to Data Center migration isn’t officially supported via the standard migration assistant—it’s a bit of a manual process, especially for attachments. Here’s what typically works: * Use the Jira Cloud backup feature to export a ZIP file (this includes issues and attachments). * Extract the…

Hi @Vruti Thakkar You can connect Jama and Jira using REST APIs, but syncing things like hierarchy, trace links, and comments gets tricky without structured mapping. Here’s what matters most: * Make sure fields are aligned between both tools—especially custom ones. * Handle relationships carefully (e.g., parent/child…

Hi @Monika Yeah, this is a known issue. Xray Server and Xray Cloud don’t use identical entity labels, and that mismatch can break automated field mapping during migration. Here’s what helps: * Use a migration approach that lets you re-map entities manually or through configuration—not just raw exports. * Additionally…

Hi @Leo This is a common gap in basic GitHub–Jira integrations. Most native setups only capture commits, branches, and PRs—but they don’t handle status transitions unless issue keys are used consistently, and the integration supports deeper field mapping. OpsHub Integration Manager(OIM), an Atlassian Solutions partner can…

Hi @ramyaallena You’re right to look into this—Script Runner for Cloud is quite different from the Data Center version. Here’s what to expect: * Features like behaviors and certain workflow customizations aren’t supported in the Cloud version. * Most scripts will not migrate automatically—you’ll need to manually rework…

Hi John. There isn’t official Atlassian documentation specifically for Salesforce–Jira integrations during next-gen migration, but here’s what to keep in mind. When moving from classic to next-gen Jira projects: * Issue types, custom fields, and workflows may not carry over automatically * Next-gen projects use…

Hi @Durga prasad Migrating from Zendesk to Jira Service Management (JSM) on Atlassian Cloud (Premium) is achievable, and there are several approaches depending on the complexity of your data and migration goals. You may refer to an article on the Atlassian community that walks through the key considerations before…

Hi @Supporto Livello 1 Collaborating across Jira Service Management instances is a common challenge—especially when working with external clients. Since each instance is isolated, you’re right that native functionality doesn’t support real-time sync or shared queues out of the box. If both teams want to stay in their own…

Hi @Mkurama Migrating projects between two Jira instances—especially across domains—can be trickier than it looks. Beyond just moving issues, you’ll want to preserve structure: workflows, hierarchies, links, attachments, and history. That’s where most manual exports or partial tools fall short—or bring in clutter you’ll…

Hi @lad6bp, Yes, you can definitely migrate your issues from the old Jira to your new Jira Cloud instance. Migrating in chunks in one of the migration best practices. But it’s important to plan carefully. To decide the right approach, here are a few things to consider: * Are Jira DC and Cloud using the same field…

Hi @Petr Drozd The difficulties you have described are unfortunately common when cloud migrations aren't well-planned and executed. You are right that the standard migration path is typically from data center to cloud and not the other way around and reversing the move may not seem straightforward, given that you have…

Hi Dimitris, Yes, when syncing Jira Cloud with Codebeamer, you’ll need to use an API token instead of your Jira password. Here’s how to generate one: * Go to https://id.atlassian.com/manage-profile/security/api-tokens * Click “Create API token,” give it a label, and copy the token. * Use your Atlassian email as the…

Hi @Vineeta Wadkar Jira and IBM Rational DOORS don’t connect out of the box, so you’ll need an integration tool to set up and manage that connection. * Syncing requirements: You can map DOORS requirements to Jira tasks or stories and include traceability links so both sides stay connected. * New requirements: If set up…

Hi @chandrashekhar_singh Connecting your GitHub repo to Jira can be a great way to bring development activity into your planning workflow—like linking pull requests, branches, or commits directly to Jira issues so everything stays in sync. Now, depending on what you're trying to achieve—basic visibility or deeper…

Hi @UdayKiran You’re not alone—this happens more often than it should. If pull requests aren’t showing up in Jira, it’s usually due to one of these: * The GitHub repo isn’t properly linked in the DVCS settings * The PR isn’t tied to a Jira issue key in the branch name or commit message * Permissions or token scopes might…

Hi @Vikram You’re running into a common limitation—most Jenkins-to-Jira integrations require higher-level admin permissions to post updates like build info directly to issues. This is often due to how the APIs handle authentication and write access to specific fields or projects. But no, full admin rights aren’t always…

Hi @sweber You're right to double-check—Atlassian’s native GitHub → Jira integration does not currently support automatically adding PR references into Jira comments the way the Teams integration does. What it does offer is smart linking: if your PRs mention a Jira issue key in the title or description, Jira will show that…

Hi @Anup Kale Yes, CSV exports/imports seem like the go-to move, but they’re rarely smooth—especially with JSM. Customers not mapping correctly, lost permissions, missing custom fields… it’s easy for things to break. A lot of tools offer migration help, but the key question is: Can they do it without disruptions or…

Hi @Julian Andres Carvajal Bedoya There can be many ways of automating an integration by using APIs, ETL tools, custom scripting but keep in mind set ups can be complex and require significant time and development effort. To make it easy and hassle-free consider using an Atlassian solution partner which use low code…

Hi @Boris Engert You can upgrade your Jira Server as suggested above and then copy your data to the Cloud. If history is not important, then you may go for a CSV import and export. If you want to directly migrate from your older version 4.4 to the cloud without upgrading the Jira Server or losing history, then the best…

Hi @Priyadarshini Bharathkumar You are looking to automate Jira project access provisioning upon ServiceNow approval, creating a seamless user experience. Here's a breakdown of the integration solution and how it can be implemented: Understanding the Integration Requirements: Trigger: ServiceNow approval of the service…

Hi @Sirisha Karavadi As you already built an automation script to integrate JSM tickets with Jira that supports cloning of ticket and supports comments between JSM and linked Jira Issues. For synchronizing the status of linked Jira ticket to JSM as mentioned in #1 and #2, you can extend the script to fetch the list of…

Hi @Engineering Services OpsHub provides a free Community Edition that integrates work items bidirectionally with reliable and predictable outcomes. You can refer to Jira Integration with Azure DevOps documentation for the details on Azure DevOps and Jira integration. In addition to being free, it provides rich data…