• Atlassian Administration
• Jira platform
• Jira Software
• Jira Service Management
• Jira Work Management
• Jira Product Discovery
• Confluence
• Bitbucket
• Opsgenie

Differentiate between sandbox and production environments in BYOK encryption

When an admin creates a sandbox for a product encrypted with Bring Your Own Key (BYOK) encryption, the sandbox is also BYOK-encrypted. The sandbox products are labeled, to differentiate them from production environments.

To view your BYOK-encrypted products, including sandboxes:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > BYOK encryption.

Block public links with data security policies

Public links allow your team to share a Confluence page with anyone who has the link, even if they don’t use Confluence. This is very convenient, but there may be situations where you want to prevent people sharing sensitive content.

A new data security policy rule allows organization admins to control whether public links can be used in Confluence product instances and spaces covered by the policy.

When you set the public links rule to 'don't allow', all existing public links are turned off, and users are unable to turn public links on for a page.

This rule is available with an Atlassian Access subscription.

Learn about preventing public links

To set the public links rule in your data security policy:

• Go to admin.atlassian.com. Select your organization if you have more than one.
• Select Security > Data security policies.
• Select a data security policy. If you don’t have one yet, you’ll need to create one.
• Select Public Links in Policy rules on the policy screen.
• Choose Don’t allow existing and future public links, then select Save.

Once you activate the policy, any existing public links will be turned off and users won’t be able to turn on public links in Confluence products covered by that policy.

Filter the user list with added roles

We’ve updated the users list in the Atlassian Administration Directory. You can now filter the user list by new roles that have been split into multiple dropdown menus instead of one.

The roles we’re introducing include:

• Compass basic
• Jira Service Management stakeholder and customer
• Jira Product Discovery contributor

To filter the user list by roles:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Directory > Users.
3. From the Role field, select the role you’d like to filter by.

This change only applies to user list filters for centralized user management. Learn more about the centralized user management

Make it easy and secure for customers to log in to your help center with single sign-on

When you connect an identity provider to your Jira Service Management site, you can authenticate your customers with SAML single sign-on (SSO).

Before you begin
You must subscribe to Atlassian Access from your organization before you set up SAML single sign-on. Learn more about how to start with Atlassian Access

To set up SAML SSO for portal-only customers:

1. Go to Settings > Products.
2. Under Jira Service Management, select Authentication.
3. Select Add identity provider.
4. Follow the prompts to complete the setup.

Learn more about SAML single sign-on for portal-only customers

Connect Microsoft Azure AD to Atlassian with an option that works for you

When you connect your Microsoft Azure AD identity provider to an Atlassian organization, you now have two options.

Option 1: Manually set up user provisioning

Recommended when you need:

• flexibility in setting up your Microsoft Azure Active Directory identity provider with SCIM and SAML
• to sync groups and users with no flattening of nested group structure
• to sync when you add users to your Azure AD

Learn how to add an identity provider for this option

Option 2: Automatically set up user provisioning

Recommended when you need:

• easy set up by allowing access to groups and users in your Microsoft Azure Active Directory
• to flatten your nested group structure and keep group memberships
• to sync automatically (every 4 hours)

Learn more about Azure AD for nested groups

To connect your identity provider:
1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.

Learn more about identity providers

Control whether members use API tokens to authenticate

You can now control whether members can make API calls with a User API token into your organization’s products.

With this new API token setting, you can allow or block members from:

• Creating a new User API token to authenticate
• Using an existing User API token to authenticate

To try out the API token setting:

1. Log in to admin.atlassian.com.
2. Select an organization if you have more than one.
3. Select Security from the global navigation.
4. Select Authentication policies from the sidebar.
5. Select Settings.
6. Select User API tokens.

Keep track of activities for data security policies in the audit log

We’re now tracking activities for data security policies in the audit log.

Use the audit log to see key activities, like when a data security policy is created, activated, deactivated, and deleted. You can also see when rules have been added and removed from a data security policy.

We’ll be introducing new activities in the future to give you even more visibility over your data security policies.

Learn more about tracking activities from the audit log

To see audit log activities for all data security policies:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select the More actions icon (•••).
4. Select View audit log.

The audit log will show all tracked activities for every data security policy in your organization.

To see audit log activities for a particular data security policy:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select the policy.
4. Select the More actions icon (•••).
5. Select View audit log.

The audit log will show all tracked activities for your selected data security policy.

Find Atlassian Administration settings faster

You can now avoid searching every page of the Atlassian administration looking for what you need. We’ve added a new search field. From this field, you can enter a top or left navigation page title and select the page you want from the results.

To use the Administration search field:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select the search field in the top right.
3. Enter the page title.
4. Select the page you want.

Retiring the possibility to manage the atlassian-addons-project-access role

Following up on our previous announcement, we’re planning to remove the possibility to manage the atlassian-addons-project-access role in two to six months. The exact date depends on the feedback we receive after this announcement.

By default, the role is assigned to all project permissions in permission schemes and all issue security levels in issue security schemes. As a result of this change, the possibility to manage that role’s permissions and issue security levels, both via the UI and the REST API, will be restricted.

If you have any concerns about the planned changes, please leave them under this public ticket.

Create custom domains for your Jira products

We removed keyword restrictions when you create custom domains. You will no longer have a fixed list to select keywords for subdomains. Instead, you have the ability to manually enter your own subdomains.

Jira family products have also been given added support. You can now select Jira products from the dropdown menu when you create a custom domain.

To create a custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.

Confluence guest role counts towards your Access bill

We're notifying you about changes to Atlassian Access billing for people assigned to the Confluence guest role. This change applies to individuals (managed accounts) in your organization with the Confluence guest role.

The Confluence guest role makes collaborating with people outside your company more secure. You can assign the guest role to any person so they can access a single Confluence space.
Read about Confluence guest role in the community post

With Atlassian Access, you can apply security to managed accounts with the Confluence guest role. These are the settings you can enforce in a billable authentication policy:
-single sign-on
-two-step verification
-user API tokens
Understand authentication policies

We count any managed account with the Confluence guest role towards your Atlassian Access bill.
Learn how to manage your Access bill
If you prefer not to count Confluence guest users toward your Access bill, you can move them to a non-billable policy.
We won't bill you for any users in a non-billable policy.

In a non-billable authentication policy, you’re unable to:
-Enforce single sign-on
-Require two-step verification
Understand non-billable authentication policy

Activate Atlassian Intelligence for your organization's products

You can now activate Atlassian Intelligence features for your team's products. Atlassian Intelligence helps teams accelerate work, increase efficiency, and provide value faster using artificial intelligence (AI). Learn more about Atlassian Intelligence

To activate Atlassian Intelligence for your products:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Atlassian Intelligence.
3. Select Select products.
4. Choose the products where you want to activate Atlassian Intelligence features.
5. Select Next.
6. Review the products and accept the terms and conditions.
7. Select Save to confirm.

After activation, Atlassian Intelligence features will be available for users.

Update Jira and Confluence links after migrating to cloud

When you migrate from Server or Data Center to Cloud, your products start living under different URLs, which breaks most of your issue or page links. Until now, the only way to update the links between individual entities was reaching out to Atlassian Support, which doesn’t really work well with the ‘I want to do it when I want to’ approach.

With that approach in mind, we’ve built a new feature in admin.atlassian.com that lets you update all the links in your migrated products, including actual issue or page links, and also regular URLs. When and how often you do it – whether it’s after each migration or once everything lives in cloud – is completely up to you.

Learn more about updating links

To get started with this change:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Product links. You’ll see a list of products migrated to cloud.
3. For each product, run a link update and provide new destinations for links. You can do it by selecting … > Update links.
4. Watch the magic happen in your instances, and if you’re not that trustful – check the results in the audit log and history report.

Gain security insight with more charts

Get more insight into your users with four new charts. These charts allow you to see managed accounts and external users that have access to your organization, your products, and their security practices.

The new charts include domains with access to your products, users with access to your products, two-step verification for external users, and external user policy.

To access new charts:

1. Go to admin.atlassian.com. Select your organization if you have one.
2. Select Security > Insights.

Additional self-serve data residency move window options are available

When you request a data residency move, we gather information about your product, including the size of your product data. Previously, there were limited options to move data. We’re enhancing the data residency self-serve experience with new move window options across all tiers of plans.

Move windows indicate when your data residency move can be scheduled. We now offer three types of move windows:

Schedule move in the maintenance window

The move will take place during the maintenance window, and this option becomes available when the move can be safely carried out within a standard maintenance window. For this option, the estimated downtime for the data residency move is under 2 hours.

Schedule move within the next 48 hours

The move will be scheduled within the next 48 hours. This option becomes available when your estimated downtime is less than 20 hours. For example, when your estimated downtime is 19 hours, and you select this option, your move will be scheduled in the next 48 hours. We will inform you via email when the move is scheduled.

Schedule move in a 24-hour window

The move will start on the date and at the time of your choice. However, you will need to request your move at least three days in advance.

Support team will manage your move

Sometimes, we're unable to schedule data residency moves automatically. This could be due to a large amount of data or technical limitations. If we can't automatically schedule your data residency move, we will generate a support ticket after you submit your request, and our support team will help you schedule your move. You can access the support ticket on the data residency page.

To schedule a data residency move:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data residency.
3. In the data residency table, select Move product.
4. Go to Select location to select where you want to move the product. Select Next.
5. Review the information about your selected location, estimated downtime and the recommended option.
6. Select the recommended option or any other available option that you prefer. Select Next.

Data residency is now supported in six new regions

We're launching data residency in United Kingdom, Japan, India, Brazil, South Korea, and Switzerland to allow you to control where your data is stored.

There are a few limitations with these new locations. Find out more about any limitations

We're adding these locations to the list of supported locations in phases, so expect to see updates in the coming weeks.

To schedule a data residency move for the United Kingdom, Japan, India, Brazil, Switzerland, and South Korea:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data residency.
3. In the data residency table, select Move product.
4. Go to Select location, and select the desired country as the location.

Discover more about data residency

Data residency for Marketplace apps

When evaluating data residency for your apps, you might see some apps listed as "No action available."

This means that some app partners declare that their apps don't need to be pinned or migrated because their apps exclusively store data within the Atlassian product. Another reason is that the apps may not store any data in the scope of the Marketplace partner's data residency policies.

To request a data residency move for your apps, you will have first to move your product. Learn more about how to move your product from one location to another

Once your product has been pinned to your selected location, you can move your eligible apps to the same location. Learn more about data residency for Marketplace apps

Managed/Auth Policy Users Guest Users

Track the Atlassian Access cost for Confluence guests with a CSV file you export.

You can now track the Atlassian Access cost for Confluence guests. Export a CSV file in Atlassian Administration from:

-Managed accounts
-Authentication policies

Each CSV file includes the site a Confluence guest accessed, and whether or not the Confluence guest is billable for your Atlassian Access subscription
To export the CSV file for managed accounts:

-Go to admin.atlassian.com. Select your organization if you have more than one.
-Select Directory > Managed accounts.
-Select Export accounts to a CSV file.

Learn about CSV file details for managed accounts

To export the CSV file for Authentication policies:
-Go to admin.atlassian.com. Select your organization if you have more than one.
-Select Security > Authentication policies.
-Select a policy > Members.
-Select Export members to a CSV file.

Learn about CSV file details for authentication policies

Manage your product data from one central location

We're rolling out a new Data management page in Atlassian administration with a collection of features that helps you copy, store, organize, and maintain your product data from one place.

As part of this change, we've moved two features under Data management:

• Copy product data, and
• Sandbox

This means you'll now be able to access the Sandbox and Copy product data features by selecting Settings > Data management.

To access the Data management page:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Data management.

Searching for issues just got faster in Jira Cloud

We’ve modernized, optimized, and redesigned the way you search for issues. With features like smart syntax highlighting and enhanced autocomplete, the new JQL editor lets you build powerful queries for accurate search results. Configure and reorder columns to see what’s most important to you. Learn more about the new issue search in Jira Cloud

Add status while creating an issue

You can now select the status of an issue while you're creating it. For example, you could make an issue with the "in progress" status.

When selecting the status of an issue while creating it, you'll only be able to select statuses that don't have screens, actions, rules, validations or conditions in your workflow.

The new global issue create experience is enabled for all instances

We’ve modernized and optimized the experience to create issues to make it fast and scalable. Note that you won’t be able to switch back to the old experience.

Use the GitHub for Jira app to connect GitHub Enterprise, instead of DVCS

Jira admins making a new GitHub connection for a new organisation now need to install the GitHub for Jira app. The app functions just like the DVCS Connector, but with better security features and improved performance.

This only applies to new GitHub connections in new organisations. Existing connections using DVCS are not affected.

Learn more about the GitHub for Jira app.

Control what you see in your products

Product recommendations now have controls, so now you can dismiss them or learn more about why you’re seeing them. These controls are being added to the recommendations in the app switcher menu which means you'll have more control and receive better product recommendations.

You can select the three dots next to the recommendation to learn why we have recommended it or to dismiss it entirely.

The recommendation controls will first be released to both Free and Standard teams of up to 50 users. Note: Only admins will be able to add a new product by clicking on the recommendation.

OAuth upgrade for Microsoft email servers

With Microsoft deprecating basic authentication, all Microsoft mail servers need to be reconfigured using OAuth. OAuth simplifies your sign in process and is more secure compared to basic authentication.

To configure your Microsoft mail server using OAuth:

1. In the Navigation bar, select Settings > System.
2. Select Incoming mail.
3. Select Add incoming mail server.
4. Give your mail server a name and description.
5. Select Sign in with Microsoft.
6. Select Add.

Learn more about how to configure your mail server.

Update to the create issue mini window

We've updated the look and feel of the create issue mini window.

Next time you're creating an issue, you can use the icons on the top right of your issue to exit full screen and use the re-designed mini window. You can also click the background outside the issue you're creating to exit the full screen view.

With the mini window, you'll be able to create work in context and navigate your project without losing progress on your new issue.

Developers can now quickly determine what to work on next with automated suggestions

When you're in the middle of a sprint and you finish a task, it can be hard to know exactly what to do next. Automated suggestions from connected tools are specifically chosen for you based on work on your board. This will help you decide which tasks to do next and keep momentum. This is an alpha release available in team-managed projects.

1. Go to your Jira board and select your avatar.
2. What to work on panel will slide open with your customized suggestions. Hover over any of the suggestions to see tooltips with more information.
3. Select the call to action if you want to work on the suggestion.

Early access program: Customize priorities for your projects

As a Jira admin, you can configure priorities that work best for projects so that your team can select the right priority for their issues. Learn more about priority schemes.

Sidebar responds to small windows or higher-zoom views

If you view Jira in a small window or at higher zoom levels, the sidebar now changes sizes to keep all controls in view. In these smaller windows, the sidebar no longer opens on hover to avoid accidental opening.

The sidebar is unchanged in views wider than 768 pixels.

When viewing Jira in a window narrower than 768px or zoomed in at 200%, you'll notice that hovering your cursor over the sidebar no longer expands the sidebar.

To open the sidebar, select the expand sidebar button ( > icon). Select the button again to collapse the sidebar. You can also select the edge of the sidebar itself to expand and collapse it.

Custom navigation colors are now compatible with dark theme

If you've set a bright custom color for your navigation bar, we'll automatically modify it for anyone in your site using dark theme.

Work more securely with your collaborators in Jira Cloud

Keeping privacy and security in mind, the Browse projects permission lets users in a project see a list of recommended users for fields like mentions, reporter, watchers, custom user field, custom multi-user field, custom people fields, and approvers. Learn more about restricting global permissions to users and groups

Retiring the possibility to manage the atlassian-addons-project-access role

Following up on our previous announcement, we’re planning to remove the possibility to manage the atlassian-addons-project-access role in two to six months. The exact date depends on the feedback we receive after this announcement.

By default, the role is assigned to all project permissions in permission schemes and all issue security levels in issue security schemes. As a result of this change, the possibility to manage that role’s permissions and issue security levels, both via the UI and the REST API, will be restricted.

If you have any concerns about the planned changes, please leave them under this public ticket.

Better results with improved custom field support

We've added support to custom field types such as select list fields (single choice, multiple choice, and cascading), radio buttons, checkboxes, labels, date and date time pickers, version picker, project picker, user and group pickers, number, and URL.

To get started with this change:

1. Go to your project's sidebar.
2. Select Issues.
3. Select More+ to use these fields.

Issues and comments created from an unknown email will now use Default Reporter

Our Jira Incoming Emails component has had an update. When an email is received from an unknown email address, and the sender isn’t a Jira user, a new user will no longer be created. The person you selected in your settings as the Default Reporter will be used instead when creating an issue or comment from an email.

Display issues in a table

We're rolling out improvements to how you display Jira issues in descriptions or comments. The new experience allows you to search for issues using filters, keywords or JQL, and flexibility to add, remove, and reorder fields.

To insert Jira issues:

1. Type /jira and select Jira issues.
2. Search for issues with either:
   • Filters - Use filters to narrow down your search
   • Basic - Type in keywords to search for issues
   • JQL - Use Jira Query Language (JQL)
3. Select Insert issues.

This will display your selected issues in a table format you can interact with.

To edit your table of Jira issues:

1. Select anywhere on the table.
2. Select the Edit button (left-most icon) from the menu that appears at the bottom of the table.
3. Edit your search query.
4. Select Insert issues.

Import your data into Jira as issues

Moving your work into Jira Software is now faster and simpler. With the new CSV importer, you can easily transfer information from tools such as Asana, ClickUp, and GitHub into Jira Software, allowing you to start working more quickly. 

To import your data,

1. Select Projects > Create project,

2. Select Import data to a new project,

3. Upload a CSV file.

The information will appear as issues in the Jira Software project.

Automation: Create sprint action

You can now create sprints in your scrum boards using Atlassian Automation using the "Create sprint" action.

For example, you could set up an automation rule to automatically create a new sprint every two weeks.

Learn more about the Create sprint action

To give this a try:

1. Navigate to Automation in Confluence Cloud or Jira Cloud.
2. Select Create rule.
3. Choose a trigger for your rule, and then select the Create sprint action.

You'll also need to set up a connection to your Jira project - Learn more about connections in automation

organisation-domains-ui-improvement

We're making some small visual improvements when viewing customer organizations from your service project. This is found by navigating to Customers then selecting an organization from the list.

When adding a customer to an organization, you can now search for existing customers via their email addresses or display names, where previously you would need to know the exact email address.

The Edit organization name, Remove organization from project, and Delete organization have been moved to a More actions menu and are still available.

Create new Confluence pages or Jira issues using /create

We've made it easier to create new Confluence pages or Jira issues while editing a description or comment.

To create a new Jira issue using /create:

1. From Jira descriptions or comments, type /create jira.
2. Select Create Jira issues.
3. Enter issue details then select Create.

To create a new Confluence page using /create:

1. From Jira descriptions or comments, type /create confluence.
2. Select Create Confluence page.
3. Enter page details then select Create.

Removed object IDs in Assets screens

As part of the ongoing efficiency work to support increasing the number of objects supported in Assets, we’re removing the ID fields from the following screens: attribute ID from object types, schema ID from schema configuration, status IDs from schema configuration, and status IDs from global schema configuration.

This change is backward compatible and will not affect any existing AQL queries or automation rules.

New ways to manage email notifications from Jira

We've moved notification preferences out of your Personal settings page into its own Notifications space where we can continually develop ways for you to take control of your Jira notifications.

We've also replaced the old notification configurations with six new ones, so you can choose what notifications you actually want to receive for the issues you're watching.

To see the change:
Select your profile and settings icon, then select Notifications.

Custom name for Story points now shows in plans

For those who've configured their site to use a custom name for the story points value, that custom label will now show in all places that previously used "Story points" in plans.

Know when you have new work suggestions

Introducing a bubble notification on the work suggestions button when you have tasks in the panel.

1. Go to your Jira board.

2. Find the button next to your avatar.

3. You'll notice a blue bubble if you have work suggestions available.

4. Select the button to open the work suggestions panel and view the added tasks.

Move data between sites with cloud-to-cloud migration

We're introducing cloud-to-cloud migration to make it easier for you to move users and projects from one cloud site to another. Cloud-to-cloud migration can help you combine data between two or more cloud sites, split a cloud site into multiple cloud sites, duplicate a cloud site, or move specific projects from one cloud site to another.

Org and site admins can access this feature by logging in to the cloud site you want to move your users and projects from, then going to Settings > System > Migrate cloud site.

Updates to how you create projects in Jira

Creating projects in Jira is now simpler with our new template library. Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works.

Additionally, we’ve renamed our project types (next-gen and classic) to make them clearer and more descriptive:

• Next-gen projects are now named team-managed projects. The functionality itself remains the same and continues to be ideal for independent teams who want to control their own working processes and practices in a self-contained space.

• Classic projects are now named  company-managed projects. Setup and maintained by Jira admins, company-managed projects remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow.

Advanced Roadmaps - New navigation

Advanced Roadmaps has a new look that makes it look and feel more like the rest of Jira Software.

To state it simply, the nav now lives on the left-hand side. This new layout opens Advanced Roadmaps up to a whole new world of designs and new features (whoops, not sure if I was supposed to say that 🤭).

Even though this is rollout to all users, we'd still love to hear your thoughts about how it effects your work, or your ideas for improvements. Use the Give feedback button which is still located in the upper right of your screen.

If you opted in the Early Access Program from last month, you won't notice a change. However, this layout is now the new default view for Advanced Roadmaps and can no longer be disabled.

Read more about these changes in our community post.

Connect Google Drive in Project Pages

Project pages previously only connected to Confluence. Users can now connect and view Google Drive files from within Jira

Any updates made to Google Drive files within Jira are automatically synced, ensuring that all team members are working with the most up-to-date information.

The integration provides an option to search for and link existing Google Drive files to Jira issues, making it simple to associate relevant files with specific tasks.

To get started with connecting Google Drive to Jira Software:

If you’ve never used project pages before:

1. Select Connect Google Drive
2. Select sign in with Google
3. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
4. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project
5. Select connect shared drive

If you have Confluence connected to project pages:

1. Select the Add Google Drive tab
2. Select Connect Google Drive
3. Select sign in with Google
4. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
5. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project.
6. Select connect shared drive.

That’s it! Once you’ve connected a shared Google Drive to Jira, it will be synced to your Jira project.

Organize and track work against Compass software components

You can now link issues to Compass components from any company-managed Jira Software project.

This helps your team organize and track work in Jira against elements of your software architecture cataloged in Compass – so you can understand the impact of that work; prioritize work more effectively; and find the information you need to get that work done faster.

Learn more about Compass components

Switch to Compass components (project admins)

1. In your project sidebar, select Components.
2. Check that Compass components are turned on. Next to Create component, it should say Compass components. If it says Jira components, select it and switch to Compass components.
   • Jira components won't be deleted, and they'll still be visible on issues they were previously linked to. You can switch back to Jira components at any time.

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

1. On the Components page, select Get Compass free. It'll take a couple of minutes to set up.
   • Only site admins can do this; if you're not a site admin, you can send a request to your site admin to get Compass.

If you have Compass, but don't have any software components:

1. On the Components page, select Create component. Compass will open in a new tab.
2. Fill out the information for the new component, including the name, type, owner team, and related source code repository link. Read more about creating Compass components
3. Open any issue in your project.
4. Select the Components field, and choose the Compass component you want to link to the issue.
5. The component and its linked issue will appear on your project's Components page; and you can search for the component in the backlog, boards, and issue navigator.

If you have Compass, and have software components:

1. Open any issue in your project.
2. Select the Components field, and choose the Compass component you want to link to the issue.
3. The component and its linked issue will appear on your project's Components page; and you can search for the component in the backlog, boards, and issue navigator.

Read the full documentation

Connect pending Bitbucket workspaces on the Code page or the development dialog

If someone in your team has begun the process to connect Bitbucket with your Jira site, you can now complete the connection process on the Code page or in the development dialog. You must be a Jira admin to do this.

To connect pending Bitbucket workspaces on the Code page:

1. Go to Code in your project menu.
2. Select Connect workspace in the blue banner to connect a workspace.

To connect pending Bitbucket workspaces using the development dialog:

1. Navigate to an issue in your project.
2. Open the development dialog by selecting either a branch, commit, pull request, build, or deployment from the development panel.
3. Select Connect workspace in the blue banner to connect a workspace.

Read more about integrating Bitbucket with Jira

Refine your board with quick filters

Refine the issues that appear on your board by creating a quick filter based on Jira Query Language (JQL).

This is a refreshed experience — the modernized UI is also more accessible and we've improved the overall UX to make filtering snappier and simpler.

To create a quick filter, navigate to your board, then select More ... > Configure board. Find the Quick filters page, then select Create quick filter.

Change Atlas goals assignments from your plan

In December, we rolled out the ability to view Atlas goals on your plan. With the rollout of this feature, you can now change the value of the Atlas goal field in your plan to realign your work with different goals.

Track and triage incidents affecting your services in Jira

We’re excited to roll out the new incidents feature in Jira Software Cloud.

This feature pulls in data from connected incident management, monitoring, and observability tools, so your development team can have a holistic view of incidents impacting services they are responsible for.

Our first supported product is Jira Service Management, and we plan to add support for more incident management and observability tools soon.

By turning unexpected incidents into manageable, visible work, you can improve your team’s focus on quick resolution and internal review while building proactive work practices to prevent incidents from happening again.

To get started with the incidents feature:

For some customers who use Jira Service Management, the feature will be available and automatically appear under Operations in the list of features.

To turn it on manually:

1. Go to Project settings > Features.
2. Toggle Incidents on.

We're gradually rolling out the incidents feature over the next few weeks to specific customers. If you don't see it yet, check back again soon.

Finish setting up your development tools from the issue view

Jira site admins can now finish setting up code and deployment tools by following a link from the issue view. If any site admin has installed a tool on your site, we'll show a link on the development panel so you can finish setting it up.

If a code tool has been installed but not configured, we'll show a link to Set up code tools.

If a deployment tool has been installed but not configured, we'll show a link to Set up deployment tools.

To get started:

1. Go to your Jira project and open an issue.
2. In the development panel, select Set up code tools (or Set up deployment tools).
3. In the dropdown, select the tool you want to set up.
4. Follow the steps to finish setting up your integration.

Move plans to trash instead of deleting them

When you delete a plan, it's now held in the trash for 60 days before being permanently deleted.

This differs from before when planners would select Delete, confirm their decision, and the plan would disappear like Andy Dufresne from Shawshank Prison.

Find out how to delete a plan using this new, less destructive manner

Work suggestions for critical vulnerabilities now available in Jira

View critical vulnerabilities on your work suggestions panel. These will be related to issues in your sprint.

1. Go to your Jira board.

2. Select your avatar.

3. Your work suggestion will open. Look for a critical vulnerability suggestion and select the card to view more information.

Updates to how you create projects in Jira

Creating projects in Jira is now simpler with our new template library. Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works.

Additionally, we’ve renamed our project types (next-gen and classic) to make them clearer and more descriptive:

• Next-gen projects are now named team-managed projects. The functionality itself remains the same and continues to be ideal for independent teams who want to control their own working processes and practices in a self-contained space.

• Classic projects are now named  company-managed projects. Setup and maintained by Jira admins, company-managed projects remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow.

Make it easy and secure for customers to log in to your help center with single sign-on

When you connect an identity provider to your Jira Service Management site, you can authenticate your customers with SAML single sign-on (SSO).

Before you begin
You must subscribe to Atlassian Access from your organization before you set up SAML single sign-on. Learn more about how to start with Atlassian Access

To set up SAML SSO for portal-only customers:

1. Go to Settings > Products.
2. Under Jira Service Management, select Authentication.
3. Select Add identity provider.
4. Follow the prompts to complete the setup.

Learn more about SAML single sign-on for portal-only customers

New project details page for company-managed service projects

We've redesigned the project details page for company-managed projects to match the clean, sleek look of our team-managed project details page. As part of this update, you can also enjoy more formatting options for the project description.

Introducing a new workflow editor in company-managed projects

We're building a new workflow editor for your company-managed projects!

If you're familiar with team-managed projects, you might be familiar with the new workflow editor - it's a faster, cleaner, more intuitive experience for creating and editing your workflows.

In our first release, we're making the new editor available for Jira Service Management projects so you can start using it right away, but we still have more work to do to bring across all the features from the old workflow editor.

While we continue building the new editor, you can switch between editors as needed using the Open in old editor or Open in new editor options. You can also select a default editor so that your workflows always open in the editor of your choice. Just select Change default editor and follow the steps to make your choice.

If you have feedback on your experience with the new editor, we'd love to hear it. Make use of the feedback options in the editor to let us know your thoughts.

Learn more about the new workflow editor.

Improved search results in your help center

Your help center's search results will now also include links to external resources that you've added to your service projects. This means customers can find links to useful self-service articles and more from tools outside Jira Service Management in your help center, making their search experience more comprehensive and efficient.

Find out more about adding external resources to your service project.

Usage tracking for features

Ever wonder just how many objects you've got in Assets? How many schemas? Or maybe how many people are having conversations with your virtual agent? Well, wonder no longer! Now you can track your usage for certain Jira Service Management features such as Assets and virtual agent in one easy location.

To track your usage in a given feature:

• From the top right of your screen, select Settings (cog) > Products.
• Under Jira Service Management, select Feature usage.
• View the Assets tab for the number of schema objects and schemas.
• Otherwise, select Virtual agent for the number of assisted conversations and conversations.

Add anyone as a stakeholder, no agent license needed

We’re introducing the stakeholder role in Jira Service Management. Now you can add anyone as a stakeholder.

If you’d like someone to be informed about an incident’s progress to take necessary precautions and actions, add them as a stakeholder. They’ll only receive updates about incidents, and won’t have product access.

This feature is available only on Premium or Enterprise plans of Jira Service Management.

Read more about adding stakeholders

You can assign users a Stakeholder product role on Jira Service Management, through Atlassian Administration > Directory. You can invite new users or assign existing users as stakeholders.

Chat in Slack: Emoji shortcuts are now powered by Jira automation

Emoji shortcuts, based off Halp’s legacy recipes, now use Jira automation’s powerful no-code engine. With this change, admins can manage all automation rules in one place and emoji reactions can be used to edit issues created by Assist in Slack — all allowing for a simpler configuration experience.

If your projects have custom emoji rules, you have until June 4, 2024, to set up similar ones in automation. After that date, the emoji shortcut feature in chat settings will no longer function.

Find out more in our Community blog

Before you start setting up your new automation rules, keep in mind:

• The ticket emoji shortcut used to create issues isn’t affected by this change, so you don’t need to set this up in automation.
• You need to set up the eyes emoji shortcut, which assigns agents to issues. Tip: Use the template from the Emoji shortcuts tab in chat settings to quickly set up this automation.

To set up emoji rules in automation:

1. From your project settings, select Automation.
2. Select Create rule.
3. Select Emoji reaction to Slack message as your trigger*.*
4. Select Turn on rule, name your rule, and then Turn on rule again to save.

To help test your new emoji rules, you can now turn off emoji shortcuts in chat without deleting them:

1. Set up your emoji rule in automation.
2. From the Emoji shortcuts tab in chat settings, find the rule to turn off.
3. Use the toggle to turn off the rule.
4. Test to your satisfaction.

Connect Google Drive in Project Pages

Project pages previously only connected to Confluence. Users can now connect and view Google Drive files from within Jira

Any updates made to Google Drive files within Jira are automatically synced, ensuring that all team members are working with the most up-to-date information.

The integration provides an option to search for and link existing Google Drive files to Jira issues, making it simple to associate relevant files with specific tasks.

To get started with connecting Google Drive to Jira Software:

If you’ve never used project pages before:

1. Select Connect Google Drive
2. Select sign in with Google
3. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
4. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project
5. Select connect shared drive

If you have Confluence connected to project pages:

1. Select the Add Google Drive tab
2. Select Connect Google Drive
3. Select sign in with Google
4. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
5. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project.
6. Select connect shared drive.

That’s it! Once you’ve connected a shared Google Drive to Jira, it will be synced to your Jira project.

Colourful categories

Project admins can now assign colours to categories from the list view in Jira Work Management.

Manage custom fields for your project in context of the list view

You can now create and manage custom fields in context of the list view. Certain types of work may require specific information for your team to get the job done. Jira Work Management now allows you to create and manage these additional fields in context of the list view to save you from navigating away from your work. This will help your team with viewing the right, relevant information upfront when completing tasks.

To get started with the change, select the plus symbol at the top right of your list view to show or hide more fields, and manage your custom fields.

See all your attachments in one place

We’re introducing a new view so you can see any attachments added to issues in your project. This means you no longer need to search through issues to find a specific attachment.

We’re slowly rolling out this feature, so don’t worry if you can’t see this yet.

If this is already available for you, you can see all the attachments in your project by selecting Attachments from the project view navigation.

From Attachments, you can download an attachment by hovering over it and selecting the download button that appears. You can delete an attachment by hovering over it and selecting the delete button, which removes it from Attachments and the issue it was attached to.

More background colors

We've added more colors to our background palette. Now you have a wider range of options to create your project's identity and overview.

Project background: select the option next to your project's name and choose a color.

Jira Work Management overviews: the new colors will appear on the creation screen.

Template bundles in the project create page

Effortlessly create between 2 to 6 projects at once, with bundles. We're helping streamline your project creation process and minimizing the need for repetitive manual tasks. Whether you're working in Jira Work Management, Jira Software, or Jira Service Management, bundles guarantee a smooth project creation experience.

Choose from two pre-set bundles: the Marketing or the IT team bundle. And if they don't fit your requirements, you have the flexibility to customize and create your own bundle.

There are a few ways you can create a bundle, one way is to:

1. Select the plus icon + in the project sidebar
2. Choose More templates from the dropdown
3. Select Bundles

Another way to create a bundle is to:

1. Select Projects > Create project in the top navigation bar
2. Select Bundles

Use the GitHub for Jira app to connect GitHub Enterprise, instead of DVCS

Jira admins making a new GitHub connection for a new organisation now need to install the GitHub for Jira app. The app functions just like the DVCS Connector, but with better security features and improved performance.

This only applies to new GitHub connections in new organisations. Existing connections using DVCS are not affected.

Learn more about the GitHub for Jira app.

Calculate delivery progress based on story points

With enhanced calculation options, the delivery progress can now better reflect the size of your linked delivery tickets in Jira Product Discovery. You can easily configure the field to display progress based either on the number of issues per status or on the number of issue story points per status.

Creators can configure the delivery progress field:

1. Click the Delivery progress field to open the Delivery tab, or select a specific idea and go to the Delivery tab.
2. On the Delivery tab, click the delivery progress bar, and then select Configure delivery progress.
3. From the dropdowns, choose the most suitable options to display the delivery progress:
   1. Default or Simple for the estimation type
   2. Issue count or Story points for the estimation values

Learn more details about the estimation rules and configuration options.

Send a notification when changing content restrictions

Let people know they've been added to a restricted page. Now whenever you add a person or a group to the Restrictions settings of content, you'll see an option to notify the newly added people about their access. This will send a system notification from Confluence.

If you'd like to add context to the notification, try using the Share button or copy the link to the content and include it in a chat message or email.

Or if you just want to change access without notifying anyone, simply uncheck the checkbox in the lower left that appears when you add a person or group.

Default data classification levels get migrated

When organization administrators migrate a space or Confluence instance, default data classification levels migrate as well.

This preserves related rules around creating, storing, managing, moving, or deleting page and blog data in each space — without space administrators needing to reset a default.

Learn more about data classification

Data classification is currently only available through the Atlassian Information Security Beta program. If you’re not part of the program, subscribe to our Cloud roadmap to be informed when this feature becomes generally available.

Customize and display the child pages macro with enhanced control and ease

You can now find, customize, and display the Child pages macro (formerly known as "Children Display") more easily than ever thanks to the following updates:

• New and improved name and icon for instant discovery.

• A simpler, more intuitive configuration experience with separate Basic and Display config tabs.

• Clearer in-product guidance around setting up and customizing this macro.

Confluence Premium: Better content management

The area formerly known as bulk archive has been updated and moved under Space settings, Manage content. We’ve added more table information and filters, allowing space admins with Confluence Premium or Enterprise to assess the state of their content before applying actions, like archive or delete, to hundreds of selections at a time.

An Inactive pages button filters pages that don’t have children and haven’t been viewed, updated, or commented on in a specified time frame. Selecting the All content button includes whiteboards in your results.

Up to 500 items can be archived at once, storing them in the archive for future reference. Up to 100 items can be deleted at one time, moving them to the trash.

Learn more about the content manager

Go to Space settings > Manage content > Manage content tree.

To filter inactive pages, go to Manage content tree, select Inactive pages, and select a time frame.

Be more expressive with panels

In addition to the five preset panel options, you can customize panels by choosing one of the 20 background colors available.

Panels can have emojis, or you can remove the emoji to meet the needs of your content. The emojis available to you are the same set that you already use in Confluence; this includes custom emojis you and your teammates added.

1. Add a panel to a page by typing /custom panel or by selecting Custom panel from the insert menu.

2. Use the floating toolbar to choose a background color and pick an emoji if you want one.

Automatically get a personal space

A personal space in Confluence is a place of your own to jot down new ideas, introduce yourself to your team, keep track of tasks, store important items or files, polish content before sharing with others, and more.

You can choose to leave the space open for others to visit and collaborate, or you can restrict the pages so that no one else can see them.

If you don't already have a personal space, one will be created for you after you've logged in and viewed a page. There are three ways to get to your personal space:

• Select Spaces in the global navigation bar. Your personal space is automatically starred for easy access.
• Select your profile icon at the top right of the global navigation bar and select Personal Space.
• Select Home in the global navigation bar. All starred spaces are shown on the right.

Learn more about personal spaces

Transfer of page ownership between users

When a page is created, the person who creates is now known as the owner of that page. We've made it possible for page owners to transfer ownership of their page to another person at any time. Space and site admins can also transfer page ownership from one user to another.

This way, if a current page owner leaves a project, team, or company, ownership of the page can then be granted to whomever is most appropriate, and maintenance and validity of the page remains fresh.

A page owner is the ‘point person’ for a given page and their name appears in the byline, under the page title.

Learn more about page ownership and how it can be transferred

Control what you see in your products

Product recommendations now have controls, so now you can dismiss them or learn more about why you’re seeing them. These controls are being added to the recommendations in the app switcher menu which means you'll have more control and receive better product recommendations.

You can select the three dots next to the recommendation to learn why we have recommended it or to dismiss it entirely.

The recommendation controls will first be released to both Free and Standard teams of up to 50 users. Note: Only admins will be able to add a new product by clicking on the recommendation.

Sidebar responds to small or higher-zoom views

If you view Confluence content in a small window or at higher zoom levels, the sidebar now changes sizes to keep all controls in view. In these smaller windows, the sidebar no longer opens on hover to avoid accidental opening.

The sidebar is unchanged in views wider than 768 pixels.

When viewing a Confluence page in a window narrower than 768px or zoomed in at 200%, you'll notice that hovering your cursor over the sidebar no longer expands the sidebar.

To open the sidebar, select the expand sidebar button ( > icon). Select the button again to collapse the sidebar. You can also select the edge of the sidebar itself to expand and collapse it.

Template suggestions in the page editor

When creating a new page, you start off with popular templates featured first.

Once you begin adding a title to the page, these featured templates will be replaced by suggested templates: templates that may be a better match for your needs based on the title you entered.

1. Create a new page.
2. Start typing a page title.
3. Recommendations of popular templates will be replaced by suggested templates, based on the title you've entered.

Open Beta: Surface your Assets objects in Confluence

Surfacing your Assets for Jira Service Management objects in Confluence is now available in Open Beta!

This means your Assets data can now be easily accessed and viewed directly from within a Confluence table, making your workflow more efficient and getting information to the people who need it, when they need it.

To use this feature, you must be a Jira admin and / or have permissions to see the relevant object schema in Assets in Jira Service Management as well as an active Confluence licence in order to see the schema and manage this macro in Confluence..

To embed a table with Assets objects:

1. Navigate to a Confluence page you own.
2. Enter / on your keyboard.
3. Search for Assets (Beta) in the dropdown menu search bar, then select Assets (Beta).
4. Select Insert objects from.
5. Choose the object schema that stores the objects you want to display.
6. Enter an AQL query to filter down the objects you want to be displayed. Learn more about AQL queries.
7. Select Insert objects.

Learn more about displaying Assets in Confluence

Confluence Premium: Discover automation in context

Space administrators with Confluence Premium and Enterprise will find it easier to learn when automating common Confluence actions could save them time. An automation prompt appears after a space admin archives a page from the content tree, hovers over a page that hasn’t been updated lately, adds a label to a page, or publishes a page title with the word “meeting”.

Each prompt links to a related rule template in space automation, which require little to no configuration to build.

Learn more about Confluence automation

Confluence Premium: 20 new automation components

Confluence automation is adding 12 new trigger and 8 new action components.

Space, product, and site administrators can use components to build rules that automatically organize content and manage team workflows. Automation is available in Confluence Premium and Confluence Enterprise.

Learn more about creating automation rules

Reactions replace likes in Confluence home feed

You can now add, delete, and view reactions in the Confluence home feed, as well as see who reacted to content.

This will make it easier for users to collaborate and express themselves.

Space permissions get some look and feel improvements

We've made some small improvements to the look and feel of space permissions, most notably to break the long page into tabbed sections so you don't have to scroll so much. There are now separate tabs for Users, Groups, Guests, and Anonymous access.

As part of this change, we've also upgraded our technical stacks to allow for more significant UX improvements to space permissions experiences in the future.

Restore and reattach inline comments, even after deleting highlighted text

Inline comments anchored to highlighted text can get resolved when that text is changed or deleted during an editing session. It is now possible to restore those comments by reattaching them to selected text in the editor.

Resolved comments can be accessed from the More actions menu on the toolbar. Find the resolved inline comment you want to restore, and select Restore comment.

In the editor, highlight text you'd like to add the comment to, and select Add comment.

Automation: Create sprint action

You can now create sprints in your scrum boards using Atlassian Automation using the "Create sprint" action.

For example, you could set up an automation rule to automatically create a new sprint every two weeks.

Learn more about the Create sprint action

To give this a try:

1. Navigate to Automation in Confluence Cloud or Jira Cloud.
2. Select Create rule.
3. Choose a trigger for your rule, and then select the Create sprint action.

You'll also need to set up a connection to your Jira project - Learn more about connections in automation

Confluence administration updates

Confluence administration has long contained more than settings. We made updates to reflect that and make everything easier to find.

When product admins select the gear icon in the top-right of Confluence navigation, they’ll see new hierarchy in the side navigation, distinguishing monitoring capability from premium admin tools from settings. The settings themselves are now collapsed into more manageable, expandable, buckets — and are searchable by keyword.

Confluence admins should continue to select the Confluence administration gear (formerly Settings) in the top-right of Confluence navigation.

Nested actions now available on Confluence Standard

Nested actions, previously available as premium functionality, are now available on all paid plans. This allows users with Confluence Standard to archive or delete entire branches of the content tree at once.

Up to 500 nested pages and/or whiteboards can be archived together.

Up to 100 nested pages and/or whiteboards can be deleted together.

Learn more about archiving content or deleting content

1. Find a parent item in the content tree and hover over the title
2. Select More actions (•••)
3. Select Archive or Delete
   1. ) A screen will inform you how many nested items there are
4. Check the box to include them
5. Follow the remaining prompts to either Archive or Delete them

Global App Switcher - Changes to UI & Functionality

We're working to bring Atlassian Organisations to the forefront for our users by including them in the Atlassian App Switcher. As part of this work, we're adjusting a few elements to improve the overall usability of the App Switcher. Please note that these changes will be rolled out slowly, so there may be differences in the App Switcher between products.

What products will this change affect?

• Bitbucket
• Admin Hub
• Atlas
• Analytics & Visualisation Platform
• Compass
• Start
• Billing Platform (Purchasing)

Key changes:

• The switcher is now filtered by Organization > Product > Site (previously was Product > Site).
• Atlassian Start is no longer a standalone hyperlink, and instead will appear under Your Apps.
• Clicking on an app or product will now open it in a new tab.
• We’ll show you recommended apps under Recommended for your team. However, if you have all apps installed now, you’ll be shown the Discover section instead.
• Removal of the More section which used to show custom links.

These changes should:

• Create a more seamless flow when you switch between Atlassian products.
• Make it easier to identify which organization owns the products you’re using.
• Increase security by letting you know when you're leaving your current organization's workspace.
• Reduce noise when selecting an app - you’ll no longer see apps and sites associated with other organizations.

Join the conversation and give us early feedback

Cache key support for self-hosted runners

Since releasing cache key support for builds on the Atlassian infrastructure earlier this year, we have been actively working to add cache key support for our customers who are using runners. That being said, we are happy to announce that we now support runners using cache key to generate caches. Additional documentation on smart caches with cache keys can be found in the following section of our Caches help documentation: Caching with file-based cache keys.

We’ve made it easier for you to set up and work with integrations

We’re introducing a new, streamlined integration framework offering an improved user experience. The framework is designed to simplify the installation and configuration of integrations while offering greater flexibility in the processes.

The initial setup and configuration steps are now more organized, with each having its own separate space. To keep things neat and tidy, the configuration page has been decluttered. You'll also find that advanced incoming rules have been integrated directly into the main configuration section, bringing everything together in one place. We've improved the readability of incoming and outgoing rules and the process of setting them up and editing them.

Learn more about the Opsgenie integration framework