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

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.

Filter the user list with added roles

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

The roles we’re introducing include:

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

To filter the user list by roles:

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

Add a custom domain for your help center

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

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

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

To add a custom domain:

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

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

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

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

Option 1: Manually set up user provisioning

Recommended when you need:

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

Learn how to add an identity provider for this option

Option 2: Automatically set up user provisioning

Recommended when you need:

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

Learn more about Azure AD for nested groups

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

Learn more about identity providers

Control whether members use API tokens to authenticate

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

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

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

To try out the API token setting:

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

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

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

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

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

Learn more about tracking activities from the audit log

To see audit log activities for all data security policies:

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

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

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

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

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

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 helps teams accelerate work, increase efficiency, and provide value faster using artificial intelligence (AI). Learn more about Atlassian Intelligence

To activate Atlassian Intelligence for your products:

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

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

Update Jira and Confluence links after migrating to cloud

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

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

Learn more about updating links

To get started with this change:

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

Gain security insight with more charts

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

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

To access new charts:

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

Additional self-serve data residency move window options are available

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

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

Schedule move in the maintenance window

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

Schedule move within the next 48 hours

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

Schedule move in a 24-hour window

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

Support team will manage your move

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

To schedule a data residency move:

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

Additional improvements to information within Product updates

You can now see the rollout schedule details on the release note cards.

We've also included the rollout schedule information in the header of the details page.

1. Go to admin.atlassian.com.
2. Select your organization if you have more than one.
3. Select Products.
4. Select Product updates.

Epic field improvements

We've improved editing an issue's Epic field from the backlog. Most importantly, we've reduced our load time.

Also, any epics you selected recently now show at the top of the list, making it easier to find and select the epic you need.

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.

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.

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.

Removing the original theme across Jira Cloud products

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

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

Update to the create issue mini window

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

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

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

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

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

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

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.

Work more securely with your collaborators in Jira Cloud

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

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

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

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

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

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.

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.

Enabling more boards in company-managed projects to create cards in columns

We're bringing the Create issue button to more complex boards in company-managed projects; previously it was only available for Kanban boards using a default workflow and default board filter.

This functionality will now be available for boards with modified workflows. For example, boards with columns associated with multiple statuses. If you have a board like this, you should now see a Create issue button appear in columns on your board.

Over the coming months, we will enable this functionality for even more boards in company-managed projects.

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.

Removed object IDs in Assets screens

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

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

Refine your board with quick filters

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

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

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

Create issues from the board in company-managed projects

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

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

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

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

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

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

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 code repositories, security containers, and Confluence spaces.

To get started:

1. From the top menu, go to Projects > Create project.
2. Choose a project template, a project type, and enter a name and key for your new project.
3. From the the Connect your tools screen, connect your code repositories, security containers, and Confluence spaces.

You’ll see this screen and be able to connect your work if you have one of these tools connected to your site:

• Bitbucket
• GitHub
• Confluence
• Snyk
• JFrog
• Mend
• Lacework
• Stackhawk

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.

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

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

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

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

Learn how to configure columns and statuses

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

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

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

To connect pending Bitbucket workspaces on the Code page:

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

To connect pending Bitbucket workspaces using the development dialog:

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

Read more about integrating Bitbucket with Jira

New Parent field in company-managed projects

We're improving the way you associate epics with your bugs, stories and tasks in Jira by replacing the existing Epic link and Parent link fields in company-managed projects with the Parent field, consistent with team-managed projects. Read more about these changes on the Community

With this release, we've introducing the following changes:
• the Parent field is now available when creating new schemes and layouts
• the existing Epic link and Parent link fields have been replaced with the Parent field in the issue view, and when creating new issues and workflow transitions
• the Add parent feature seen in team-managed projects has now been added to the company-managed issue view
• the parent JQL function now includes the functionality of the epic link, parent link and parentEpic functions

Move a mighty amount of issues from a completed sprint

Didn't get through all the issues you'd planned to in a sprint (we're talking more than a thousand or so)?

Take a moment to pause while they're dropped into a new sprint, a sprint that you've already created, or your backlog.

Configure your swimlanes on a Kanban board

Organize the issues on your board vertically, horizontally, and with increased accessibility. Whoa.

Add swimlanes to your Kanban board with a refreshed settings experience. From your board, go to ... then Configure board > Swimlanes.

Sort your issues by a JQL query, assignee, epic, story, or project to get a better view of what you and the team are working on.

Identify issues with card colors

Add a color to your issues to quickly identify your work. Colors can be based on a Jira query, issue type, priority, or assignee.

This is a refreshed experience — the modernized UI is also more accessible and it adopts the global Jira color picker, decked out with a palette of recommended hues.

To add a color, go to your board, then More ... > Configure board. From the Card Colors page, select a method then pick a color.

Track and triage incidents affecting your services in Jira

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

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

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

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

To get started with the incidents feature:

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

To turn it on manually:

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

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

Finish setting up your development tools from the issue view

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

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

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

To get started:

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

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.

New project details page for company-managed service projects

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

Introducing a new workflow editor in company-managed projects

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

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

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

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

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

Learn more about the new workflow editor.

Choose which customer detail fields appear on the issue view

Admins of projects using the Customer service management feature can now choose the detail fields they want to show on the issue view.

To choose which fields appear on the issue view:

1. From your service project, go to Customers.
2. Select the name of any customer.
3. Select Customer actions (•••), then Edit details.
4. Use the toggles to enable the fields you want to appear.

Make edits on a form without opening up edits for customers in the portal

You can now edit a form on issue view without it also opening edits for customers in the portal view. Simply select Edit form when you’re wanting to make edits yourself without giving your customer editing power. When you need to request customer changes, or ask customers to complete new forms, select Open customer edits.

We’ve also made improvements to form settings so you can understand and see your selected preferences much more clearly.

Read more about opening customer edits on a form, or about form states

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.

Categorise your services with types

Services just got types!

To add a type to a service:

1. Go to Services
2. Select the service to which you want to add a type
3. Select Service type and select a type from the menu

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

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

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

Find out more in our Community blog

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

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

To set up emoji rules in automation:

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

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

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

Template bundles in the project create page

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

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

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

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

Another way to create a bundle is to:

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

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.

Import data directly from monday.com into Jira Work Management

Moving your work from monday.com to Jira Work Management just got easier. Using the monday importer, you can directly import projects into Jira Work Management.

Save the effort of manually moving data and ensure the project information is relevant and accurate.

To directly import your data using the monday importer:

1. From the navigation bar, select Projects > Create project.
2. From the sidebar, go to More > select Import data.
3. Select Import to a new business project.
4. In the import from an app section, select monday.

Colourful categories

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

Removing background customization from left side navigation

To prepare Jira Work Management for future changes, we're removing background customization from the left navigation. If you have any questions, reach out to our support team.

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.

New grant access emails enabled

We’re updating our email communications to better serve you. Here’s what’s changing:

• New email design for a better user experience

Confluence Public Links Persistent Lozenge

Additional contextual education on public link pages allow for anonymous visitors to make the connection between their content and other Confluence features, faster.

Protect your progress with autosave while using the Roadmap Planner macro

The roadmap planner macro will now autosave changes for you every 15 seconds, so important progress won't be lost or inadvertently discarded.

If you do want to discard changes you've made while creating or updating your roadmap planner, select Close to exit the modal, then revert the page to a prior version via Page history.

Share content externally with public links

Public links let you share a safe, view-only version of any Confluence page with anyone on the internet. 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.

You'll have ample functionality to give you 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).

Notifications will be sent 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).

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 dig into our support articles.

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)

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.

Get to know the new sidebar

We've redesigned the sidebar to make it sleeker, more intuitive, and more compact. As part of this change, we've added a new All content item where you can discover content and search within a space. We've also rearranged sections for Shortcuts, Content, and Apps and made them expandable. Finally, we've added tooltips for sidebar elements — along with a few other accessibility features.

Confluence Premium: Delete a selection of pages at once

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

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

Learn more about deleting pages

To delete a selection of pages at once

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

To restore or permanently purge deleted pages:

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

To view archived pages:

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

Template suggestions in the page editor

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

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

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

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

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

Block page and blog exports from space settings in Confluence

Customers with Atlassian Access will now be able to block exports of pages and blogs from Confluence spaces via PDF, CSV, HTML, Word, and XML in Confluence.

Previously, the data export rule allowed customers to block exports directly from pages and blogs but didn’t block users from export of that content from Confluence spaces. With this change, exports of pages and blogs will be blocked at both the page and space level.

Learn more about preventing data exports

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.

Use filters to search and display Jira issues

Now you can use filters to search for Jira issues and display them in a table, without leaving the Confluence page.

This improvement follows the release that allows you to search for issues using keywords or JQL, and flexibility to add, remove, and reorder fields.

How to display Jira issues in a table

Start using filters to search for Jira issues:

1. Create a new Confluence page or edit an existing one.
2. Type /jira and select Jira issues.
3. With Basic selected, use the filters to search by Project, Type, Status, or Assignee.
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.

Restore and reattach inline comments, even after deleting highlighted text

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

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

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

Guests can request licensed user access

Guest users can request licensed user access directly from content found within their organization's site but outside of their assigned space.

Cache key support for self-hosted runners

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

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

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

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

Learn more about the Opsgenie integration framework