Dr. Ankita Mehta-OpsHub, Inc Atlassian Partner

Hi @Vaibhav Panchal Switching from Jira Service Management (JSM) to the Zoho stack works best when the migration is planned around accuracy, continuity, and minimal disruption. The goal is to get all the data you need into Zoho without losing context or slowing down your helpdesk. Key things to sort out before you begin: *…

Hi @Theresa Barnard You’ve got a few good options here, but before picking a CRM app inside the Atlassian stack, it helps to think through a few basics: * Data access – Make sure customer records stay internal-only and aren’t exposed to portal users. * Email integration – Since you use Outlook, check for reliable two-way…

Hi @Nicole_Brueckner Migrating issues without losing development information like Bitbucket branches, commits, and pull requests—is definitely important to keep the full context intact. Since development data in Jira is typically linked via the issue key, simply migrating issues while changing their keys can cause those…

;Hi @jhcaution Since the “Switch to Atlassian administration” option is missing and you’re getting a 404 error on the migration URL; it does sound like your workspace might be in a special state or pending some prerequisites before the connection can be established. A few things you might want to check or consider *…

Hi @vittorio bini I totally get the challenge you're facing with syncing timesheets between Jira and ServiceNow. Here’s what you may want to consider before you begin: * Mapping the Data: First, figure out how Jira Epics will map to ServiceNow Project Tasks. This will help keep things organized as the data flows between…

Hi @Scott Derderian You’ve made the jump from Jira Data Center to Jira Cloud, and now you're diving into GitHub integration—exciting stuff! When it comes to evaluating add-ons for this, here are a few things to consider: * Core Functionality: Think about what exactly you need in the integration. Are you looking to sync…

Hi @khushboo_puri Migrating Jira Align to Jira can definitely be a bit of a task, if you don’t take the following things into account: * What Data Do You Need?: Figure out exactly what you need to bring over. Are you migrating epics, features, stories, or maybe sprints and teams? It helps to know which pieces you want to…

Hi @preethi gardas Migrating from ALM to Xray can require some careful planning, especially when it comes to syncing test cases, requirements, defects, and test runs. Here are a few things to consider: * What Needs to Be Moved? Think about the relationships between test cases and requirements, or defects and test runs.…

Hi @Anastasia Gourina When thinking about integrating Jira/JSM with other tools, there are a few things to consider: * Complexity of Your Workflows: If you're after simple automations, Zapier can work fine, but if your workflows are more complex—like syncing ticket history, tracking times, or logging changes into other…

Hi @James Noble If you're looking to commits, pull requests, and defects between Jira and ADO, here are a few things to keep in mind: * What exactly are you linking? If you're just looking to link commits and PRs, that's straightforward. But if you need defects created automatically during code reviews, you’ll need…

Hi @Ermela Sarenas Yes, you can add another Test Case Management System (TCMS) like TestRail to a Jira environment already using Xray. However, running two TCMS tools can affect performance, increase complexity, complicate reporting, and raise operational costs. It's important to evaluate whether a single tool can meet…

Hi @Larry Lee Based on your description, it sounds like the work items did migrate, but they’re not appearing in views like Backlog or Active Sprint because of how the board is configured. You’re able to see them in Timeline and Lists, which usually means they’re missing from your board due to filter or column settings —…

Hi @Chiru Even if usernames and emails match, Jira treats AD users as new identities because it uses internal IDs. So, ownership (like dashboards, filters, comments, etc.) doesn’t carry over automatically. Things to consider before you begin: * Jira doesn’t auto-map ownership across directories * Manual cleanup or…

Hi @Matt Richards Before diving into how to fix the "blank operations page" issue in JSM, here are a few things worth checking to make sure the integration with Prometheus even shows up: * Project type matters – The Prometheus integration only works with Jira Service Management projects that have ITSM features like…

Hi @Marcos Hoyos , You're asking all the right questions — this is a common challenge when moving from tightly integrated ITSM tools (like Proactivanet) to Jira Service Management Cloud, which handles identity differently. What can be done Out of the box, JSM Cloud supports customer user provisioning via Atlassian Access…

Hi @Jason Butler If you're working with vendors who use different systems like Autotask, getting Jira Service Management (JSM) to talk to them smoothly can feel trickier than it should. Before you begin, please consider the following questions: * Are you syncing status, comments, attachments, or field updates? * Nail this…

Hi @Urmo There’s no native HiBob–Jira Assets integration, so if you're considering a custom setup or API-based sync, it’s important to plan for a few things upfront: * Data scope: What fields from HiBob are critical (e.g., name, role, manager, status)? * Update frequency: How often should the sync run? Will real-time or…

Hi @Karlovsky120 While Jira’s JSON import lets you create issues with specific fields (including custom ones), you can’t import full issue history (like status transitions, comments, changelogs, or original timestamps) using the native JSON import alone. Also, when planning a TFS to Jira migration—especially if you want to…

Hi @ACTRA ITDS Thank you for reaching out — and it’s inspiring to hear about the work your non-profit union is doing to support your community in Canada. Yes, Atlassian offers free Jira Cloud licenses for eligible non-profits through their Community License Program. Once approved, you’ll be able to use Jira Cloud (and…

Hi @ro_axonfintech As of now, Atlassian hasn’t published anything confirming that cloud-to-cloud migration will be disabled. Their Cloud Migration Assistant tools are still available and supported — but there have been known limitations and delays with large or complex projects. If you are looking for cloud to cloud…

Hi @David Martínez López You’re asking if Jira Cloud can natively pull in Azure Entra ID (formerly Azure AD) user attributes like department, location, or manager — and use them in issues, automations, or workflows. The short answer is: Not natively (yet). Jira Cloud doesn’t expose those Entra metadata fields by default.…

Hi @Robert Morris If you're seeing commits, branches, and pull requests in Jira but still getting messages like "Finish connecting your code" or "You’re almost ready to view deployments", it usually means the integration is working partially — specifically, the deployment and code event sync isn't complete. Here are the…

Hi @Mags K Yes, migrating from Fresh service to Jira Service Management (JSM) is absolutely doable — but a smooth transition depends on planning and the tools you use. Here are some key things to consider: * What exactly are you migrating? Just tickets, or also SLAs, workflows, attachments, KBs, assets, and users? Some of…

Hi @Don Hames This is a common challenge when working with Xray: standard Jira operations like Move, Bulk Move, Deep Clone, or even CSV export/import typically handle only the Jira issue data—not the Xray-specific metadata (like test steps, executions, coverage, attachments, etc.). Xray stores much of its data in custom…

Hi @Raoul Hopley Yes, data can be migrated from Server to Cloud. However, since your Server instance currently uses the Smart Templates app, one thing to keep in mind during migration is the handling of plugin field data. There have been cases where certain plugins were not compatible with Cloud. In such cases, consider…

Hi @Eunchae Shin Yes — the system is asking for the Support Entitlement Number (SEN) of your Jira Data Center instance, which is the destination, not the Cloud (source). Atlassian requires this to validate where the export is being used. Also keep in mind: * Jira Cloud’s native export is site-level only, not…

Hi @Albert Manuel, f you're only migrating a few projects between Jira Cloud instances — and not global configurations or users — that simplifies things, but there are still a few key aspects to keep in mind: * Custom fields & workflows: If the destination instance doesn’t have the same setup, you may need to recreate…