Scaling up Jira Software Cloud with support for 50K users and performance insights

[#1]

In December, we shared some big scale improvements for Confluence and Jira Service Management and we’re back with more to share. Today, we’re announcing support for 50,000 users on a single instance of Jira Software Cloud. We also have a brand new feature tailored for enterprises called Site Optimizer in Jira Software Enterprise that will help you effectively manage your data shape to optimize your performance.

Supporting larger teams on cloud per instance

Beginning March 29th, you can have up to 50,000 users on a single instance of Jira Software.

When we increase the number of users we support, this isn’t just about hitting a certain number. We think very critically about all the components that go into providing a performant experience at scale. We look at enterprise data shapes to understand how things like network configurations, concurrent user traffic, amount of data, migration tooling, and feature functionality perform at scale so we can ensure our products support your largest teams.

Because every organization is unique, it’s important that we look at how your data shape by running scalability assessments. We’ve expanded the eligibility of these assessments so every organization that has more than 5,000 users will undergo a scale assessment.

The process is really simple. Through the migration tooling (JCMA and CCMA), you’ll automatically collect your data and share it with Atlassian.

Our teams work together to analyze the data and share the results. In our experience, the results of the scalability assessments often show that there are opportunities to clean up your instances or make modifications before you migrate to cloud to achieve the best day-one experience.

Optimizing performance on cloud

As we expand the number of teams we support in cloud, we’re also developing features that help you optimize the usability of your site and improve the overall performance of large, complex data shapes in cloud

Site Optimizer is a new beta feature in Jira Software Cloud Enterprise that allows you to understand your site’s attributes and take action to optimize performance through:

A new dashboard: The Site Optimizer dashboard shows you how many attributes you have and if they’re within the ideal threshold for optimal performance.

Bulk actions: Once you have a view of your data thresholds, you can take immediate action by removing unused attributes from your instance.

Today, Site Optimizer reports on:

• Custom fields

• Issues and projects

• Roles and permissions

Because this is a beta feature, we’ll be rolling this out iterative over the next few weeks. Everyone on Jira Software Cloud Enterprise will have access to it by April 15, 2024. The great news is that participants in the Site Optimizer Early Access Program have not only seen an improvement in the performance of their instances but also reported productivity gains from their teams. When you’re not having to shift through unused data, you save a lot of time.

What’s next?

As we mentioned in our last scale announcement, visibility and guidance are our biggest investment areas for performance and scale. Over the next year, we’ll be:

• Expanding the attributes available in Site Optimizer so you can get more insight into the usage of your instance and take action to optimize performance.

• Provide more guidance on how to setup your instances and how to scale them once you’re in cloud.

If you’re interested in learning more or making the move to cloud, reach out to our enterprise advocates. We also welcome feedback. If there are certain attributes that you would want to see in Site Optimizer, or if you’d like to have this visibility in your other Atlassian cloud products, leave a comment below.

[Mirek]

Hi @Dmitry Melikov 

Nice to hear that Atlassian is finally investing more in optimizing performance and creating native tools that would help achieve some goals. 

I am wondering only when seeing custom fields optimizer that help clean up unused fields.. Is this tool really finding unused or only those with no values? 

I know that unused CF in Jira is not so obvious.. it can have no values and it looks like it could be easily deleted but if someone delete that kind of field it could still be "used" in workflows, filters, dashboards, reports.. any many other configuration.. and after that it would break everything.. 

Many times also CF is duplicated by name (not so sure why Jira allows that even it is causing many problems) so hoping also that deleting later that kind of field would not cause any harm to data. 

[Dmitry Melikov]

Hi @Mirek , thanks a lot for your question!

In this initial release, Site Optimizer presents custom fields that aren't used in any projects, screens, or contexts. We're referring to these fields as unused and recommend that they be moved to trash.

In upcoming releases, we’re working on adding more of the criteria you mentioned, such as:
- Deleting duplicate custom fields
- Identifying custom fields that don’t belong to any issues
- Identifying custom fields that have no values

Additionally, to mitigate the risk of deleting custom fields that could be important, we will also provide an option to restore custom fields from our activity log within 60 days.

[Matt Doar]

One of the things I've found hard to track down in the past is how many issues have a non-default value. For example, if all the issues in a project have a custom field that has never been set, and so all issues have the default value, then the field is not useful. But that might be pretty hard to find out?

Perhaps looking for cases where a subset of issues all have the same value in a custom field.