Assess your instance scale using Jira Cloud Migration Assistant: Database queries and usage metrics
You can assess the scale of your Jira instance by collecting data about its content, such as the number of users, projects, automations, and many more. Sharing this data with the Atlassian migration team will allow us to analyze the complexity of your migration and provide some guidance on migration planning.
How it works
The assessments are part of the cloud migration assistants, currently hidden behind a dark feature. When you enable them and run the assessment, we’ll automatically collect the following data:
Database entities: Number, or metadata, of entities, such as projects or issues
Usage data: for example the number of active users in the past days
Instance metadata: version, SEN number, Server ID, timezone
Browser metrics: performance and browser metrics, including network speed and quality, based on users' browser
The data will be saved in a ZIP archive with a number of files. You’ll need to share them with Atlassian for analysis, and also review yourself to get a better idea about your instance.
FAQs
Here are some common questions we’re getting.
Do you collect any identifiable data?
The assessment doesn’t collect any personal identifiable data (PII). Any data that we collect is based on IDs. It’s also not automatically shared with Atlassian – you share the files when you want to.
Do I need Internet connection? Do you call any APIs outside of my network?
The Internet connection is not required to collect the data. We’re also not calling any APIs outside of your instance’s network.
What’s the performance impact on the Jira instance?
We did performance testing and optimizations to make sure the assessment doesn’t affect your instance. When it’s running, your users can keep doing their work in Jira.
What’s the user key / ID collected from the user’s browser?
When collecting data from your users' browsers, we collect the user key associated with every user. These keys are hashed on export and never exposed to Atlassian teams. We only use them for grouping, clustering, and creating themes for research and analysis.
Before you begin
Here are some prerequisites:
You need to upgrade Jira Cloud Migration Assistant to version 1.9.14, or later.
It takes 24 hours to collect the users' browser data. We recommend that you run the assessment during working hours so the data is meaningful. The assessment won’t impact the performance of your instance.
Assess your instance scale
To assess your instance, follow these steps.
1. Enable the assessment
To enable the assessment:
Go to
<Jira_URL>/secure/admin/SiteDarkFeatures!default.jspaAdd
com.atlassian.jira.migration.features.assess-l1-cloud-tooling
If you need more details, see Enabling dark features in Jira.
2. Run the assessment
To run the assessment and collect the data:
Open the Jira Cloud Migration Assistant.
In the Assess the size of your instance card, select Begin assessing.
We’ll ask you to confirm that the data will be stored on your instance. Select Continue.
The assessment will start. We’ll collect the data that includes:
Database entities: Running queries on your database to collect data about your entities.
Usage data: We’ll check access logs to see the usage data.
Browser metrics: We’ll collect performance data from your users' browsers.
3. Download the results
Once the assessment is complete, which should take 24 hours, select Download ZIP file. The ZIP archive includes the following files:
File | Description |
|---|---|
| Data about specific entities, retrieved from the database. It helps us understand the scale of your instance. |
| Similar to above, but with a different set of entities. It helps the migration tooling team to determine the best migration strategy. |
| Usage metrics taken from access logs. It helps the Jira Cloud teams determine the best cloud instances for you. |
| Metadata about your instance for easier identification. |
| Data from users' browsers on the performance of your instance. It helps us understand what you’ll need in cloud for best performance. |
What data is collected?
Here are some details on the collected data that you can find in each of the files.
File: cloud-scale-database-[date].csv
The files includes data about the following entities:
Metadata of issues with 10k or more history groups
Number of active Jira Service Management agents
Number of active users
Total number of attachments
Number of automation rule executions a day
Metadata of automation rules with 30 or more branches
Number of deleted users
Metadata of groups with 35k or more user memberships
Number of Jira Service Management customers
Number of history groups
Number of history items
Number of inactive users
Number of Insight objects (assets)
Metadata of Insight objects (assets) with 20 or more fields
Number of Insight object schemas
Total number of issues
Number of Jira Service Management agents
Number of projects by type
Number of projects with 30 or more automation rules
Number of projects with 30 or more SLAs
Number of projects with 50 or more queues
Number of projects with 80k or more issues
Number of user groups
Total number of users
Metadata of projects with 10k or more history groups
Total attachments size in GB
File: tooling-scale-database-[date].csv
This file includes the following metrics:
Metadata of issues with 10k or more history groups
Number of active Jira Service Management agents
Number of active users
Total number of attachments
Number of automation rule executions a day
Metadata of automation rules with 30 or more branches
Number of deleted users
Metadata of groups with 35k or more user memberships
Number of Jira Service Management customers
Number of history groups
Number of history items
Number of inactive users
Number of Insight objects (assets)
Metadata of Insight objects (assets) with 20 or more fields
Number of Insight object schemas
Total number of issues
Number of Jira Service Management agents
Number of projects per project type
Number of projects with 30 or more automation rules
Number of projects with 30 or more SLAs
Number of projects with 50 or more queues
Number of projects with 80k or more issues
Number of user groups
Total number of users
Metadata of projects with 10k or more history groups
Total attachments size in GB
File: usage-metrics-[date].csv
Interactions date: Date when an interaction with the Jira instance was recorded in the access logs.
Active users per day: Total number of unique users who interacted with the Jira instance in the past 14 days.
Peak-hour active users per day: Number of unique users who interacted with the Jira instance at the same time. We obtain it by aggregating user IDs and the corresponding date-hour combinations in the access logs. It provides a snapshot of your instance’s busiest periods.
Node availability and data collection status: Data on the availability of each node (or single node). It also shows the status of data collection.
File: instance-metadata-[date].json
Product name and version: Name and version of your Jira product.
SEN: Support Entitlement Number (SEN), which is a unique identified of your Atlassian product.
Server ID: Unique identified of your Jira instance.
Instance UUID: A distinctive number of your Jira instance. It’s typically used for internal tracking and debugging by Atlassian Support.
Instance timezone: Timezone of your Jira instance.
Assessment starting date: The date when you started this assessment.
File: cloud-scale-browser-metrics-[date].jsonl
user ID: A unique identifier of a user. It’s generated securely and hashed randomly to maintain privacy, while also allowing us to track user interactions.
Browser type and version: Details about the browser, for example Google Chrome, Safari.
Operating system: Details about the operating system, for example Windows, MacOS.
Processor count: Number of processors on the device.
System memory (RAM): Total memory or RAM on the device.
Network download speed: The speed of downloading data.
Network connection quality: The effectiveness of network connection.
Network Latency (RTT): Round Trip Time (RTT) is a measurement of the time it takes for a signal to travel from a user's computer to the Jira Instance and back. This helps gauge the responsiveness of users' network connection.