You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I’m Ben, a product manager on the Atlassian’s Migration team. We’ve recently started a new EAP for the Portfolio analyzer and this is an official invitation for you to join the program, try out the feature, and help us make it better or add additional capabilities that could be useful for your case.
Right now, it has the following functions:
Relations: You can view your Atlassian products, their projects or spaces, and all relations and links between them. A relation is identified based on any type of link in the content, also regular URLs.
Summary info: You can see the aggregated information, like the number of issues or pages, for the entire instance or a selection of items.
Filtering: You can use filters to find items that weren’t updated for a long time or that have dependencies on the most common apps, like ScriptRunner for Jira.
Scoping your migration: You can create a selection of items, see the estimated migration time, and export the related project or space keys into a file to help you build a migration plan in the assistants.
One of our main goals is to help you scope the items you want to migrate. You can do it by manually selecting specific items, filtering by last update or app usage, or automatically selecting all dependent projects or spaces so your data is complete after the migration.
Here’s a sample selection of projects that have dependencies on one of the most common Jira apps:
When you create a selection, you can export it into a file that includes the keys of projects or spaces you selected. In the next versions, we want to make it more automated – right now, you’d have to manually add them to your migration plan.
It’s an early EAP, so collecting and uploading data is still fairly manual. Here’s a summary of steps:
Collect data: You’ll run a script on each of your server instances to collect data about entities and relations between them.
Upload data: You’ll upload the collected data to your organization in cloud. We don’t collect any identifiable data, such as the content of issues or pages.
View data: Once it’s uploaded, you’ll be able to view it in Portfolio analyzer on https://portfolio-migration.atlassian.com (available only after you get EAP access).
You can request to join the EAP using the following form. We’ll only need emails of Atlassian accounts we should grant access to.
If you’d like to learn more about this feature, you can check out our docs: Portfolio analyzer docs
We’re really looking forward to hear your feedback, so we can improve this tool based on your needs. Feel free to comment on anything, from how the feature works to the improvements you’d like to see. We’ll get our best people to review it. You can leave your feedback as a comment on your Early Access Program sign-up request or in the comments below.
Sneak peek: Our initial ideas were to improve the user experience of Portfolio Analyzer or experiment with data clustering.