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

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

Test external user security before you roll it out

You can now test your external user security settings before you roll them out to your whole company. You're able to add a test policy and select up to 5 users for the test policy.

When you’re done testing the settings, you can turn the settings on in your external user policy. When you do this, the settings roll out to all your external users.

You will see these user interface changes to external user security:

External user policy- includes security settings and external users in your organization
Test policy

To test external user security, you can create a test policy and then add up to 5 users to the policy.

To create a test policy:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > External users.
3. Select Add test policy.
4. Add external users (up to 5) to the test policy.

You can add or remove external users to your test policy at any time. When you’re done testing the settings, you can turn settings on in the external user policy.

Learn more about external user security

Prevent your users from signing up for products

With an Enterprise plan, you can now prevent your managed accounts from signing up for products on their own. When they try to sign up for a product, we send them to a page where they enter details about how they plan to use the product. You can review all your users' requests, from the Product requests page. Learn more about product requests

To prevent users from signing up for products:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Product requests.
3. Select Update request settings.
4. Find the products that you want to prevent users from signing up for. For each product, select the dropdown under Request setting and select Require admin review.

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

Add users from Google and Microsoft in Atlassian Administration

Now you can add anyone to your Atlassian products by connecting your Google and Microsoft accounts in Atlassian Administration. Connecting Google and Microsoft lets you easily search for and invite people by name instead of entering full email addresses.

To connect your Google or Microsoft account and add users to your products via Atlassian Administration:

1. Go to admin.atlassian.com
2. Select the Directory tab, and then select Invite users.
3. Place your cursor in the Find users to invite input field. Then, select Google or Microsoft to proceed with authenticating your Google or Microsoft account.
4. After authenticating and granting access to Atlassian Cloud, place your cursor in the Find users to invite input field again.
5. Now you can search for and invite people by name with a connected Google or Microsoft account. You can manage your connections anytime by selecting the cog icon.

We’re making it faster to get your team using the tools they need

People who use Atlassian products but aren’t admins have to request to try a new product. When an admin approves the request the requestor isn’t automatically added to the approved, new product.

Now, when an admin approves the request to try a new product, the requestor is automatically added to the approved, new product. Admins don’t need to go out of their way to add the requestor to the product after they’ve approved the new product, it will all happen at once.

That means it’s easier than ever to help your team and give them the tools they need to get their work done.

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

Track your billable managed accounts for Atlassian Access

You now can now see a more precise description in your managed account CSV file for the term Billable. Billable means a managed account is billable for an Atlassian Access subscription.

You will see this change to your managed accounts CSV file:

-The column name Billable will change to Billable for Atlassian Access

To see the managed accounts that count towards your Atlassian Access subscription, you can export the CSV file for managed accounts.
To export managed accounts

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Directory > Managed accounts.
3. Select Export members.
4. You'll get a dialog that confirms we'll email you a CSV file once the file is ready to download. Select Export to continue.

It may take a few minutes if you have a large number of accounts. The unique download link in the email expires in 24 hours. Anybody else with the link can download the file.

1. When you receive the link you can download and open the CSV file

Billable for Atlassian Access appears as a column name in your managed accounts CSV file

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.

Issue View: Issue strikethrough now based on resolution

On the issue view, linked and child issues will sometimes have a strikethrough, indicating that they have been completed. Previously, however, this strikethrough was appearing if issues had a status category of Done, regardless of whether or not they had been set as resolved.

We’ve updated the behaviour on the issue view, so that linked and child issues will now only have a strikethrough if a Resolution has been set.

Learn more about issue strikethroughs on the issue view

Copy the value of one field to another in workflow rules

In team-managed projects, you can automatically copy the value of one field to another after moving an issue. To try it out, go to your project and select Project settings > Issue types > Edit workflow.

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.

Access more fields in team-managed service projects

While configuring request types in team-managed service projects, you can now add and reuse fields from your company-managed service projects.

On the Request types page in your Project settings, use search to find fields from your current project or any of your company-managed service projects. You can also use the Suggested fields section to browse recently created and recently used fields.

Wallboards: Added support for themes and Forge gadgets, but removed custom transition effects

Previously, wallboards would only display in dark mode and couldn't display Forge gadgets. Now, your wallboards will match the theme you've set in your personal Jira settings and will also display Forge gadgets. To add support for these features, we had to remove the option to apply custom transition effects to wallboard slideshows. Fade-in/out will be the only available transition effect. Check out any of your wallboards or wallboard slideshows to see these changes.

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.

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.

"Create dashboard gadget" pop-up now supports dark theme

When you create a dashboard gadget from the issue navigator, you'll see that the "Create dashboard gadget" pop-up now fully supports dark theme. To check it out, select Export issues > Create dashboard gadget from the issue navigator.

Discover the new form template library

We’ve made it easier to browse, search, and preview all form templates.

Find a variety of templates suited to all team types from IT to HR, plus leverage pre-built conditional sections and rich formatting to help get you started sooner.

See each team’s most popular templates, or select Show all to see what else is available. From employee checklists to budget approvals, you’ll be sure to find a template that helps you better assist your customers.

Select Project settings > Forms and select Create form to either select a form template to customize, or Blank to create your own.

Learn more about creating a form using a template

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.

View all of your organizations in Jira Service Management

Jira Service Management admins can now view all of the organizations in Jira (regardless of which projects they're added to) from product settings.

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. If you'd like to add a new organization:

1. Select Create organization to create a new organization.
2. Type your new organization's name and select Create.

Control which customers can send requests to your project

While creating a new service project, use the Channel access setting to decide who can send requests to your team by email, widget, and the portal.

Restricting channel access ensures that only people who've been invited to your service project can send requests, while setting channel access to 'Open' allows anyone to send requests to your team, as allowed by the site's customer access settings.

After creating your project, you can update your Channel access settings at any time from the Customer permissions page in your Project settings. Learn more about customer permissions and channel access.

Automation moving out of the issue view

Recent rule executions for each Jira issue are moving to a new Automation panel (similar to the Details and More fields panels).

Previously, this information was found by clicking on an option called "Automation" on the Jira issue view.

Removal of "Automation" issue glance

The "Automation" issue glance is being removed from all issues. You'll find recent rule executions for each Jira issue in a new "Automation" panel (similar to the Details and More fields panels).

View key information when you hover over links

You can now view the summary, description, and other key information when you hover over links in Jira issues and search results.

This reduces the need to open links in a new tab or window and switch contexts while you work.

1. Open a Jira issue or do a quick search.
2. Hover any link to view key information.

Stay up to date with progress bars for releases

We’ve added a progress bar for related work so you can quickly determine the readiness of your release. You can see how many related work items have been added and their status.

Learn more about progress bars in releases

To get started with release progress bars:

1. From your project’s sidebar, go to Releases.
2. Select your release from the list.
3. Go to the Progress section to see up-to-date details.

No more limits on number of security containers

We’ve removed the 100 security container limit, and now you can connect and view as many security containers as you want to a project.

Learn more about security containers in Jira

To use with pagination for security containers:

1. From your project's sidebar, select Security.
2. Find the Security containers section, then select Load more to see additional containers that have been connected to your project.

Unlink an issue from a vulnerability

We’ve added the ability for you to unlink issues from security vulnerabilities in Jira.

Now, if the wrong issue is accidentally linked to a vulnerability, or the issue was created by mistake, you can quickly and easily remove the linked issue to ensure all the information in the Vulnerabilities section is accurate.

Learn how to manage security vulnerabilities in Jira

To get started unlinking Jira issues from a vulnerability:

1. From your project's sidebar, select Security.
2. Find the vulnerability, and select the unlink issue icon in the Issues column, then select Unlink, or
3. Select more actions (•••), then Edit linked issue.
   1. From Edit linked issues, you can confirm which issues are currently linked to the vulnerability.
   2. To unlink an issue, select ( x ) next to the issue, then Save.
   3. Unlinking an issue simultaneously removes it from the Issues column in the vulnerabilities table.

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.

Removing single email address notifications

We identified a security concern with Jira notifications Single email address field where it could be used maliciously to send spam to any email address. So we're removing this functionality completely from Jira Cloud.

Any existing single email address recipients will stop receiving these notifications after the change is rolled out. There are still alternative options for notifying external emails which you can read about in the community article about this change

Advanced Roadmaps - Share your dependency report through the Confluence macro

Share your Advanced Roadmaps dependency report in a Confluence page in the same way you would your timeline.

Learn how to share your dependency report.

Advanced Roadmaps - New quick select options in the Review changes modal

In the Review changes modal, you can now select changes based on the following:

• changes made by you
• changes made today and
• changes that apply only to issues you've selected on your timeline

Learn more about filtering changes in the Review changes modal.

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.

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.

Make simple bulk edits to issues in the backlog

You can now make bulk edits to priority, assignee, labels, and estimate all from the backlog.

To select a group of issues, hold "shift" while you select the issues. To select multiple issues, one at a time, hold "command" (for Apple devices) or "control" (for Windows devices) while you select each issue.

Right-click on any of the selected issues and choose the bulk action you'd like to perform. You can perform these actions on up to 50 issues at a time.

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.

Exciting updates to the sprint commitment insight

We've extended the sprint commitment insight to share more valuable information with you. Look out for an added info panel with sprint metrics like work committed.

The chart also had a new update and will be interactive. You can access the metrics from your previous or current sprints by selecting the bars on the chart.

To try this out:

1. Select Insights.
2. Scroll to the Sprint commitment chart.
3. Select any bar on the chart to view the metrics for that sprint.
4. Notice the blue panel with additional information and metrics.

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.

Advanced Roadmaps - Create and remove dependencies on the dependencies report

Create new dependencies and remove existing ones without leaving the Dependencies report in Advanced Roadmaps.

Learn how to create a dependency between two issues from your Dependencies report.

Team-managed projects: Optimized and responsive layout for issues in the backlog

Issues in the backlog now have an optimized and responsive layout that makes it easier to parse the different types of information on each card. We’ve reorganized icons and fine-tuned their alignment for improved legibility. You’ll notice this on the priority, estimate (if using a Scrum board), flag, status, and epic fields. When resizing the backlog to accommodate smaller screen sizes, epics will be indicated by the epic’s color.

To see the enhanced layout, go to your team-managed project, then select the Backlog view in the project navigation.

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.

Updated project creation experience

We've simplified the process of creating new projects to make it easier to get started. When you select a project template, you will now go straight to the screen where you can add your project's details instead of viewing the details for the template. You can still view the details of the template by selecting See details.

We've also redesigned the form and put some of the more advanced settings in an accordion.

For company-managed projects, these settings include:

• Project key (auto-generated using your project name)
• "Use settings from an existing project"

For team-managed projects, these settings include:

• Access settings (set to private by default)
• Default language (set to the site language by default)
• Project key (auto-generated using your project name)

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.

Introducing a smart way to find similar incidents

On an incident, we’ll now show some incidents from the past that are similar to the one you’re viewing, so you can use past information to investigate and resolve the incident faster.

These results are AI-powered, so some results may not be relevant or helpful to you. To help improve results, you can give feedback by reacting 👍 or 👎 to a result.

Enable notifications for Jira Service Management customers only

You can now enable notifications for Jira Service Management customers while notifications are disabled for other Jira products.

Go to the cog icon on the top right of your screen, then select System > Outgoing mail.

When outgoing mail is disabled, you'll be able to see the option to turn on mail for Jira Service Management only.

If you have compliance and privacy needs, we recommend also turning on safe notifications for Jira Service Management.

Use templates to create virtual agent intents in Jira Service Management

When creating a new intent, instead of entering your intent settings and training phrases from scratch, you can now use templates!

We created some templates based on common use cases, while other templates are automatically generated using data from your recent Jira Service Management issues. All templates are editable, so you can tweak them to suit your needs.

To use intent templates, just create a new intent.

Fix incompatible request types from the issue view

We've made it easier to see and fix any request types that are incompatible with an issue.

Request types can become incompatible with an issue if you make certain configuration changes to that issue. For example, if you change the issue type of an issue, that issue's current request type will become incompatible, as the issue type of the request type and the issue no longer match. Learn more about how issue types and request types connect.

Now, you can use the details panel of your issue view to check if your request type needs updating. If a warning appears, select the request type, then choose a new request type from the menu. Only compatible request types will appear in the menu. If there are no compatible request types, an admin will need to create a new one.

Your Coach is now simpler and even more helpful

We're thrilled to announce some exciting updates that are designed to make your journey with Your Coach even smoother and more productive. Here's a rundown of the enhancements:

• We've brought the Quick setup key actions right to the forefront. This will allow you to access important features faster.

• Bid farewell to tab-switching. You can now access Walkthroughs and Documentation from their corresponding sections and key actions.

• We've reimagined the layout for better usability. The Sample space has found a new home at the bottom of the pane, and the Exit option has been relocated to the top right corner, making it ultra-convenient.

• Clarity is key. We've fine-tuned the titles and descriptions of key actions, ensuring that you have a crystal-clear understanding of each step.

We're excited to bring these improvements to you and believe that they will elevate your overall experience with Your Coach.

Easily resolve failed customer invites due to email suppression list

We've made it simpler for project admins to resolve failed customer invites caused by email addresses being added to a suppression list.

In the current Jira Service Management experience, when customers are invited to join a service project, some invite notifications fail as the email addresses are on a suppression list. There was no option for admins to resolve such errors and they would need assistance from Atlassian support to remove affected customer emails from the suppression list.

With this new improvement, admins can now resend invites that failed due to email suppression easily without reaching out to Atlassian support. When you see that a customer invite failed because the email address is on a suppression list on the Customer notification logs page, you can resolve the error by simply resending the invite.

From your service project, go to the Customers page, and select Resend invite next to the customer’s email address. This removes their email from the suppression list and resends the invite.

We recommend keeping an eye on the Customer notification logs page to spot any failed invite notifications and address them as soon as possible.

Learn more about customer notification logs

Chat for Microsoft Teams: User avatars are now displayed as initials

To enhance our security posture, we’re updating the request and issue card display in Microsoft Teams for chat customers.

These cards will now display user initials for agents and help seekers instead of Teams profile pictures. This only impacts the visual experience — no functionality is changing with this release.

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.

Jira Work Management Premium is here!

When it's time for your teams to scale, get access to advanced features that support cross-functional work with a Jira Work Management Premium license.

Visualize and track work across multiple projects with overviews, get unlimited storage, 24/7 Premium support, and so much more.

Learn more about Premium plans

Export of a list view into a CSV file

We’re introducing a new way to export Jira Product Discovery list views into CSV files. Now, you can download a list view data with just a few clicks directly from a list view.

To export a list view into CSV:

1. Open any list view in your Jira Product Discovery project.
2. On the upper right corner of the list view, select Share > Export > Download CSV.

Currently, reactions and Atlas fields aren’t supported during the export.

Learn more about exporting in Jira Product Discovery.

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.

Switch themes while using Presenter mode

You can now switch between dark and light themes while using Presenter mode.

Try this out:

1. View a page.
2. Select More actions (•••).
3. Select Presenter mode.
4. Select the Presenter settings (⚙️) cog.
5. Use the theme selector to switch on or off dark mode.

Easier to request the access you need

When using a page link that takes you into edit mode, you have new options when you don't have permission to edit. You can request edit access as well as view the page.

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.

Add a note to archived pages

Let others know why pages were archived.

When teammates archive a page (or a group of nested pages) from the content tree, they’ll be prompted with the option to add a note. This attaches a written record explaining why the pages were moved.

Confluence Premium space admins can add the same note to a selection of pages in Bulk Archive.

Notes can also be added or edited from the more actions menu in the archive (but only by the person who archived the page).

Learn more about archiving pages

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.

Indent and outdent content easier from the toolbar

The editing toolbar now includes indentation buttons, making indenting and outdenting content easier for those unfamiliar with the existing tab and shift + tab keyboard shortcuts.

You can use the buttons to indent the following content:

• Top-level paragraphs and headings
• Bullet lists
• Numbered lists
• Task lists

Learn more about indenting content in Confluence Cloud

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)

Control how people are added to Teams

Teams can choose if they want to require an invite or request approval from an existing member for new people to join.

For all new teams, membership controls are enabled by default. Existing teams will remain open for anyone to join.

To change membership controls for an existing team:

1. From the team profile page, select the menu icon next to Add people.
2. Select Team settings.
3. Select or clear the checkbox under Membership controls.
   1. Selecting the box will enable anyone to join the team without needing an invite or approval.
   2. Clearing the box means people will need to request approval or get an invite from an existing member.

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.

Pick the product theme that works best for you

You can personalize the way Confluence looks to best suit your needs. The options include Light, Dark, System, or Original (the current default Confluence theme).

To check if you have access to themes:

1. Select your avatar at the top right of the global navigation bar.
2. Select Theme.
3. Choose your preferred theme.

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.

Dark Mode Onboarding

We're adding a spotlight to show users the new theme switcher.

Bitbucket Premium: Share Pipelines configurations

Pipelines configuration sharing is a Premium feature, meaning you or your organization must have a Premium plan in Bitbucket Cloud to use it. Learn more about Bitbucket Premium

Being able to share your YAML configuration in Bitbucket Pipelines allows you to define and share pipeline definitions within the same workspace, which enables you to streamline your pipeline definitions by not having to repeatedly create each pipeline configuration. Learn more

Bitbucket Pipelines variable description

Now you can add a variable description for your Bitbucket Pipeline by configuring the 'description' field for the variable in the bitbucket-pipelines.yml file. The variable description you have provided is displayed under the variable in the Run Pipeline dialog. Now your teammates don't need to go back and forth to the Readme in order to get this information.