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

Keep group names up-to-date

Correct pesky spelling mistakes and keep your group names up-to-date with the ability to rename groups.

This feature is currently in beta and is only available for organizations with the improved user management. This feature isn’t currently available for groups used within some Jira administration settings. Check out the Community announcement.

To rename a group:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Directory > Groups.
3. Select the group that you want to rename.
4. Select the More actions icon (•••) next to Add group members.
5. Select Edit group name and enter a new name.
6. Select Save changes.

Learn more about updating groups

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

Copy data from one instance of your Confluence Cloud to another

As an org admin, when your organization adds or reorganizes teams, you may need to move data from one instance of your Confluence Cloud to another. You can move users, spaces, and related data within or across organizations.

Learn more about what we copy

To access this feature:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Copy product data.

For detailed instructions about how to copy data, see Start copying Confluence data.

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

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

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

To set up SAML SSO for portal-only customers:

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

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

Add a custom domain for your help center

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

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

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

To add a custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select the Custom Domains tab.

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

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

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

Option 1: Manually set up user provisioning

Recommended when you need:

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

Learn how to add an identity provider for this option

Option 2: Automatically set up user provisioning

Recommended when you need:

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

Learn more about Azure AD for nested groups

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

Learn more about identity providers

Control whether members use API tokens to authenticate

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

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

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

To try out the API token setting:

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

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.

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.

Activate Atlassian Intelligence for your organization's products

You can now activate Atlassian Intelligence features for your team's products. Atlassian Intelligence is a virtual teammate that helps your organization work more efficiently with artificial intelligence. Learn more about Atlassian Intelligence

To activate Atlassian Intelligence for your products:

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

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

Include subtasks when calculating workload by assignee

We've added an option to include subtasks when viewing workload by assignee via the backlog in company-managed projects.

To see this change, go to the backlog view in your company-managed scrum project. Select the More menu (...) next to any avatar icon, which will open Workload by assignee. Use the toggle to Include subtasks in estimates in the sum of estimates for each assignee in the sprint.

Filter backlog by subtask on company-managed projects

We've brought a subtask filter to the backlog view in company-managed scrum projects.

To use this new filtering option, select the Type filter from the backlog view, then select Sub-task.

If your team uses a custom name for subtasks, it will appear in the issue type filter instead of Sub-task.

Searching for issues just got faster in Jira Cloud

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

Add status while creating an issue

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

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

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

OAuth upgrade for Microsoft email servers

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

To configure your Microsoft mail server using OAuth:

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

Learn more about how to configure your mail server.

Update to the create issue mini window

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

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

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

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

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

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

M2 Manage all of your customer organizations in Jira Service Management

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

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

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

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

Get better results by refining your search with more criteria

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

To get started with this change:

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

Early access program: Customize priorities for your projects

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

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

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

Custom navigation colors are now compatible with dark theme

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

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.

It’s faster and easier than ever to add people to Jira with Slack

If you use Slack it’s now the default way to add people to Confluence. That means if you already have Slack connected as a connected app in admin hub, it will become the default channel to send invitations to other people to join you in Confluence.

This change only applies if you have Slack listed as a connected app.

You can check to see if this change applies to you by going to Confluence, selecting ‘Teams’ from the menu at the top, and selecting ‘Invite people’ from the menu that drops down.

You can also check or change this by following these steps:

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

2. This step is different depending on your user management experience:
Original: Select the site's name and URL to open the Admin for that site.
Centralized: Select Products then select the site from the left hand side.

3. Under Site settings, select Connected apps.

4. Select Revoke next to where Slack is listed.

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.

Improved accessibility for the project settings details screen

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

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

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

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

Migrate Jira users and groups in advance

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

• All users and groups

• (Optional) Group membership

• (Optional) Jira Service Management customers

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

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

Learn more about migrating Jira users in advance

To get started:

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

Advanced Roadmaps is now officially Plans in Jira Software Premium

"A rose by any other name would smell as sweet" - some old guy

At the start of November, we posted a community article announcing that the planning feature formerly known as Advanced Roadmaps (formerly formerly known as Portfolio for Jira) is getting a new name. This change does not impact existing functionality of plans in Jira Premium. Read our community posting to learn more about this name change.

With the publication of this release note, we've now wrapped up most of the in-product changes to reflect this new name. Again: no changes in functionality, but there are some small places in-product where that now reflect this new name. For example, what was once Advanced Roadmaps permissions is now Plan permissions; small things like that.

Now that this change is finalized, the documentation and supporting materials will soon update to reflect this change (if they haven't already).

Automation recommendations on the board

With this release, you can easily setup a rule to automatically create an issue when critical vulnerabilities are found. This automation recommendation will appear in your Jira board's automation menu from where you can action it.

1. Go to the Automation menu in your Jira board.

2. Select Create rule from within the recommendation banner where you'll be able to setup the automation rule.

3. You can select See more templates to view all other templates.

This recommendation will be visible if:

• the project has vulnerabilities and there is no existing rule with the trigger “When a critical vulnerability is found”.
• you’re an admin.

No more duplicate fields on forms containing linked Jira fields

Avoid fields appearing twice on request types that use forms. Now when you’re in the form builder and link a form field to a Jira field that is already in use on an associated request type, we’ll remove it for you on the request form. The same goes when configuring your request types. Form fields will be unlinked in forms that contain linked Jira fields that are duplicated. This means customers and agents will no longer have to see two of the same field on the one request.

Find out how to link a form field to a Jira field, or see examples to understand more about duplicate form fields and Jira fields.

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

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

Advanced Roadmaps - Update issue status directly from your plan

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

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

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

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.

Increasing the visibility of the create issue mini window

We want to help people discover the new create issue mini window, which has recently been re-designed. We’ll open the mini window by default the next time you create an issue.

It’s easy to switch back to full screen with the icons on the top right of the mini window. We’ll remember the state you prefer for the next time you create an issue after that.

However, we encourage people to try using the mini window. It has significantly more flexibility than the full screen window as you can move around your instance and interact with other issues without losing progress on the issue you're creating.

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

Advanced Roadmaps: New look for the Confluence Macro!

Out with the old and in with the new! When you embed your plan in a Confluence page, you'll now see a new and improved layout.

This new design not only looks better, but also shows more plan viewing tools when embedded. Without leaving your Confluence page, you can:

• adjust filters
• view the warnings menu
• toggle between Timeline vs. List mode and
• change view settings

Add custom fields from team-managed projects to issues in your plan

You can now add custom fields from team-managed projects to issues in your plan. Unlike global company-managed fields, these custom fields can only be applied to issues from that same team-managed project.

1. Select Plan settings from the left side navigation.
2. Choose Custom fields to show you all of the custom fields currently in your plan.
3. Select Add custom field in the upper right corner, then search for the fields you want to add.
4. Use the Add fields button to finalize your choice.

Together at last, Atlas goals and Jira Software Premium plans

Give your goals context in Atlas. Then link the bigger picture from Atlas goals to granular work in plans.

Integrate Atlas with Jira Software Premium so your team can see how their work ladders up to something much bigger.

Company-managed projects: Quickly assign versions to issues in your backlog

To help your team plan and ship work faster, you can now assign versions to your issues without leaving the backlog.

In your company-managed backlog, right-click on an issue to open the contextual menu, hover over Version, then select the version you'd like your issue assigned to.

Export your project timeline as a CSV file

Sharing's caring! Share your project timeline with offline users as a CSV file for presentations and other documents.

To export a timeline as a CSV file:

• Above your timeline, select 
  Export in the top right corner.
• Set the Timeline view Start date, and End dates, then select 
  Export. The CSV file is automatically downloaded through your browser.

Plans - Filter by dependency type in the Dependencies tab

When looking at the Dependencies tab in your plan, you can now filter by the type of dependency.

Store data on your device in Jira Software

Store frequently accessed data on your device to increase the performance of your board and backlog.

To enable this feature, select your avatar in the top right of a Jira project, then go to Personal settings. Scroll to find Jira Labs, and switch on the toggle to Store data on your device.

Chat in Slack: Turn on or off customer satisfaction surveys per project

Chat for Slack now respects your customer satisfaction (CSAT) survey preferences in your project settings. If you have CSAT turned off for a project, Assist won’t collect feedback in that project’s Slack chat channels.

If you migrated from Halp to Jira Service Management, requesters will now rate their help experience on a 1-5 star scale. This matches how Jira Service Management collects CSAT. Before, Halp asked requesters to rate their experience as a thumbs up or a thumbs down.

Find out more about CSAT surveys

To manage CSAT surveys:

1. From your project settings, select Satisfaction settings.
2. Turn on or off Collect customer satisfaction feedback.

No more duplicate fields on forms containing linked Jira fields

Avoid fields appearing twice on request types that use forms. Now when you’re in the form builder and link a form field to a Jira field that is already in use on an associated request type, we’ll remove it for you on the request form. The same goes when configuring your request types. Form fields will be unlinked in forms that contain linked Jira fields that are duplicated. This means customers and agents will no longer have to see two of the same field on the one request.

Find out how to link a form field to a Jira field, or see examples to understand more about duplicate form fields and Jira fields.

Introducing a new workflow editor in company-managed projects

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

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

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

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

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

Learn more about the new workflow editor.

New project details page for company-managed service projects

We've updated the project details page for company-managed projects with a redesign that matches the clean, sleek look of our team-managed project details page. As part of this update, you can also enjoy more formatting options for the project description.

Automation: System rules

Some project templates will now come with System rules - rules that are set up automatically when the project is created. These rules won't count towards your monthly automation usage. They also can't be modified, but they can be disabled.

Learn more about system rules

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.

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

Group your SLA goals by priority

We’ve heard from many of our customers that they are repeatedly hitting SLA goal limits in Jira Service Management projects.

You can now unlock greater capacity for your SLA goals by grouping them around priorities. A goal can have several priority-based time targets under it and still count as just one goal. This allows you to reduce your dependency on the goal limit through more efficient goal configurations.

The feature also includes some quality-of-life and user experience improvements to make managing and updating your SLAs easier. To see any changes or improvements to your goal configuration, you’ll need to review and edit your SLAs so your priorities are grouped under the relevant goals.

Find more info about grouping SLA goals by priority.

You won't notice any changes to your SLA configuration until you start editing your goals. Find out more about how to edit goals.

Once you start editing your goals, you can group priorities under a single goal to create more efficient configurations.

Improved search results in your help center

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

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

Introducing customer notification logs for request-related actions

With the latest enhancement, project admins can now view logs for undelivered customer notifications, triggered due to actions taken on requests. You can view the reason for failure and take necessary actions.

To access these logs, go to your service project, and select Customer notification logs. Then, select Request notifications where you’ll find details like the recipient, the name of the notification, when it was sent, the issue key, and why it wasn’t delivered.

Learn more about customer notification logs

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

Increasing the visibility of the create issue mini window

We want to help people discover the new create issue mini window, which has recently been re-designed. We’ll open the mini window by default the next time you create an issue.

It’s easy to switch back to full screen with the icons on the top right of the mini window. We’ll remember the state you prefer for the next time you create an issue after that.

However, we encourage people to try using the mini window. It has significantly more flexibility than the full screen window as you can move around your instance and interact with other issues without losing progress on the issue you're creating.

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.

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

Faster imports from Trello into team-managed business projects

You can now import Trello data into team-managed projects in Jira Work Management using the Trello importer.

Faster direct imports from Asana into team-managed business projects

You can now import Asana data into team-managed projects in Jira Work Management using the Asana importer.

Colourful categories

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

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.

Calculate delivery progress based on story points

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

Creators can configure the delivery progress field:

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

Learn more details about the estimation rules and configuration options.

Improved accessibility for the project settings details screen

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

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

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

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

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

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

Enable notifications grouping

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

To open grouped notifications:

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

Copy data from one instance of your Confluence Cloud to another

As an org admin, when your organization adds or reorganizes teams, you may need to move data from one instance of your Confluence Cloud to another. You can move users, spaces, and related data within or across organizations.

Learn more about what we copy

To access this feature:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Copy product data.

For detailed instructions about how to copy data, see Start copying Confluence data.

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

React more quickly with default reactions

Three reactions (thumbs up, clap, tada) will now be shown on pages with no reactions, instead of the reaction picker button.

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.

Template suggestions in the page editor

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

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

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

Display Jira issues on a Confluence page with more options

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

To insert Jira issues:

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

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

To edit your table of Jira issues:

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

Open Beta: Surface your Assets objects in Confluence

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

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

To use this feature, you must have access to Assets through Jira Service Management Premium or Enterprise.

To embed a table with Assets objects:

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

Learn more about displaying Assets in Confluence

Confluence Premium: Discover automation in context

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

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

Learn more about Confluence automation

It’s faster and easier than ever to add people to Confluence with Slack

If you use Slack, it’s now the default way to add people to Confluence. That means if you already have Slack connected as a connected app in admin hub, it will become the default channel to send invitations to other people to join you in Confluence.

This change only applies if you have Slack listed as a connected app.

You can check to see if this change applies to you by going to Confluence, selecting ‘Teams’ from the menu at the top, and selecting ‘Invite people’ from the menu that drops down.

You can also check or change this by following these steps:

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

2. This step is different depending on your user management experience:
Original: Select the site's name and URL to open the Admin for that site.
Centralized: Select Products then select the site from the left hand side.

3. Under Site settings, select Connected apps.

4. Select Revoke next to where Slack is listed.

Confluence Premium: Announcement banner improvements

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

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

Learn more about configuring an admin announcement banner

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

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

Create new pages or Jira issues using /create

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

To create a new Jira issue using /create:

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

To create a new Confluence page using /create:

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

Confluence Premium: Automation in sidebar navigation

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

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

Learn more about Confluence automation

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

Reactions replace likes in Confluence home feed

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

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

Assess and prepare users in the Confluence Cloud Migration Assistant

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

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

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

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

Learn more about assessing and preparing users

To get started:

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

A better sharing experience for whiteboards

Whiteboards now have the same Share button functionality as pages and blogs, which means you can not only copy the link, but also send the whiteboard to individual people, groups, or teams and share the whiteboard in Slack directly from Confluence.

Confluence email notifications now support HIPAA compliant operation

For instances designated by HIPAA customers as containing sensitive data, the email notifications don't include any content that could potentially contain protected health information.

Improvements to trusted domains in Confluence Cloud Migration Assistant

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

Trusting the domains via the CSV file

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

More improvements

Other improvements include:

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

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

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

Learn more about reviewing email domains

To get started with this change:

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

Elevate Team Calendar Productionization for Standard

Currently, admins on the Standard plan can try team calendars when they start a Premium trial.

With this new enhancement, space admins (and above) can now opt to hide the team calendar upsell from their Confluence site. Users on this site will also be unable to see the team calendar tab or upsell within Confluence.

1. To hide team calendars, go to Space settings and find the Manage space section.

2. Under the Edit sidebar tab, look for Calendars and toggle the setting to off (X).

Dark Mode: Removing Original Theme

Users will no longer be able to choose the Original Confluence color theme. The new Light theme replaces the classic look.

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