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

Monitor usage of user API tokens in your organization

We're giving you the ability to see user API token usage in one place. User API tokens allow the users in your organization to call Atlassian product APIs to access product data. You can track these details about user API tokens only for your managed accounts:
-Token name
-Created by
-Date created
-Last active
Tracking these details for external users is not yet available. External users have email addresses with a domain you don't manage.

To view user API tokens:

1. Log in to admin.atlassian.com > Security
2. Select User API tokens.

BYOK-encrypted products view

Bring Your Own Key (BYOK) encryption for Jira Software is available to customers with Enterprise plans.

Once you have BYOK encryption set up for products, you can view the products and their details. You can also see whether your BYOK-encrypted products are offline as a result of revocation of access to keys.

To set up and create a BYOK-encrypted product, contact your Atlassian Enterprise account representative. Learn how to set up BYOK encryption

To view your BYOK-encrypted products:

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

Take control of your domain’s user accounts

We’re giving you more flexibility to manage user accounts for your domains. You’ll be able to control how and what specific user accounts you’d like to manage.

When you verify your domain, you can:

• Choose how to claim new users for a domain — automatically or manually

• Choose to claim all users or some new users for a domain

Learn how you currently verify a domain

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

Add a custom domain for your help center

Use your own domain for the Jira Service Management help center. For example, your customers could use 'customer.support.acme.com/<path name>' (or optionally be redirected from 'support.acme.com') instead of 'acme.atlassian.net/<path name>' to access the help center.

Enjoy stronger brand recognition for your help center, boost credibility and search engine optimization, and offer a customized experience to your help seekers. This greater discoverability will help your customers get to the right place and get the assistance they need.

This feature is currently in beta, and is rolling out gradually to organizations. There are a few limitations to be aware of, and your fully qualified domain name will need to follow a specific pattern. Learn about custom domains

To add 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 the Custom Domains tab.

From here you can add a new custom domain and see all custom domains configured in your organization. Custom domains is available for Jira Service Management Standard, Premium, and Enterprise plans.

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.

Organization Insights enhances visibility to your organization’s security posture

The new chart for two-step verification chart for managed accounts provides information about how users are logging in to their Atlassian account. It shows the number of managed accounts that don't have two-step verification enabled, those that have two-step verification enabled, and those that are managed under single sign-on (SSO). Learn more about organization insights

To help increase your organization's secure logins, you can:

• Encourage individuals to enable two-step verification in their Atlassian Account settings
• Implement an authentication policy that requires two-step verification for all managed accounts (available with Atlassian Access)

To access the new chart for two-step verification status for managed accounts:

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

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.

Find out exactly when new features rollout to your products

We’ve improved the way you see rollout information for changes to your products.

With real-time release information, you’ll know exactly when a release is available in your products.

We’ve updated release note statuses:

• PLANNED
  Atlassian is working on a change. There’s no rollout date scheduled.
• COMING SOON
  Atlassian is rolling out a change, but your products haven’t received it yet.
• ROLLING OUT (for multiple product instances only)
  A change is being rolled out by Atlassian, and only some of your instances have received it.
• ROLLOUT COMPLETE
  All your products have the change.

For organizations with multiple products on the same URL, you can now drill down view of your individual products. From the release note details page, select View rollout schedule and see which products have received the change while it’s rolling out.

Control when and how often your external users must verify their identity

We’re improving external user security settings to give you more flexibility and control. You can now take advantage of these new external user security settings:

Verification frequency

You’re able to apply verification frequency in an external user or test policy.

You can change how often an external user needs to verify their identity before they can access products like Jira or Confluence in your organization. You can choose to verify for a period ranging from 15 minutes to 30 days.

Reset sessions

You’re able to reset sessions for all external users in your organization. This means external users need to verify their identity the next time they access products like Confluence or Jira in your organization.

Learn more about external user security

To reset sessions:

1. Log in to admin.atlassian.com > Security > External users
2. Select a policy.
3. Select Reset sessions.

To update verification frequency:

1. Log in to admin.atlassian.com > Security > External users
2. Select a policy.
3. Select Verification frequency.
4. Update Verification frequency.

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 is a virtual teammate that helps your organization work more efficiently with artificial intelligence. 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 your users to be able to use Atlassian Intelligence features.
5. Select Next.
6. Review the products and accept the terms and conditions.
7. Select Save to confirm.

When you activate Atlassian Intelligence for your products, some features may not be available yet but will be soon.

Stay up-to-date with new releases in Product updates

We’re now sorting release notes by Date modified. On the Product updates list, release notes will appear in order by the date we publish a new release note or the date we change the status of an existing release note.

For example, when the release note changes from ROLLING OUT to ROLLOUT COMPLETE, it will move to the top of the list.

To view all the latest changes to your products, filter for status ROLLOUT COMPLETE. To view changes to your products on certain days or periods, use the Date modified filter to select your dates.

Easier access to the products your team needs

People who aren’t admins can try Jira Service Management without having to send a request to their admin. The admin(s) will get an email and notification when it happens.

This change is only available if someone is on a Free site and wants to try a Free product. Only one person can try Jira Service Management. They can’t add other users and won’t have admin permissions.

This means it’s easier for people to access the Atlassian tools that they need, and try them out for free.

Admins can always go to admin.atlassian.com to edit user and product permissions.

Migrate Jira users and groups in advance

We’ve added a new card to the Jira Cloud Migration Assistant home screen that lets you migrate Jira users and groups before project data. When using this option, you can migrate:

• All users and groups

• (Optional) Group membership

• (Optional) Jira Service Management customers

We recommend that you migrate users in advance, especially in large instances, because it can reduce downtime during your actual data migration. Once you migrate users, we’ll only update them with the differences during your subsequent migrations instead of migrating your whole user base.

When your users get to cloud, they can also start working right away or learning the ropes as you continue to migrate projects and data.

Learn more about migrating Jira users in advance

To get started:

1. Update the Jira Cloud Migration Assistant to the latest version.
2. On the home screen, find the Migrate your users in advance card.

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.

Sorting pinned fields in an issue

If you've pinned multiple fields, you can now drag and drop your pinned fields to change the order and keep your favorite ones at the top.

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.

New 'Team' custom field in Jira

Admins can now enable a new ‘Team’ custom field from project settings. This allows project users to assign Jira issues and tasks to Atlassian teams.

Read more about Atlassian teams in Jira

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.

Removing the original theme across Jira Cloud products

We'll be removing the original theme and using light theme as the new default for Jira. You'll still be able to switch your theme between light and dark.

This change is happening across all Jira Cloud products and is an essential evolution of Jira’s original theme due to its improved color contrast for accessibility.

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.

M2 Manage all of your customer organizations in Jira Service Management

We're rolling out another improvement to the way organizations can be managed. Jira Service Management admins manage all of their organizations in Jira (regardless of which projects they're added to) from product settings.

This change makes it easier for admins find and manage organizations in Jira Service Management, regardless of which service project they're attached to.

Go to Settings > Products > Jira Service Management > Organizations. Here you’ll see a list of the existing organizations in Jira Service Management.

Organizations created from this page will begin without any projects associated with them. Find out more about how to manage organizations from Jira product settings.

Get better results by refining your search with more criteria

We’ve added support to fields like description, environment, epic name, Atlas goal, Atlas project, time in status CHART, and custom fields of the type paragraph, short text, and read-only. Additionally, we’ve added support to configure all fields as columns in the List view.

To get started with this change:

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

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.

Improving results carried over from "Quick search" to "Advanced issue search"

We're improving your search results when you go to Advanced issue search from a quick search. We're automatically adding a "wildcard search" to the advanced issue search query. That means, when you go to Advanced issue search, you'll get relevant results from your quick search, even if the word is incomplete.

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.

Introducing new ways to manage your notifications

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 6 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 icon (on the top right of your Jira project), then select Notifications

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.

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.

User access admin: Navigate to user management easily

With the Manage users permission or Site admin role, go to Settings (cog icon on top right) to access and manage users access to the product.

We’ve also reordered Settings to help you navigate to your preferences faster.

Request access to other products from Smart Links

We’re making it easier for you to use the same products as everyone else in your team through a Request access button straight from Smart Links.

The next time you select or hover over a Smart Link from Jira:

• If you have access to the product, you can immediately view the content.
• If you don’t have access to the product, select Request access.

Open Confluence embedded pages from the isssue view in Jira Service Management and Jira Work Management

While you're viewing a Jira issue, you will now be able to open Confluence pages in the same tab without navigating away from your issue. The page will open in a window on top of the issue.

Jira Product Discovery template recommendations in Jira Software

When you are on the Jira Software ‘Projects’ page you may now see recommendations for Jira Product Discovery templates.

Jira Product Discovery templates are all about helping teams prioritize ideas before they are scheduled for delivery, so the new template recommendations will only be shown to people who have jobs that involve prioritizing team workloads. For example, Product Managers or Project Managers.

Improved accessibility for the project settings details screen

Accessibility improvements have been made to the Details screen in Project settings for Jira Service Management, Jira Software, Jira Work Management, and Jira Product Discovery.

These changes will make it clear which fields are required, and will be visible in all project types for all products except for company-managed projects in Jira Software and Jira Work Management.

To view these changes, select Project settings, then Details. The changes include:

• inclusion of a statement at the top of the screen explaining that some fields are required and showing the legend for these required fields.
• each required field being marked with a red asterisk.

Company-managed projects: View more issues with full screen mode

Use full screen mode to see more issues and enter a more focused view of the board and backlog. With a single click, you can now hide the main navigation and project sidebar to reduce clutter and maximize the number of issues on your screen.

To enter full screen mode on the board or backlog, select the Enter full screen icon at the top right. To exit, select the Exit full screen icon.

New Summary page in your plan

One screen to rule them all! (or at least improve your visibility into plans)

The Summary page is a new feature that helps planners see the progress of their plans, track teams' work, and stay abreast on the health of your plan – all from one page!

The Summary page shows four widgets: Issue progress, Key dependencies, Team progress, and Team capacity. You're probably familiar with most of these concepts from other places in Jira Software, but on the Summary page they're scoped to the entirety of your plan. This lets you view the capacity and progress of all of the teams in your plan; see the largest blockers from every project; track how work at all hierarchy levels above Epic are progressing. The world is your oyster!

Read more about how these widgets work.

Select Summary from the left side navigation in your plan. The widgets should automatically pull information from your plan and display it in a colorful and welcoming manner.

Advanced Roadmaps - Update issue status directly from your plan

Move an issue from To do to In progress to Done without leaving your timeline view. That's right — Advanced Roadmaps now lets you update your issue's status directly from your timeline.

This change addresses a very popular feature request submitted by customers. Link to feature request ticket.

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.

Advanced Roadmaps - Create custom label from timeline

Imagine that you're in the midst of a planning bonanza, and you have a brainwave; "Eureka!" you exclaim. "I should create a new label for these issues!"

In the days of old, you had to go back to your issue view to create a label, but now you can do it without leaving Advanced Roadmaps.

But remember – labels can't contain spaces.

Changes to epic fields in company-managed projects

We've made changes to epics on your board and backlog to more closely align epics across company-managed and team-managed projects.

Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color.

These updates will also apply to the Epic link field in the issue view. Learn more about these changes

Connect your tools while creating a new project

We’ve updated the way you connect code and documentation tools when starting a new scrum or kanban project in Jira Software.

Depending on which tools are already connected to your site, you can quickly connect your team’s Bitbucket and GitHub repositories and their regular Confluence spaces.

And if you want to start fresh for this project, you can create new Bitbucket repositories and Confluence spaces while you’re creating your project.

To get started:

1. From the top menu, go to Projects, then Create project.
2. Go through the usual project creation process and enter details for your new project.
3. From the the Connect tools to power your project features screen, connect your Bitbucket repositories, GitHub repositories, and Confluence spaces (if one or more of those tools are already connected to your site).

Improved colors in epic and version panels

We’ve updated colors in the epic and version panels to better match Jira’s light and dark themes. You’ll notice a more accessible and visually appealing experience when hovering over and selecting cards.

Highlight your team’s software releases in your Jira Work Management calendar

Now you can keep your whole team up to date when you link your Jira Software project’s releases to a Jira Work Management calendar.

This is especially useful for communicating to a cross-functional team that includes both business teams and software teams.

Your teammates will be able to see release statuses, release dates and issue progress for all the releases in your Jira Software project.

And when you make changes to a release in Jira Software, the Jira Work Management calendar will be updated automatically.

To get started, add a Jira Work Management calendar to the related work section of your release. You must be an admin of the Jira Work Management project to link releases to the calendar.

1. From your project’s sidebar, select Releases.
2. Select a version from the list.
3. In the Related work section, select Add related work or Add links, release notes, and more…
4. Select Add Jira Work Management calendar.
5. Enter the name of the Jira Work Management project you want to link your releases to.
6. Check the Show all releases… checkbox, then select Add.

The Jira Work Management calendar you selected will now appear in the related work section of this release.

And all the releases from this Jira Software project will appear in the linked Jira Work Management calendar.

Add a section of rich text to your release

You can now add a section of rich text to your release. The new section can show text, lists, hyperlinks, dates, and emojis, and you can format the text with bold, italics, and colors.

To add rich text to your release:

1. From your project’s sidebar, go to Releases.
2. Select your release from the list.
3. Select Give this section a name" and enter a heading.
4. Select "Add your own text here..." and enter some body text.

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.

Company-managed projects: Improved accessibility for column and status settings

We're making improvements to the look and accessibility of board settings pages. When managing your board's columns and statuses, you'll notice a modernized interface and quicker access to support documentation without leaving the page. Importantly, we've made the page easier to navigate for keyboard-only and screen reader users.

To check out these improvements, go to your company-managed board, then select more actions (…) in the top right to open the board menu. Select Configure board, then Columns to view the Columns and statuses page.

From here, you'll be able to simplify your workflow, add or remove columns, add column constraints, and map statuses to columns. For Kanban boards, you can also enable the Kanban backlog and choose how epics are displayed.

Learn how to configure columns and statuses

Archive plans in Jira Premium

Archiving plans allows you to remove any plan you no longer need to view day-to-day, and restore it later if you need to.

To try out this change:

1. Navigate to the Plans view.
2. Select archive from the ••• menu.

Once they're archived, a plan can be restored through Advanced Roadmaps settings.

Control your view of the board and backlog

Find the View settings button in the top right of your board and backlog to switch on what you need, and switch off what you don’t.

On the backlog, you can open the epic and version panels, view quick filters as buttons, and view more issues by switching on Compact mode. On the board, you can open issues in the sidebar, and expand or collapse swimlanes. You can also choose to show or hide card details in both the board and backlog.

Create issues from the board in company-managed projects

You can create new issues directly from columns on your board. We've done this to more closely align issue creation across company-managed and team-managed projects.

Over the next few months, we'll bring this functionality to all company-managed projects, but for now, you can only create issues from the board if you're:

• in a kanban project
• using the default workflow
• using the default board filter.

To create an issue on the board, hover over the column and select Create issue.

The option to create an issue will appear in all swimlanes except Query and Projects.

If the Allow users to select a status for an issue they’re creating option has been disabled in System settings, this new functionality will not appear in your project.

View subtasks directly on the backlog

Previously, only company-managed kanban projects displayed subtasks directly on the backlog – all other project types required you to click into an issue’s details to see its subtasks.

You’ll now be able to view subtasks on the backlog of all your projects, improving visibility and allowing you to better plan and prioritize your work.

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

Connect an exisiting board to a project or user

A fix that allows you to assign a board to a new project or user, in case its previous home no longer exists.

Introducing Developer escalations for better collaboration with developers

Customer service agents can now easily create a developer escalation for a customer issue using the Developer escalations feature.

This feature enables you to streamline developer escalations for your project with a dedicated work category and view. Developers can view, comment, and collaborate on developer escalation issues raised by customer service agents.

To turn on this feature, from your service project, go to Project settings and select Features.

Read more about developer escalations.

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.

Simplified object schema configuration and streamlined importing

Configuring an object schema is now streamlined and simplified. When configuring an object schema, you can create new reference types and statuses by selecting Create a reference or Create a status.

We’ve also simplified how imports are created. To create a new import, select Create import, select your import type, and then select Create. Object types and attributes will be automatically created for you.

On the other hand, if you’d like to create object types and attributes manually, you can turn off Automatically create object types and attributes and map your object types and attributes yourself.

Finally, Process Results has been moved into the Imports tab, where you can see the history of your completed imports by selecting View history.

Learn more about importing objects into Jira Service Management.

Quickly create a new request type using request type templates

We’re introducing request type templates into company-managed projects to make adding a new request type to your service project a whole lot faster.

Instead of creating a new request type from scratch, you’ll have the option to browse a library of templates designed for a range of different teams and use cases, and select one to quickly create a new request type that you can edit later.

These request type templates act as a starting point for Jira admins who are new to Jira Service Management, as well as those Jira admins who are looking to create consistency across multiple projects, or further customize their project to meet changing needs.

To create a new request type using a template:

• From the navigation on the left, select Project settings, then Request types.
• Select Create request type, then select Create from template.
• Browse, search, and Preview the different templates.
• Select the template you want to use to create your new request type.
• Review and update the request type’s details including name, description, icon, portal group, and issue type and associated workflow, then select Save.

The request type object will be created and associated with the selected issue type and workflow. Consistent with how things work today, no new issue types or workflows will be created.

Get started easily with a Blank project and request type templates

We’re bringing the time-saving benefits of the new request type templates to the project creation experience.

When creating a new company-managed project using one of our Blank service management project templates, Jira admins will have the option to use request type templates to add request types to your project before it’s created.

Browse, preview, and select a template to create a new request type. You’ll land in your new project for the first time with your tailored selection of request types already added, and you can go on to customize them straight away.

To tailor your new Blank service project using request type templates:

• From the top menu bar select Projects, then Create project.
• From the Service management category, select a Blank project template.
• Review and complete your project’s details, then select Create project.
• On the welcome screen, select Let’s go and you’ll land in the request type template library.
• Browse, search, and Preview the different templates.
• Select the template you want to use to create your new request type.
• Review and update the request type’s details including name, description, icon, portal group, and issue type and associated workflow.
• To add more request types, select Save and create another to be taken back to the template library. Repeat this process as many times as you like until you’ve added all your request types.
• When you’re done (or If you’re only adding one request type), select Save and continue to project.

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

Add a custom domain for your help center

Use your own domain for the Jira Service Management help center. For example, your customers could use 'customer.support.acme.com/<path name>' (or optionally be redirected from 'support.acme.com') instead of 'acme.atlassian.net/<path name>' to access the help center.

Enjoy stronger brand recognition for your help center, boost credibility and search engine optimization, and offer a customized experience to your help seekers. This greater discoverability will help your customers get to the right place and get the assistance they need.

This feature is currently in beta, and is rolling out gradually to organizations. There are a few limitations to be aware of, and your fully qualified domain name will need to follow a specific pattern. Learn about custom domains

To add 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 the Custom Domains tab.

From here you can add a new custom domain and see all custom domains configured in your organization. Custom domains is available for Jira Service Management Standard, Premium, and Enterprise plans.

Get richer information about your incident on Microsoft Teams

The Atlassian ChatOps app for Microsoft Teams will now post richer information in your chats about activity on the ongoing incident.

You'll now get notified of updates to incident priority, assignee, responders, stakeholders, and affected services. Also, you can directly send stakeholder updates from your Microsoft Teams chat.

Learn more about connecting Microsoft Teams to your service project

Use workflow templates to easily replace your request type's workflow

Workflow templates have been added to company-managed projects to help save time and effort when setting up and customizing your team's service project.

Workflow templates can be used to easily replace a request type's workflow with a new one. Rather than creating the new workflow from scratch, Jira admins will have the option to browse a library of templates designed for a variety of teams and use cases, including some that come with preconfigured approvals steps.

Preview and select the one that best suits your needs, and use it to create a new pre-configured workflow that will be linked to your request type.

To change a request type's workflow using a template:

• From the navigation on the left, select Project settings, then Request types.
• Select the request type you want to update and within that request type's configuration screen, select Manage workflow, then select Replace using template.
• Preview a template to see its description, statuses, and transitions.
• Select the template you want to use, then review and make desired changes to the names of your new workflow and issue type.
• Select Continue and the new workflow and issue type will be added to your project and linked to the request type you chose to update.

You can also replace a workflow using a template from the Request types screen by selecting the More actions menu next to the request type you want to update. Then in the Workflow section, select Replace using template.

Automatically share invite to Zoom meetings on Slack

We've made it much easier to invite incident collaborators to your Zoom meetings.

When you start a Zoom meeting on an ongoing incident, Jira Service Management will send the meeting invite on your incident Slack channel, so you don't have to invite all responders manually.

To share Zoom meeting invites on Slack, you need to connect Slack to your service project.

Learn more about connecting Slack to your service project

Select or edit your team type in project settings

A new 'Team type' field has been added to the Details screen in Project settings for both company-managed and team-managed projects.

This field will enable admins to:

• view the team type that was selected on the Create project screen when the project was first created, and update it as needed.
• record the type of team that is using the project (if this wasn't selected during the project creation process) to help classify and keep track of multiple service projects within a site.
• benefit from pre-filtered views in project settings to help streamline the configuration process. For example, when creating a new request type using a template, the template library view will default to the category that most closely matches the project's team type.

To view, fill, or update the 'Team type' field:

• From the navigation on the left, select Project settings. The 'Team type' field is visible on the Details screen.
• Select your team type from the list.

Changes to epic fields in company-managed projects

We've made changes to epics on your board and backlog to more closely align epics across company-managed and team-managed projects.

Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color.

These updates will also apply to the Epic link field in the issue view. Learn more about these changes

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.

Import data using a comma-separated value file

Use a comma-separated value (CSV) file to import data into company-managed and team-managed projects in Jira Work Management.

Learn more about importing data into a business project using a CSV file

Get the information you need quicker and more easily

We're making some improvements to Jira Work Management. We want to make it easier for you and your teams to get to the most relevant information as seamlessly as possible. Any filters, grouping, sorting, and hidden items you’ve applied to your view will persist and remain as they were when you return to the tool. For example, if you apply a filter to the board view then navigate to a different project and come back, your filter will remain as it was before.

Effortlessly import data from Asana to Jira Work Management

Save time and effort by automatically mapping Asana project fields into a business project using the Asana importer. With a few clicks, admins can easily set up a business project and import project data from Asana. Read more about the Asana importer

Checkbox custom field is now available in the list view

You can now view and edit the checkbox custom field in your list view in Jira Work Management. This is available for both team-managed projects and company-managed projects.

You can also filter your project using the checkbox custom field in the list view.

[Learn more about custom fields in the list view|https://support.atlassian.com/jira-work-management/docs/customize-your-list-by-adding-or-removing-fields/#Add-custom-fields-to-your-list]

Deleting categories from an issue

Deleting a category will not automatically remove it from an issue. To remove it you'll either need to unassign it once you've deleted it or replace it with a new category field.

Colourful categories

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

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.

Improved accessibility for the project settings details screen

Accessibility improvements have been made to the Details screen in Project settings for Jira Service Management, Jira Software, Jira Work Management, and Jira Product Discovery.

These changes will make it clear which fields are required, and will be visible in all project types for all products except for company-managed projects in Jira Software and Jira Work Management.

To view these changes, select Project settings, then Details. The changes include:

• inclusion of a statement at the top of the screen explaining that some fields are required and showing the legend for these required fields.
• each required field being marked with a red asterisk.

Auto-convert editor option for eligible pages in a site

Site admins can now enable auto-conversion from legacy to the new editor for all pages containing eligible content within a site. This makes it easier than ever to upgrade to the new editor on eligible pages.

Space admins:

1. Navigate to Site Settings → Further Configuration → Convert pages automatically
2. Check Enable

Auto-convert editor option for space admins

Space admins can now choose to turn on automatic conversion from the legacy editor within a space. This new space setting makes it easier than ever to upgrade the editor on eligible pages.

Space admins:

1. Navigate to Space Settings → Manage Space → Convert Pages
2. Toggle on Convert pages automatically.

Enable notifications grouping

Notifications related to the same entity or object will be grouped together to help users manage their day-to-day actvities better.

To open grouped notifications:

1. Select the Notifications (bell) icon from the top-right menu.
2. Your notifications will appear grouped by entity or object.

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

Sort resolved comments by recency

You can now sort resolved inline comments by newest and oldest order. By default comments will be sorted newest first.

Copy content with ease via the floating toolbar

We’ve updated the floating toolbar experience within the editor. The floating toolbar now includes a copy button, which makes copying page elements easier than ever!

You can use the button to copy the following content:

• Tables
• Panels
• Expands
• Media (images & video)
• Links
• Layouts
• Code snippets
• Extensions and Macros (like the Table of Contents)

Move pages and blogs easily when editing

To make moving pages and blogs easier than ever, even while creating new content, we've:

• added a pencil icon to the editor breadcrumbs at the top of every page. When selected, it allows you to move your page or blog without interrupting your editing flow.
• enabled a Move option in the more actions (•••) menu within the editor for all pages or blogs that you have permission to move. (As always for page or blog moves, you must have permission to delete and create content in the new location.)
• upgraded the dialog for moving pages in the editor to show a preview of the page tree.
• upgraded the dialog for moving blogs to look more modern and visually appealing.

Learn more about moving pages and blogs from within the editor

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.

Confluence Premium: Delete a selection of pages at once

Space admins with Confluence Premium or Enterprise now have two options for quickly removing large numbers of pages from the content tree.

Formerly “Bulk Archive”, selecting pages in the content manager now prompts admins with the option to archive or delete them. Up to 500 pages can be archived at a time, storing them in the archive for future reference. Up to 100 pages can be deleted at a time, moving them to the trash.

Learn more about deleting pages

To delete a selection of pages at once

1. Go to Space settings in the sidebar.
2. Select Manage page tree from the Manage pages card.
3. Select the items you'd like to remove.
4. Select Delete.
   1. Follow the prompt to confirm your selection, cancel the action, or archive instead.

To restore or permanently purge deleted pages:

1. Go to Space settings in the sidebar.
2. Select Trash from the Manage pages card.
3. Select Restore for each page to be restored, or select Purge All to permanently delete all items from the trash can.

To view archived pages:

1. Go to Space settings in the sidebar.
2. Select Archived pages from the Manage pages card.

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.

Display Jira issues on a Confluence page with more options

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

To insert Jira issues:

1. Create a new Confluence page or edit an existing one.
2. Type /jira and select Jira issues.
3. Search for issues with either:
   • Basic - Type in keywords to search for issues
   • JQL - Use Jira Query Language (JQL)
4. 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 using Basic or JQL.
4. Select Insert issues.

Early Access Program - Display your Assets object data on a Confluence page

You have the ability to display your Assets data in Confluence using macros. This is an early access launch of a much-requested feature for Assets.

This native feature enables you to select an object schema, filter the objects stored within, and then surface those objects in a table within a Confluence page. This makes it easier than ever to track, manage, and analyze your assets wherever you need them.

Check out the Community post to join the early access program (EAP) for this feature.

To embed a table with Assets objects:

1. Navigate to a Confluence page you own.
2. Enter / on your keyboard.
3. Search for Assets in the dropdown menu search bar, then select Assets.
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: Announcement banner improvements

Product administrators with Confluence Premium or Enterprise can make widespread announcements in a configurable banner that appears at the top of Confluence.

And now multiple banners can be scheduled, archived, and copied from an announcements table. This allows product admins to manage more than one banner at a time, preserving the publication history and providing the ability to easily re-publish them in the future.

Learn more about configuring an admin announcement banner

You can find "Announcement banner" under Configuration in Confluence Settings.

Email notifications for mentions and tasks have been redesigned

Email notifications for mentions and tasks were improved to include more context and content so that you understand what happened without having to go to Confluence.

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

View your table of contents instantly while editing a page

Upon adding a table of contents to a page, you can now see it instantly, and in its entirety, while editing. There's no need to publish the page first in order to view it.

Header links within the table of contents are not currently selectable but will be soon.

While editing a page, type / or select the + menu from the toolbar. Find and select Table of Contents. As headings are added to the page, they'll be reflected in the table of contents in real time.

Keep track of activities for team calendars in the audit log

View the history of when a calendar or custom event was added or deleted in your team calendar audit log. You’ll also be able to see who completed these actions.

To see audit log activities for a team calendar:

1. Go to admin.atlassian.com.
2. Choose your organization if you have more than one.
3. Select View audit log.

Create new pages or Jira issues using /create

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

To create a new Jira issue using /create:

1. From Confluence pages 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 Confluence pages or comments, type /create confluence.
2. Select Create Confluence page.
3. Enter page details then select Create.

Follow Atlas projects from Smart Links

You can now follow Atlas projects straight from Smart Links.

Atlas allows you to connect teams and work across products with customizable projects, goals, and objectives.

To follow Atlas projects from Smart Links:

1. Hover or select a Smart Link from a Confluence page or comment.
2. Select Follow.

You may also select Unfollow to stop getting updates from Atlas projects.

Confluence Premium: Automation in sidebar navigation

Space administrators with Confluence Premium or Enterprise will now find it a little easier to get to Space automation.

Automation is now available as a link at the top of the sidebar, alongside other key features like Analytics and Calendars.

Learn more about Confluence automation

Sidebar links can be turned on or off by visiting Space Settings > Manage space > Edit sidebar.

Request access to other products from Smart Links

We’re making it easier for you to use the same products as everyone else in your team through a Request access button straight from Smart Links.

The next time you select or hover over a Smart Link from a Confluence page:

• If you have access to the product, you can immediately view the content.
• If you don’t have access to the product, select Request access.

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.

Assess and prepare users in the Confluence Cloud Migration Assistant

In Server and Data Center, username is the primary identifier, that’s why many users don’t provide valid emails when creating their accounts. That’s an issue when you decide to migrate, because in cloud every user must have a valid and unique email address. Otherwise, they’ll block your migration.

To give you a hand with updating all these old and testing accounts, we’ve added a new card to the Confluence Cloud Migration Assistant that lets you:

• Assess your users to find invalid and duplicated email addresses
• View their details to identify important accounts that should be updated in your user directory
• Automatically fix all remaining accounts, for example by merging duplicates or deactivating them

A similar functionality was already available for Jira, now we're bringing it to Confluence!

Learn more about assessing and preparing users

To get started:

1. Update the Confluence Cloud Migration Assistant to the latest version.
2. Open the migration assistant. You'll see the Assess and prepare users card on the home screen.
3. Select Begin assessing to identify users with invalid and duplicated emails.

Improvements to trusted domains in Confluence Cloud Migration Assistant

We’ve added improvements to trusted domains in Confluence Cloud Migration Assistant so you can review and trust them in bulk. These changes were already available for Jira, now we’re bringing them to Confluence!

Trusting the domains via the CSV file

The biggest improvement, especially for bigger instances, comes with the CSV file. You can download a  CSV file with all the domains from your user directory, modify them, and upload the file back. This should make it easier to handle a high number of domains.

More improvements

Other improvements include:

• • User details:* View the inactive/active user count for each domain, with details on specific users.

• • Sorting:* Sort the list by columns to find the most common and important domains.

• • Filtering:* Filter by Decision status (Trusted, Not trusted, etc.) to quickly see what’s left to do.

Learn more about reviewing email domains

To get started with this change:

1. Update Confluence Cloud Migration Assistant to the latest version.
2. On the home screen, access the Review all domains screen.

Potential change to your Bitbucket Cloud bill

From October 31st, 2023, Bitbucket Cloud will begin counting all workspace members as a billable user. This is a change from our current model of only billing for users who have access to a private repository. Due to this change, customers with users who only have access to public repos or users with no access to any repos will see an increase in their bill due to a higher billable user count.

This change is a part of our efforts to align the definition of a user in Bitbucket Cloud with the rest of Atlassian's products, providing administrators consistency when managing users and budgets. One of the key projects that this change will enable is the integration of Bitbucket users into Atlassian Administration and Access, as described in https://bitbucket.org/blog/unified-user-management. Note: We have reached out to the customers who are directly affected by this change to our billing model. For more information, check out our blog post.

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