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

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 > Security > Authentication policies > Settings > User API tokens

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

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.

Enable HIPAA for eligible products in Standard, Premium, and Enterprise plans

Sign a Business Associate Agreement (BAA) and enable HIPAA for your eligible Atlassian products on Standard and Premium plans through our new self-serve experience. For Enterprise customers, contact an Atlassian representative to sign the business agreement.

To enable HIPAA for your Atlassian products:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Compliance. Then select Health Insurance Portability and Accountability Act (HIPAA).
3. Select Sign a BAA. If you already have a signed BAA, select Tag products.

Learn more about HIPAA compliance for Atlassian products

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

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

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

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

Learn more about tracking activities from the audit log

To see audit log activities for all data security policies:

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

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

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

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

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

Find Atlassian Administration settings faster

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

To use the Administration search field:

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

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

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

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

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

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.

We’re making it easier for your team to access Confluence

Before, people who weren’t admins had to request to access Confluence. This request was sent as an email to their admin who could then approve or deny the request.

Now, people who aren’t admins can try Confluence 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 Confluence. 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.

Add borders to images in Jira

This new and improved feature is now available in Jira Software, Jira Work Management, and Jira Service Management. Image borders allow a cleaner way to separate content and images with additional customization options. You can adjust the border size and select the right color to give it the emphasis you're looking for.

To add a border:

1. Select an image to make the toolbar appear.
2. Select the leftmost button with the square icon to apply the border.
3. Customize the border by selecting the arrow next to the icon.

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

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

Teams can now be created from the team field

With the new team custom field available in Jira Software, Jira Work Management, and Jira Service Management, you can now create a team from the field menu.

To get started:

1. Select the team field on any issue.
2. At the bottom of the suggestions list, select the "Create a team" option.
3. Create your new team through the dialog.

New ways to navigate Jira with your keyboard

We’re introducing the only shortcut you’ll ever need.

The command palette lets you use your keyboard to find and update issues, navigate around Jira, switch themes, and more.

Open the command palette from anywhere in Jira by using:

• command(⌘) + K for Apple devices
• ctrl + K for Windows devices.

There’s no requirement to getting started. Just try command(⌘) + K or ctrl + K and start exploring. You might find it makes working in Jira faster and easier than ever.

Expand and collapse forms in portal view

Improvements have been made to the portal view in Jira Service Management to make it easier for customers to review their forms. Customers can now choose to expand forms to review and edit, then collapse them when they wish to review another form on a request.

Learn more about how forms can be used in the portal

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.

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.

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.

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 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.

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.

Add Zoom meeting recordings as internal note to the incident

Now, when you create a Zoom meeting to collaborate on an incident, you can customize the meeting topic and choose to add the meeting recording as an internal note to keep the incident's activity section up-to-date.

The meeting's recording will be added to the incident once it's processed by Zoom, which can take a while.

You'll need to give Jira Service Management permission to access your meeting recordings, so it can add your recordings. Select Give permission when you're prompted while creating a Zoom meeting.

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.

More detail in Smart Links with better features

We've upgraded Smart Links to show the information you need with improved features to increase your productivity.

The changes include modernised Inline, Card, Embed, and Hover display views with new layouts, shapes, colors, and fonts.

To view these changes:

1. Copy or type in a URL in a Jira comment or description.
2. Select the link.
3. Change how the link is displayed from the Smart Link toolbar.
4. Select Save.
5. Hover over the display and interact with link elements.

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.

Automation: Audit log date filters

When viewing the audit log in Automation, you can now filter entries by date and time. This is handy if you want to find all rule executions that happened between certain times, or if you want to troubleshoot an error that occurred before a certain date.

1. Navigate to Automation
2. Select Audit log.

Track all release contributors in one place

You can now have more visibility into everyone who’s contributing to a release. People assigned to issues linked to a release show up as contributors.

To get started with release contributors:

1. From your project’s sidebar, go to Releases.
2. Select your release from the list.
3. Check the release’s contributors for up-to-date details.

We’re making it easier for your team to access Confluence

Before, people who weren’t admins had to request to access Confluence. This request was sent as an email to their admin who could then approve or deny the request.

Now, people who aren’t admins can try Confluence 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 Confluence. 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.

GitHub now supported in Jira’s security feature

You can now track security vulnerabilities scanned from GitHub and access important security work in one place. Your wider team can plan and organize, gain visibility into status, and fix vulnerabilities faster.

Vulnerabilities from GitHub’s dependabot and secret scanning alerts will appear in the security feature.

Learn how to connect GitHub for Security

Join the discussion on Community

To get started:

Once your GitHub admin enables GitHub for Jira, and it’s already set up on a project:

1. From your project’s sidebar, go to Security.
2. Check the vulnerabilities table for the most up-to-date details.

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.

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.

Advanced Roadmaps - Your plan as a list

Have you ever wished that you could have a version of your plan that's just heaps of columns (we know you have; it's one of our most requested features)?

Well, dream no more! You can now make a version of your plan that doesn’t focus on the timeline structure using the Timeline | List toggle on your plan (next to the View settings button). When you do, you'll be greeted with a ‘second page’ of your plan where you’re free to add more columns to show more detail, or tell a completely different story with your data.

To learn more about this, either:

• head over to our post on Atlassian community or
• take a look at our documentation

New failed build tasks available in your work suggestions panel

If you have any failed builds related to issues currently assigned to you they will now be added to your list of suggestions so you can easily take action.

1. Go to your Jira board.

2. Select your avatar.

3. Your work suggestion will open. Look for a failed build suggestion and select the card to view more information about the build.

View, edit, and manage forms better in issue view

Improvements have been made to the issue view in Jira Service Management to make it easier for agents to review forms.

You can now expand forms to review and edit, then collapse them when you wish to focus on another area of an issue.

You’ll also find the ability to Make form internal now in the (...) menu on each form for easier access. Plus, we’ve made it more obvious which forms are internal only. All internal forms will display yellow to follow the same pattern used for internal comments. This makes it clear to your team what only they can see, and what the customer can.

Learn more about how to view, add, or edit a form on an issue

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.

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.

Introducing customer notification logs

Using customer notification logs in Jira Service Management, project admins can easily find out which notifications weren’t received by their customers and take necessary actions to ensure that their customers get notifications on time.

To access customer notification logs, go to your service project, and select Customer notification logs. Here you’ll find details like the name of the notification, when it was sent, and why it wasn’t delivered.

Currently, we’re introducing logs for customer invite notifications only. For more details, see this community post.

Learn more about customer notification logs

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.

Get additional customer context in issues

In projects with customer service management turned on, you can now view details about your customers and any organizations associated with an issue while viewing that issue, giving your agents extra context about your customers while working on support requests.

These details will appear on issues along with the other details relating to the issue. The details shown will be based on the customer detail fields you've created and the details of your customers that you've added. The customer shown is based on the Reporter field input and the organizations shown are based on the Organizations field input.

There will initially be a limit of five fields shown each for customers and organizations.

To take advantage of additional customer context in issues, you'll need to have the customer service management feature turned on. To do this:

1. Select Project settings from the navigation on the left.
2. Select Features.
3. Turn on Customer service management.

Improved delete controls for Assets in Jira Service Management

Deleting items in Assets in Jira Service Management is now safer and easier. Want to delete object schemas or object types? You'll need to explicitly type their name first. For attributes and bulk objects, you need to check a box to confirm.

We've also moved the delete buttons for better access. The “Delete” buttons for object schemas and object types are now in their respective configuration pages.

These changes make it harder to delete items by mistake, so you can manage your data with more confidence. Let's enjoy a smoother, more user-friendly experience with less worry about losing important info.

Learn more about deleting schemas in Assets in Jira Service Management

Resolve and close your issues in chat

Agents can now resolve issues in Slack for projects connected with chat. This fixes an experience where agents could close an issue without adding a resolution, which caused these “closed” issues to appear in incorrect queues and prevented CSAT surveys from sending.

Now, if an agent changes an issue status to closed in Slack, they also must choose a resolution. We expect to fix this experience for Microsoft Teams customers soon.

Learn more about resolving issues in Slack

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]

View, edit, and manage forms better in issue view

Improvements have been made to the issue view in Jira Service Management to make it easier for agents to review forms.

You can now expand forms to review and edit, then collapse them when you wish to focus on another area of an issue.

You’ll also find the ability to Make form internal now in the (...) menu on each form for easier access. Plus, we’ve made it more obvious which forms are internal only. All internal forms will display yellow to follow the same pattern used for internal comments. This makes it clear to your team what only they can see, and what the customer can.

Learn more about how to view, add, or edit a form on an issue

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.

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.

More detail in Smart Links with better features

We've upgraded Smart Links to show the information you need with improved features to increase your productivity.

The changes include modernised Inline, Card, Embed, and Hover display views with new layouts, shapes, colors, and fonts.

To view these changes:

1. Create a new Confluence page.
2. Copy or type in a URL.
3. Select the link.
4. Change how the link is displayed from the Smart Link toolbar.
5. Select Publish.
6. Hover over the display and interact with link elements.

Redesigned Confluence email settings

Confluence email settings have been redesigned to be more customizable. The Daily Summary email was removed.

Android app update v2.13 - Dec 1st, 2021

Say goodbye to all the scrolling and searching—now you can jump straight to comments by tapping the comments icon at the bottom of 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.

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.

Publish and update your content with more precision than ever

We’re improving the experience of publishing and updating pages and blog posts.

The improved experience aims to remove the anxiety that can emerge around content creation and distribution. It does so by providing users with more transparency and control over where a page will be located and who will be able to see it when it's published.

When you first go to publish a page or blog post by selecting Publish…, you’ll encounter a new modal that consolidates several publishing options and settings into one place. There, you’ll be able to:

• Choose where the page or blog post will go.
• Choose who will be able to view or edit the page or blog post once it is published.
• Add version comments to describe the page you are publishing. These comments can be helpful later when reviewing a page’s history.
• Schedule a publish for a future date and time.
• Convert a page into a blog post.

Other than location and access, all fields in the publish dialog are optional. Spending the time to set your preferred settings up front can save time on future updates.

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)

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.

Control public links on a space-by-space basis

We've added a second level of control for admins managing public links on their site. Previously, there was only one control — in global permissions — that dictated whether public links should be allowed at all on a site. This was limiting because it was an all-or-nothing switch. If there was even one space that shouldn't allow public links, it wasn't safe to allow any public links.

With this release, we're introducing a space-level control to give admins greater flexibility into which spaces on the site should allow the use of public links and which should not.
Simply go to the “Public links” tab in Space Permissions to find the space-level control.

(Note: Public links are only available to a small percentage of customers currently but we hope to roll this out to all of our paid customers later this year!)

–

In addition to the space-level control, we're also introducing the following changes:

Public links override page restrictions
View restrictions on a page or any of its parent pages won’t block people from accessing the public link anymore. Public links will just simply work!

ACTION REQUIRED We recommend checking for any pages that have the public link toggle switched on that are relying on the page’s view restrictions (including any restrictions inherited from a parent page) to prevent that public link from being accessed. Once the change hits your experience, people will be able to access those public links again. To prevent this, you’ll need to manually turn off the page's public link toggle.

Helpful confirmation messages
Sharing content publicly shouldn’t be done lightly. Confluence will help make sure you understand what you’re doing with public links at important points in your experience with them. You can be sure that when a change is made, it was made intentionally.

Clear visual cues and messaging for when content is public
With a feature like public links, information security is our #1 goal. So we’ve added indicators throughout the editing, sharing, restricting, and viewing experiences to clearly signal when content is public so you and your team are fully aware when you’re working on something public.

Control whether any new spaces created should allow public links
Admins can choose what the default public link setting should be for all new spaces created in the future and whether or not those spaces should be pre-set to allow people to use public links.

Learn more about public links

Resize tables to custom widths

Now you can resize tables to any width, whether you're editing a fixed-width or full-width page. Use the resize handle to proportionally grow or shrink your columns, and guides to align your tables with other content on the page.

What's new?

• You can now resize tables to any width, not just the three predefined sizes (centered, wide, and full-width).
• The resize handle will replace the width selector.
• Table widths will now be preserved as you toggle between page types.
• Guides are now available to help you align tables with other content on the page.

Why is this important?

This new feature gives you more control over the layout of your tables, making it easier to create visually appealing and informative content. It also makes it easier to collaborate on tables, as everyone will see the same table size.

How do I use it?

To resize a table, select and drag the resize handle located on the right side of the table.

The columns will proportionally grow or shrink based on the table size that you set.

Extended media resize experience

You can now resize media elements to any width. You can also update the pixel values for the width and height of a media element in the media toolbar.

What's new?

• You can now resize media elements to any width, not just the predefined sizes.
• Pixel values for the width and height of a media element will now be displayed in the media toolbar.
• These values can be updated to change either the width or height of a media element. Note that changing one value will update the other proportionally.
• Guides that were previously hard snapping are now soft snapping. This means that you can now select any custom size for a media element, and it will resize to that size, even if it is not a guide value.
• Guides will now show other media or elements on a page that you can align sizing to.

Why is this important?

This new feature gives you more control over the layout of your media elements, making it easier to create visually appealing and informative content. It also makes it easier to collaborate on media elements, as everyone will see the same media size.

How do I use it?

To resize a media element, select it and drag the resize handle located to the right or left of the element. The height will be resized proportionally to the width.

To update the pixel values for the width or height of a media element, open the media toolbar and enter the desired values.

Existing media

Media added to a page before this update will be using the old percentage-based sizing. To resize these items, they will need to be converted to the new pixel-based sizing. To do this, select the media item and use the drag handle to resize it, or select the Convert to pixels button in the toolbar. Media items that need conversion will have a yellow dot in their top-right corner.

Display Jira issues on a Confluence page with more options

We've made 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 - Display your Assets object data on a Confluence page

We're excited to announce the early access launch of a much-requested feature for Assets - the ability to display your Assets data in Confluence using macros!

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:

• Navigate to a Confluence page you own
• Enter / on your keyboard
• Search for Assets in the dropdown menu search bar, then select Assets
• After Insert objects from, select the object schema that stores the objects you want to display
• Enter an AQL query to filter down the objects you want to be displayed. Learn more about AQL queries.
• Select Insert objects

Learn more about displaying Assets in Confluence.

Better filters for admins managing guest access

Admins now have a better filtering experience to help them manage guests' access to their site.

First, we made it easier to find and assign space access to guests who have no space assigned. Just select the Guests with no access filter next to the search field.

If a guest doesn't have a space assigned, then they can't access Confluence at all.

We also added a Guests from a group filter. This will filter the guest list by members of a specific guest group.

For example, say you have a guest group in Atlassian Administration called "acme-contractors". You can add "acme-contractors" to the Guests from a group filter and get a focused view of only the guests who are members of that group.

With any filter applied, you can simply audit or you can perform bulk actions like assigning all guests matching the filter criteria to a new space.

You can find the Guests from a group filter by opening More filters.

To add a group to the filter:

1. Open the Select a group dropdown.
2. Start typing a group's name to search for it and select the one you want from the results.
3. Or select from recent groups.

You can add multiple groups to the filter field. This will show results for guests who have membership in all of the groups selected.

Automation: Audit log date filters

When viewing the audit log in Automation, you can now filter entries by date and time. This is handy if you want to find all rule executions that happened between certain times, or if you want to troubleshoot an error that occurred before a certain date.

1. Navigate to Automation
2. Select Audit log.

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

Share content externally with public links (general availability)

Public links let you share a safe, view-only version of any Confluence page with anyone on the internet. And with this release, they'll be available to all customers on paid Confluence plans (previously, public links were only available to a few early adopters).

For admins, we've included key functionality to fine-tune which spaces should allow public links and which shouldn't.

We've also included ample functionality to help you have visibility into where public links are allowed and used. You'll be able to keep an eye on and control this through an admin dashboard for both product admins (in global permissions) and space admins (in space permissions).

You'll also get notified whenever someone allows public links at the site or space level, as well as whenever someone turns on a public link (and can opt out of those notifications if you want).

Lastly, for Premium and Enterprise customers, we've built you some powerful bulk actions that help you audit and take action on public links at scale.

For more details about public links, see our post on Community.

Or you can dig into our support articles.

We’re making it easier for your team to access Confluence

Before, people who weren’t admins had to request to access Confluence. This request was sent as an email to their admin who could then approve or deny the request.

Now, people who aren’t admins can try Confluence 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 Confluence. 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.

Early Access Program: Use Atlassian Intelligence to help write or edit content

At this time, Atlassian Intelligence is only available for customers who have signed up to our Early Access Program. Sign up for early access

Atlassian Intelligence for Bitbucket Cloud is a new virtual teammate to help you and your team to work more effectively. Using artificial intelligence and machine learning, Atlassian Intelligence is a tool that is integrated into our cloud-based products. Learn more about AI in Bitbucket Cloud

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