Atlassian Cloud changes Jun 17 to Jun 24, 2024

These changes have recently been rolled out to Atlassian Cloud sites.

Changes labeled ROLLING OUT are being gradually rolled out and may not be on your site just yet.

Atlassian Administration

Atlassian Administration is where you manage your Atlassian organization, including user access to products, security settings, and billing preferences.

Exclude pages from content scanning detections

ROLLING OUT NEW THIS WEEK

Guard Detect sends an alert when someone updates a Confluence page containing certain types of sensitive data, such as credentials, financial, or identity data.

You can now exclude certain pages from content scanning detections. This is useful if you are getting false positive alerts for particular pages. For example, if you have a page containing test credit cards for your QA team to use, you can exclude that page from the credit cards content scanning detection.

Requires Atlassian Guard Premium.

To exclude a page from a detection:

  1. In Guard Detect, go to Detections > Content scanning
  2. Expand the detection then select View exclusions.
  3. Follow the prompts to add pages to the list of exclusions.

Alternatively, you can select Exclude page on the alert for that page.

How to exclude a page

Copy Jira data from one instance to another in Atlassian Administration

ROLLING OUT NEW THIS WEEK

We’ve moved the Jira cloud-to-cloud migration feature to Atlassian Administration. You can copy your Jira projects, issues, and related data, along with Confluence data, from one central location.

To copy Jira data:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.
  2. Select Settings > Data management > Copy product data.
  3. Select Create copy plan.
  4. On the How it works page, select Next.
  5. From the Select a product page, select Jira.
  6. Follow the prompts to copy Jira data.

Prevent people from exporting content in specific spaces and projects

ROLLING OUT NEW THIS WEEK

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

To create a new data security policy or view existing policies:

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

Improved experience for moving Marketplace apps to another location

ROLLING OUT NEW THIS WEEK

Improved experience for app data residency with email notifications for scheduled moves, when moves are in progress, and when they are completed, cancelled, or failed.

To request a data residency move for apps:

  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 View details.
  4. Select the Eligible tab.
  5. If you have eligible apps, select Move apps.
  6. Review information about the steps involved in moving your eligible apps. Select Next.
  7. Review the apps. Select Next.
  8. Select the 24-hour move window. Select Next.
  9. Review your app data residency move details. Select Submit request.

More about moving your apps to another location

Filter the user list with added roles

ROLLING OUT

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

ROLLING OUT

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

Brand your Jira products with a custom domain

ROLLING OUT

You can now use custom domains to brand your Jira products. Custom domains provide easy-to-remember URLs for your users to access your products.

You can create a custom domain if you have a Jira Premium or Jira Service Management Standard plan.

Previously, this feature was only available for Jira Service Management help center. Tell me more about custom domains

To create 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 Add custom domain. This is only visible if you have an eligible product.
  4. Review the Before you add a custom domain page, and select Next.
  5. Select which product you want to access from your custom domain.
  6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
  7. Enter a Redirect URL. This is optional.
  8. Review changes and select Create domain.

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

ROLLING OUT

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

ROLLING OUT

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.

Find Atlassian Administration settings faster

ROLLING OUT

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

COMING SOON

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.

Create custom domains for your Jira products

ROLLING OUT

We removed keyword restrictions when you create custom domains. You will no longer have a fixed list to select keywords for subdomains. Instead, you have the ability to manually enter your own subdomains.

Jira family products have also been given added support. You can now select Jira products from the dropdown menu when you create a custom domain.

To create 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 Add custom domain. This is only visible if you have an eligible product.
  4. Review the Before you add a custom domain page, and select Next.
  5. Select which product you want to access from your custom domain.
  6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
  7. Enter a Redirect URL. This is optional.
  8. Review changes and select Create domain.

Get fresh insights about your organization

ROLLING OUT

You can now manually refresh your organization’s insight charts. Additionally, we’ve added timestamps under each chart.

If you don’t refresh your charts, they’ll automatically refresh every 24 hours. Tell me more about organizational insights

To manually refresh a chart:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.
  2. Select Security > Insights.
  3. From a chart, select the refresh button at the bottom left.

Data residency is now supported in six new regions

ROLLING OUT

We're launching data residency in United Kingdom, Japan, India, Brazil, South Korea, and Switzerland to allow you to control where your data is stored.

There are a few limitations with these new locations. Find out more about any limitations

We're adding these locations to the list of supported locations in phases, so expect to see updates in the coming weeks.

To schedule a data residency move for the United Kingdom, Japan, India, Brazil, Switzerland, and South Korea:

  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, and select the desired country as the location.

Discover more about data residency

Data residency for Marketplace apps

ROLLING OUT

When evaluating data residency for your apps, you might see some apps listed as "No action available."

This means that some app partners declare that their apps don't need to be pinned or migrated because their apps exclusively store data within the Atlassian product. Another reason is that the apps may not store any data in the scope of the Marketplace partner's data residency policies.

To request a data residency move for your apps, you will have first to move your product. Learn more about how to move your product from one location to another

Once your product has been pinned to your selected location, you can move your eligible apps to the same location. Learn more about data residency for Marketplace apps

Stay on top of your organization’s security

ROLLING OUT

We improved the security guide so you can see your security setup in one place.

Understand your organization’s mix of users and their login methods at a glance. Then, review your security recommendations to keep your users and data protected.

To go to the security guide:

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

Copy Confluence data: Move users related to spaces you want to copy

ROLLING OUT

When you move data from one instance of your Confluence cloud to another, you can move spaces, and only users who contribute to the spaces.
This means that when you add or reorganize teams, you can move spaces and only the related users you want, instead of all users. This will help you copy data:

  • in small chunks
  • in multiple phases
  • quicker and reduce your overall downtime.

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.
  3. Select Create copy plan.
  4. On the How it works page, select Next.
  5. Select your source and destination.
  6. Select the spaces you want to copy.
  7. On the Copy users and groups page, select Copy users and groups related to the selected spaces from the Users and groups section.

We’re replacing Jira Software with Jira in CSV exports

ROLLING OUT

We’re bringing together Jira Work Management and Jira Software to make Jira your one tool to plan and track work.

As a part of this, we’re replacing the "Jira Software" header with "Jira" in the CSV files you export.

We recommend checking and updating any scripts that may be affected by this change.

Apply a data security policy to classified data

Classification is the process of categorizing the sensitivity of information.

To reduce the risk of data exfiltration and unauthorized access you can now apply data security policies to your classified content. What is a data security policy?

You can apply the following rules to classification levels:

  • Block data export in Confluence, Jira, and Jira Service Management
  • Block the creation and use of public links in Confluence
  • Block anonymous access in Jira and Jira Service Management

Requires Atlassian Guard Premium subscription.

To create a 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. Create a data security policy and select Classification level as the coverage type.
  4. Follow the prompts to configure the available rules.

Classify and protect your sensitive information

Keep your organization’s data protected by labeling sensitive information in your products. You can now set up classification levels for your users to classify pages, blogs, issues, and requests. You can also apply data security policies to your chosen classification levels. More about data classification

Data classification is available in Confluence, Jira, and Jira Service Management and requires an Atlassian Guard Premium subscription.

To create a classification level:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.
  2. Select Security, then Data classification.
  3. Select Create a new classification level.
  4. Select Get started and enter the relevant details.

Publish your classification levels when you’re ready for people to start classifying their work. Once a classification level is published, you can also add it to a data security policy to reduce the risk of data exfiltration and unauthorized access.

It’s now faster to copy data to your sandbox

ROLLING OUT

Save time copying data to your sandbox by choosing only the projects and spaces you need. Understand how to select data to copy

To copy specific Confluence spaces or Jira projects from production to its sandbox:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.
  2. Select Products, then Sandbox.
  3. From Actions in the product table, select Copy production data.
  4. Select the Specific projects or spaces.
  5. Follow the prompts to copy data into your sandbox.

Find out what we copy to the sandbox

Atlassian Access is becoming Atlassian Guard

ROLLING OUT

We are changing the Atlassian Access name to Atlassian Guard. This change reflects the expansion of our security solutions beyond identity and access management.

You’ll see the new name in Atlassian Administration on June 12, 2024. The capabilities you currently have with Atlassian Access remain unchanged.

Explore the future of Atlassian Guard

Atlassian Access is now Atlassian Guard

ROLLING OUT

We updated the Atlassian Access name to Atlassian Guard in Atlassian Administration on June 12, 2024. The capabilities you currently have with Atlassian Access remain unchanged.

Explore the future of Atlassian Guard

Prevent people who are not logged in from viewing Jira issues

ROLLING OUT

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the anonymous access rule to prevent people who are not logged in from viewing issues in specific projects or across entire Jira product instances. Previously, this was only available for policies that covered classification levels.

The anonymous access rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

To create a new data security policy or view existing policies:

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

Prevent people from exporting Jira issues

ROLLING OUT

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the data export rule to prevent people exporting issues from entire Jira sites. Previously, this was only available for policies that covered classification levels.

The data export rule requires Atlassian Access (soon to be known as Atlassian Guard Standard)

About data security policies

If you already have a policy that covers Confluence products, you can edit the policy coverage to include Jira product instances.

Alternatively, create a new 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 Create policy.

You’ll then be able to configure what product instances your policy will cover and add rules to protect that data.

We’re replacing Beacon with Guard Detect

ROLLING OUT

This update only applies to organizations that participated in the Beacon or Atlassian Information Security beta.

Beacon (beta) will soon be part of Atlassian Guard Premium. Read the blog

We’re replacing ‘Beacon’ with ‘Guard Detect’ in the CSV files you export. The name of your groups (such as beacon-admins) will not change.

In Atlassian Administration, you’re able to export CSV files for:

  1. Managed accounts
  2. Audit logs
  3. External users
  4. User API tokens
  5. Authentication policies

We recommend checking and updating any scripts that may be impacted by the change.

We’re changing our email notification sending domain

ROLLING OUT

We’re in the process of changing the sender domain for email notifications that are currently sent from am.atlassian.com. Some will migrate to id.atlassian.com and some to atlassian.net.

We want to ensure that account management emails, like password resets and 2-factor authentication, are sent through a separate sender domain and IP addresses.

When sending emails from a new domain or new IP address, there’s a risk that the receiving mail servers or inbox provider won’t recognise the email as legitimate and classify them as spam. To ensure this doesn’t happen, you can add the domain and IP address to your allow list.

Be alerted when a Bitbucket workspace or repository is made public

If you’re a software team, your code is among your organization’s most valuable data.

Guard Detect (formerly known as Beacon) now generates an alert when an admin makes a Bitbucket workspace or repository open to the public.

Whether the change was due to a misconfiguration or a bad actor, your security team is alerted in real time, so they can investigate and act quickly to secure your codebase.

Requires Atlassian Guard Premium.

To get alerts for Bitbucket link your Bitbucket workspace to your organization in Atlassian Administration. Link Bitbucket to your organization

Jira platform

Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product.

Improved Assignee functions in the New Workflow Editor

ROLLING OUT NEW THIS WEEK

Yet another small but mighty improvement to the workflow editor coming your way!

This change brings the Assignee functions from the old workflow editor to the new one. You can now do the following for both company-managed and team-managed projects:

  • Assign to current user, lead developer, or reporter
  • Update issue field such as assign issue to a specific user, remove assignee, assign to automatic (default assignee)

This is one part of our series of small but mighty changes to the workflow editor. Read our community post about these changes to learn more.

Bulk edit issues in Jira list

ROLLING OUT NEW THIS WEEK

Bulk edit up to 1000 issues at one time from your Jira list.

To bulk edit multiple issues:

  1. Select multiple issues from your list using the issue checkboxes.
  2. Once you’ve chosen the issues you’d like to edit, select Edit from the toolbar that appears.
  3. A sidebar will open which allows you to make edits for the shared fields across your selected issues.

New ways to edit card covers

ROLLING OUT NEW THIS WEEK

Now you can easily choose a color or an attachment, or upload a new card cover.

Select the action menu on the bottom right and choose "Edit cover"

Brand your Jira products with a custom domain

ROLLING OUT

You can now use custom domains to brand your Jira products. Custom domains provide easy-to-remember URLs for your users to access your products.

You can create a custom domain if you have a Jira Premium or Jira Service Management Standard plan.

Previously, this feature was only available for Jira Service Management help center. Tell me more about custom domains

To create 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 Add custom domain. This is only visible if you have an eligible product.
  4. Review the Before you add a custom domain page, and select Next.
  5. Select which product you want to access from your custom domain.
  6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
  7. Enter a Redirect URL. This is optional.
  8. Review changes and select Create domain.

Copy Jira Service Management data for team-managed projects and forms

ROLLING OUT

You can now copy Jira Service Management data between cloud sites from admin.atlassian.com, using the Copy product data feature. In addition, we've added the capability for team-managed projects to be copied.

Read more about what moves when copying product data. Keep an eye on this page to stay up to date on what data is available to copy between cloud sites.

Copying Jira Service Management data now lives in admin.atlassian.com, by selecting Settings, then Data management, then Copy product data.

You need to have organization admin permissions to access and use this feature.

Use Atlassian Intelligence (AI) to break down work

ROLLING OUT

You can now use Atlassian Intelligence (AI) to break down work into child issue suggestions.

Atlassian Intelligence will read the information in the parent issue and any connected Confluence site to suggest child issues for you.

To break down work using Atlassian Intelligence:

  1. Open an issue and select Add child issue.
  2. Select Suggest child issues.

The quality, accuracy, and reliability of information generated by Atlassian Intelligence may vary. Find out why

4 new fields for Jira list

ROLLING OUT

View even more issue information from your Jira list. View parent, team, development and version information as field columns. You'll also be able to filter by team, parent and versions.

To view your new fields, scroll the list all the way to the right. You can then organize your fields how you like.

To view your new filters, select Filter at the top right of your list. They will be available in the menu.

Keyboard navigation updates and new fields for Jira list

ROLLING OUT

Edit issues easier and quicker by navigating updates just with your keyboard. We've also added new fields including team, parent, development and versions.

To edit an issue using only a keyboard:

  1. To enter a value and move focus to the field on the right, press tab.
  2. To enter a value and move focus to the field below, press enter.

Your new fields will be shown in your list automatically. You can remove fields as you usually would.

Change the status of multiple issues from the backlog

ROLLING OUT

Transition up to 1000 issues through their workflow straight from the backlog. For example, you could move 10 issues from In progress to Done, or you could move 100 issues from To do to In progress.

We're still working on adding more complex scenarios to this experience. For now, you can only select issues that share a workflow. Also, you can only transition to statuses that don't require you to fill in a transition screen.

Try it out by selecting multiple issues from the backlog:

  • Use the issue checkboxes
  • Use Ctrl (Windows) or Command (Mac) while selecting issues
  • Use the Shift key to select a group of adjacent issues

Once you’ve chosen the issues you’d like to edit, select Edit, then Transition from the toolbar which appears on the backlog when you start selecting issues.

It’s easier for people with Jira to start using Jira Product Discovery

ROLLING OUT

We know our products can be complicated. So now people who have Jira, and have recently also added Jira Product Discovery, will see simple recommendations on how to start using Jira Product Discovery. For example, inviting teammates, using a template, etc.

That means it’s easier to know what to do first in Jira Product Discovery so that you’re getting the most out of it.

The recommendations will show up in the ‘Your work’ part of Jira, and everyone with either a Free, Standard, or Premium plan will see them. You can dismiss them anytime so they stop showing up.

Check out your Assets usage trends

ROLLING OUT

A few months ago, we introduced the ability to track the number of Assets objects in your instance in Jira Settings > Products > Feature usage. Well, now you can see how many objects you've had over time through the new usage graph. Helpful if you want to identify any spikes or dips in object creation at any given time.

Template recommendations in your Projects directory have a new home

ROLLING OUT

When you click on ‘Projects’ in your top navigation in Jira you land in your Projects directory. Previously, recommended templates were listed at the top of this directory.

Now, the templates we recommend sit to the side. You can display and hide them as before; the main difference is that when you hover over any of the templates, you can see a preview of what that template looks like and how it works.

We've also changed the logic behind the recommendations so that they’re more specific and useful.

Check out your usage trends for the virtual agent

ROLLING OUT

A few months ago we launched the feature usage screen for the virtual agent in Jira settings > Products > Feature usage. Now you can check your usage over the last 6 months using the chart feature - see when it spiked in the past to plan for it in the future!

Classify your sensitive work

Help people recognize when they’re viewing or working on sensitive information by classifying your pages, blogs, issues, and requests. Space admins and project admins can also set a default classification level for work created in their space or project. More about data classification

An organization admin has to set up classification levels for your organization before they’re available in Confluence, Jira, and Jira Service Management. Once they’re available, you can classify your work.

Shorter, saveable, downloadable, emailable reports for Assets

ROLLING OUT

We've got a whole bunch of improvements in store for Reports for Assets in this release... Reports are now distinct dashboards, can be saved for ease of access later, can be downloaded, and can even be emailed to you!

Inline create for custom CMP boards

ROLLING OUT

You can now create cards directly on boards with certain custom board filters.

This announcement marks our fourth iteration of inline card creation for boards in company-managed projects.

Jira incoming mail requires access renewal to Google every 6 months

ROLLING OUT

From June 3, 2024, access granted to incoming mail will automatically expire every 6 months. This means you need to re-authorize Jira to use a Google mail server every 6 months in Jira settings. For more read the community post.

  1. Open Jira and select the cog icon > System > Incoming Mail
  2. Find the mail server with Google OAuth Authentication Type
  3. Select Edit, and then Re-authorize

This is not a one-off re-authorization. You’ll need to authorize access every 6 months.

Summarize Smart Links with AI

ROLLING OUT

Save time by summarizing the content of a Smart Link with Atlassian Intelligence.

To summarize a Smart Link with AI:

  1. Navigate to the Jira description or comment.
  2. Hover over any Smart Link.
  3. Select Summarize with AI.
  4. Atlassian Intelligence will generate a summary.

Removing the import issues button from the Create issue screen

ROLLING OUT

We’re removing the Import issues button from the Create issue screen to help remove clutter. Don’t worry; you can still create issues in bulk using the CSV importer.

Create multiple help centers on your site to serve different audiences

ROLLING OUT

Create multiple help centers on your Jira Service Management site and customize each of them for your various teams or audiences. Each help center can feature distinct branding, topics, portals, and announcements to effectively cater to specific user groups.

You need to be a Jira admin to create and manage multiple help centers.

To create a new help center:

  1. Go to Settings > Products > Jira Service Management > Configuration.
  2. In the Help center section, select View all help centers.
  3. You’ll be taken to the help center management page. Select Create help center.
  4. Enter a name and URL slug for your new help center and select Create.

We've also moved around all help center settings to a single place. Select your avatar from any help center on your site and you can find your requests, profile settings and customization capabilities in the menu.

Jira

Prevent people from exporting content in specific spaces and projects

ROLLING OUT NEW THIS WEEK

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

To create a new data security policy or view existing policies:

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

Move data between sites with cloud-to-cloud migration

ROLLING OUT

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.

Add status while creating an issue

ROLLING OUT

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

ROLLING OUT

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

ROLLING OUT

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.

Advanced Roadmaps - New navigation

ROLLING OUT

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.

Control what you see in your products

ROLLING OUT

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.

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

COMING SOON

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.

Organize and track work against Compass software components

ROLLING OUT

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

ROLLING OUT

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

Use filters to search and display Jira issues

ROLLING OUT

Now you can use filters to search for Jira issues and display them in a list, 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 list

Start using filters to search for Jira issues:

  1. Edit a Jira description or comment.
  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 list format you can interact with.

To edit your list of Jira issues:

  1. Select anywhere on the list.
  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.

Move a mighty amount of issues from a completed sprint

ROLLING OUT

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.

Colourful categories

ROLLING OUT

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

Manage custom fields for your project in context of the list view

ROLLING OUT

You can now create and manage custom fields in context of the list view.

Certain types of work may require specific information for your team to get the job done. Jira now allows you to create and manage these additional fields in context of the list view to save you from navigating away from your work.

This will help your team with viewing the right, relevant information upfront when completing tasks.

To get started with the change, select the plus symbol at the top right of your list view to show or hide more fields, and manage your custom fields.

Track and triage incidents affecting your services in Jira

ROLLING OUT

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.

Hide unused fields when creating issues

ROLLING OUT

There can be a lot of fields to scroll through when you’re creating issues, and we know there are many fields that are simply unused.

We’re introducing a feature that only brings up the fields you actually use. We’ll create a personalized Create issue form for each issue type and project.

All the fields you don’t use will be hidden in a More fields section, so you'll always be able to interact with them. The feature is continuously learning. If we notice you using a previously unused field, we’ll pull it out of the More fields section for the next time.

We’ll automatically turn on the feature to hide unused fields when creating issues, but you can manage it by heading to Personal settings and finding to the Jira labs section. From there, you can use the toggle to opt in and out of the feature.

Template bundles in the project create page

ROLLING OUT

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

New ways to manage email notifications from Jira

ROLLING OUT

We've moved notification preferences out of your Personal settings page into its own Notifications space where we can continually develop ways for you to take control of your Jira notifications.

We've also replaced the old notification configurations with 10 notification preference options, so you have even more control of what notifications you actually want to receive.

To see the change:
Select your profile and settings icon, then select Notifications.

Use Atlassian Intelligence to define words in the issue description

ROLLING OUT

You can now use Atlassian Intelligence to define one or more words in the issue description. The definitions will be based on information found in connected Confluence spaces.

To use Atlassian Intelligence to define words:

  • Make sure the description is in view mode, not edit mode
  • Highlight words you need defined
  • Select Define

Definitions are only available in the description in view mode.

Maximum cardinality limit on multi-value attributes in Assets

ROLLING OUT

Assets in Jira Service Management is a database and so requires a combination of good data modeling and a great deal of processing power to handle large amounts of data. Here are recommendations for how to structure your data for Assets schemas.

See also: How to build an effective ITAM schema structure.

For this reason, we're introducing a maximum cardinality limit of 20,000 per object type attribute for Assets. Read more about recommended data structures for Assets.

Exceeding these limits can cause performance and reliability issues, therefore each site cannot create further items once they reach the limit. You can find out how many objects your site currently contains using the feature usage screen. Read more about how to track your usage.

Company-managed projects: Create, edit, and delete columns directly on the board

ROLLING OUT

If you want to quickly add or update a column on your board, you don’t need to go far. You can now create, rename, move, set constraints for, and delete columns without leaving the board. You’ll still have the ability to do all of the above in your board’s settings page, but if you’ve only got time for a quick fix, we’ve now got you covered!

If you’re a project or board admin for the board you want to update, you can try the following changes:

  • To create a column, select the + icon to the right of all columns.
  • To rename a column, select its name to edit directly.
  • To move a column, select its top, then drag the column to its new position.
  • To set column constraints, right-click its name or hover to select more actions (•••) > Set column limit.
  • To delete a column, right-click its name or hover to select more actions (•••) > Delete.

The team field in Jira issues now shows the team icon

ROLLING OUT

Previously, selecting the team field in an issue would prompt a search displaying the singular "Person" icon. The correct "Team" icon now shows to indicate what should be selected for the field.

Jira: Import from ClickUp

ROLLING OUT

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

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

To directly import your data using the ClickUp 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 ClickUp.

View project work in a single list

ROLLING OUT

View all your project's work in a single list that can be quickly scanned and sorted by field. Jira's list view can also be used to create, edit, and view issues in your project.

The list view is enabled by default in all projects. To view your project list, navigate to your project then select List from the sidebar in the Planning section.

Find out more about how to manage and update work in the list view.

View high-level work across multiple teams with a new template

ROLLING OUT

Use the new cross-team planning template to get a high-level view of work across multiple teams.

Reordering issues on the list view using assistive technology

ROLLING OUT

We’ve made our drag-and-drop functionality more accessible in the list view. Reordering issues on the list view is screen-reader- and keyboard-friendly for those using assistive technology.

Improved Jira import support

ROLLING OUT

We’ve expanded import support to Airtable, Azure DevOps, GitLab, GitHub, Linear, Notion, Smartsheet, YouTrack, and Wrike. Admins can download the CSV file from these apps, upload it to Jira, and import their data into a Jira business or software project with just a few clicks.

To import from these apps:

  • Select Projects > Create project.
  • From the sidebar, go to More > select Import data.
  • Select the app you’d like to import from and follow the directions.

Read about importing data into Jira

Jira issue email audit

ROLLING OUT

No need to raise a support ticket anymore when issue notification emails get suppressed. You have the power!

Navigate to Project settings, Notifications, Issue email audit and select Unblock email to get your team member's issue notifications sending again in around an hour.

You can search by name or email, or use the filter to display emails to unblock. The audit logs display up to 20 records, with the most recent undelivered issue notification shown first.

Heads-up when your team-managed board or backlog has over 5,000 issues

ROLLING OUT

Boards and backlogs in team-managed projects can now display 5,000 issues (the maximum issue limit). If you've gone over the issue limit, we'll give your admins a heads-up that it's time to move some issues. In the meantime, you can still view, edit, and interact with your board and backlog - even if you've reached the 5,000 max issue limit - so teams can continue to work as usual.

Improve the clarity of issue descriptions with AI

ROLLING OUT

Use Atlassian Intelligence to add clarity to your issue descriptions. Quickly improve your descriptions with clear structure and headings so they’re easier to read.

To get started, while you’re writing an issue description:

  1. Type / in the issue description field, or select the Atlassian Intelligence button.
  2. Type or select Add structure.

Using AI, we’ll generate a new, structured issue description for you to review. Look over the new description, and choose to replace your existing description or add the new one underneath.

Company-managed projects: Site admins can view private boards

ROLLING OUT

If you’re a site admin of a company-managed project, you’ll notice that private boards are now visible in the boards directory and the board picker in your project navigation. If a board is private, its details won’t be shown, but you’ll be able to view and edit the board’s filter.

Jira Service Management

Jira Service Desk is now Jira Service Management! We’re in the process of rolling out some exciting new features for all users. Learn more about these new features.

Translate your forms into multiple languages

ROLLING OUT NEW THIS WEEK

Need to surface forms to customers in multiple languages? Now you can add translations to forms in Jira Service Management so customers are able to raise requests in their preferred language.

Simply navigate to the form builder and select the Translate tab to try it out. Add languages, add translations to fields and rich formatting elements, and make it available for customers to access when you’re ready. 


Read more about adding translations to forms

Add status while creating an issue

ROLLING OUT

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

ROLLING OUT

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

ROLLING OUT

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

ROLLING OUT

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.

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

ROLLING OUT

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

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

COMING SOON

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.

Use filters to search and display Jira issues

ROLLING OUT

Now you can use filters to search for Jira issues and display them in a list, 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 list

Start using filters to search for Jira issues:

  1. Edit a Jira description or comment.
  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 list format you can interact with.

To edit your list of Jira issues:

  1. Select anywhere on the list.
  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.

Streamline customer organization management with email domains

We're excited to introduce the Email Domain feature in Jira Service Management, a powerful enhancement designed to automate and streamline the process of managing customer organizations.

With this new feature, site admins and agents permitted by Jira Service Management’s product settings can now add up to 10 email domains to a customer organization, ensuring that customers with matching email domains are automatically added to the corresponding organization. This feature is aimed at simplifying the management of customer organizations, reducing manual effort, and improving the overall efficiency of your Jira Service Management setup. How to use email domains to automatically group customers into organizations

Hide unused fields when creating issues

ROLLING OUT

There can be a lot of fields to scroll through when you’re creating issues, and we know there are many fields that are simply unused.

We’re introducing a feature that only brings up the fields you actually use. We’ll create a personalized Create issue form for each issue type and project.

All the fields you don’t use will be hidden in a More fields section, so you'll always be able to interact with them. The feature is continuously learning. If we notice you using a previously unused field, we’ll pull it out of the More fields section for the next time.

We’ll automatically turn on the feature to hide unused fields when creating issues, but you can manage it by heading to Personal settings and finding to the Jira labs section. From there, you can use the toggle to opt in and out of the feature.

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

ROLLING OUT

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.

New ways to manage email notifications from Jira

ROLLING OUT

We've moved notification preferences out of your Personal settings page into its own Notifications space where we can continually develop ways for you to take control of your Jira notifications.

We've also replaced the old notification configurations with 10 notification preference options, so you have even more control of what notifications you actually want to receive.

To see the change:
Select your profile and settings icon, then select Notifications.

Use Atlassian Intelligence to define words in the issue description

ROLLING OUT

You can now use Atlassian Intelligence to define one or more words in the issue description. The definitions will be based on information found in connected Confluence spaces.

To use Atlassian Intelligence to define words:

  • Make sure the description is in view mode, not edit mode
  • Highlight words you need defined
  • Select Define

Definitions are only available in the description in view mode.

Control who has access to raise requests in Jira Service Management

ROLLING OUT

Need to control who can and can't raise certain requests in Jira Service Management? Now you have the ability to restrict request types - one of your top requested features!

There may be times when only specific people or groups should be able to raise certain requests. These could be requests reserved for managers, different departments in your company, or even those managing sensitive information such as HR or Legal teams.

Now from any company-managed service project, you can restrict individual request types by giving access to specific people and groups, which then automatically restricts access to all others.

Read more about restricting request types

Maximum cardinality limit on multi-value attributes in Assets

ROLLING OUT

Assets in Jira Service Management is a database and so requires a combination of good data modeling and a great deal of processing power to handle large amounts of data. Here are recommendations for how to structure your data for Assets schemas.

See also: How to build an effective ITAM schema structure.

For this reason, we're introducing a maximum cardinality limit of 20,000 per object type attribute for Assets. Read more about recommended data structures for Assets.

Exceeding these limits can cause performance and reliability issues, therefore each site cannot create further items once they reach the limit. You can find out how many objects your site currently contains using the feature usage screen. Read more about how to track your usage.

Data limits for object schemas in Assets

ROLLING OUT

Assets in Jira Service Management is a database and so requires a combination of good data modeling and a great deal of processing power to handle large amounts of data. Here are recommendations for how to structure your data for Assets schemas.

See also: How to build an effective ITAM schema structure.

For this reason, we have introduced limitations on how many objects, attributes, and attribute characters can be stored inside schemas within each individual Assets in Jira Service Management site. Read more about how much data you can store in Assets.

Exceeding these limits can cause performance and reliability issues, therefore each site cannot create further items once they reach the limit. You can find out how many objects your site currently contains using the feature usage screen. Read more about how to track your usage.

The team field in Jira issues now shows the team icon

ROLLING OUT

Previously, selecting the team field in an issue would prompt a search displaying the singular "Person" icon. The correct "Team" icon now shows to indicate what should be selected for the field.

Jira: Import from ClickUp

ROLLING OUT

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

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

To directly import your data using the ClickUp 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 ClickUp.

Use canned responses for agent signature

ROLLING OUT

You can now use canned responses to specify your personal signature, which is added automatically when an agent comments on an issue using the issue view. Your signature can include your name, designation, contact information, etc.

To add your personal signature:

  1. Go to the issue view for any issue.
  2. Select Add internal note or Reply to customer.
  3. Select Canned responses.
  4. Select an existing personal canned response or Create new to create a new one.
  5. Enter the following details:
    • Name - Give a unique name to your response.
    • Availability - Agents can only create personal canned responses and would not see this option when creating a new canned response. If you're a project admin, select Personal.
    • Response - Use this field to specify your signature.
  6. Select the Use as Signature checkbox.
  7. Select Save or Create to save your signature.

Blank request type creation: updated details screen

ROLLING OUT

We've introduced a new screen for editing details when creating a new blank request type in Jira Service Management.

Previously if you selected Create request type, then Create blank, you saw a modal and followed a two-step process to update the request type's name, description, icon, issue type, and portal group(s).

We've replaced this with a screen that allows you to easily review and update the same information in a single view, alongside a preview of the request form.

To see what's changed:

  • From your service project, go to Project settings, then Request types.
  • Select Create request type, then Create blank.
  • On the left of the screen, you'll have the option to edit the name, description and icon for the new request type. You'll also be able to select an issue type, and select (or create) the portal group(s) where you want the request form to appear.
  • On the right of the screen, you'll see a preview of the form for the new request type. The blank request type will only contain a single Summary field as a placeholder so you can later customize the request form to meet your requirements.

If you choose to create a new request type by selecting Create request type, then Create from template, you'll use this same screen to review and update the request type's details.

Update the request types of issues using Atlassian Intelligence

ROLLING OUT

We've released a new feature powered by Atlassian Intelligence that updates the request types for multiple issues at once. This is particularly useful when you receive requests by email and end up with a lot of issues with the Emailed request request type. By using the Atlassian Intelligence triage feature, you can easily update these issues to have more appropriate request types.

To update the request types of issues with Atlassian Intelligence:

  1. Select issues in your queue.
  2. Select Triage.
  3. Review the suggestions and select the issues you want to update.
  4. Select Apply.

Show entitlement details on issues

ROLLING OUT

We've added a new feature to Products and entitlements in Jira Service Management. Now you can choose to show entitlement detail fields on issues. This gives agents additional context about customers and their entitlements while working on support cases.

Find out how to show entitlement detail fields on issues.

Receive support requests from multiple email addresses in a single project

ROLLING OUT

You can now add up to 10 email addresses to receive requests from your customers in a single project. You can either create new Atlassian email addresses or connect any of your team’s existing email addresses.

Admins can connect multiple email addresses to a project only for company-managed projects.

To setup your email channel with multiple email addresses:

  1. From your project settings, select Email requests.
  2. Select Create Atlassian email or Add external email and follow the prompts to complete the setup.

Assign colors to cards on your board based on request types

ROLLING OUT

You can now assign colors to cards on your board based on request types.

  1. From your board select More actions (•••), then Configure board.
  2. Select Card colors in the settings menu.
  3. From the Select method dropdown list, select Request types.

Manage approvers from the issue view's collapsible panel group

ROLLING OUT

For issues with at least one approval step, we've replaced the approver configuration 'glance panel' on the issue view with a 'collapsible panel group' experience.

The process for adding or removing approvers on issues with an approval step remains identical; however, the access point and interaction have slightly changed.

This improvement has been made in response to feedback we've received from our customers and partners and will make it easier to update approvers within the context of the issue view's right-hand panel.

To see the change:

  • Select an issue with at least one approval step.
  • From the right-hand column in the issue view, select the chevron to expand the Approvals panel group.
  • From here you can manage approvers for the issue.
  • Use the chevron to close the group when you're done.

JQL query support for boards in Jira Service Management

ROLLING OUT

You can now create swimlanes on your board in Jira Service Management projects using Jira Query Language (JQL).

To add swimlanes using JQL:

  1. From your board select More actions (•••), then Configure board.
  2. Select Swimlanes in the settings menu.
  3. From the Select method dropdown list, select Queries.

New request type templates

ROLLING OUT

We've added new request type templates to our template library in the following categories:

  • Analytics
  • Customer service
  • Design
  • Facilities
  • Finance
  • HR
  • Legal
  • Marketing
  • Sales

Attach a form directly from the request type configuration page

ROLLING OUT

We’ve made it even easier for admins to attach new forms to request types without needing to navigate to form settings.

After selecting Attach form when in request type, you can now choose to either create a new form from the form template library, or search and select an existing form.

Select Create from template to browse over 200 form templates with pre-built conditional sections and rich formatting to help get you started sooner. Or Select existing to search all forms across your entire project.

Read more about adding forms to request types

Jira Product Discovery

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

ROLLING OUT

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

ROLLING OUT

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.

We've introduce time markers for your timeline.

ROLLING OUT

You can now mark a specific date in your timeline.

In your discovery project, go to a timeline and click anywhere in the time header. The blue dot that appears marks a specific milestone. You can add a name, date, and even a color.

You can drag and drop a time mark, change the date, and create multiple markers.

Remember that these markers only apply to the timeline where you create them.

Update to system fields

ROLLING OUT

Project admins can now hide system fields that aren’t in use in their Jira Product Discovery projects.

To hide system fields:

  1. Go to Project settings > Fields.
  2. Pick a system field of your choice and click the cog icon.
  3. Click the eye icon to hide.

New integration with Atlas

ROLLING OUT

With the new integration with Atlas, you can track Atlas goals and projects alongside every aspect of the discovery phase.

  • You need to have an active Jira Product Discovery license.
  • You can only connect to Atlas sites within the same organization as the current JPD site.
  • You need to have at least one project in Jira Product Discovery.
  • As explained below, you have to connect to Atlas via Jira Product Discovery.
  • If you don’t have product access to Atlas on a site, you won’t see the site name in the integration dropdown.

Confluence

Mission control customized overview

ROLLING OUT NEW THIS WEEK

We’ve added customization to Mission control for Premium and Enterprise plans. Admins can now select which metrics to display at the top of the page in the overview section of the feature. This update helps admins tailor the insights they see to best suit their needs.

Key change: A customizable top overview section.

To get started with this change:

  1. Select the wheel icon in the top navigation on a Confluence Cloud site.
  2. Select the Edit link in the Overview section in the top of the mission control feature.

Admin settings for Confluence in Jira

ROLLING OUT NEW THIS WEEK

Admins can now control the ability to create Confluence content in Jira.

We're adding settings to turn on and turn off options to create pages and whiteboards for sprint retrospectives, from the drop-down menu in issues, and from an issue's Confluence content section.

To use these settings, admins can select the wheel icon and find the Confluence page under the left menubar's Integrations section.

Settings refresh: Look and feel & Data management

ROLLING OUT NEW THIS WEEK

We updated some site settings pages with a modern look and streamlined experience!

Key changes:

You’ll notice a more intuitive experience. We updated layouts, added pagination, enhanced tooltip messages, and more.

To find the updated pages, Confluence admins can navigate to Settings (wheel icon) and then view the left sidebar, or navigate to their new URLs:

  • Application navigator: admin/application-navigator
  • Default space logo: admin/default-space-logo
  • Macro usage: admin/macro-usage
  • PDF export: admin/pdf-export

Prevent people from exporting content in specific spaces and projects

ROLLING OUT NEW THIS WEEK

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

To create a new data security policy or view existing policies:

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

Expanded classification support for more items

ROLLING OUT NEW THIS WEEK

You can now add classification levels to whiteboards and databases. Data classification is only available in Atlassian Guard Premium.

To get started:

  1. Select Add classification in the top navigation.
  2. Choose a classification level.
  3. Select Update.

Share whiteboards with anyone

ROLLING OUT NEW THIS WEEK

Let anyone with a whiteboard’s public link (even external people) view what’s happening on a whiteboard in real-time. This can be useful for sharing roadmaps, brainstorms, holding workshops, and more.

Anonymous visitors are represented in the top toolbar and as a cursor moving across the whiteboard while they’re viewing it. They can see collaborators working on the board and other anonymous visitors.

Anonymous visitors and their cursors are also visible to collaborators who are working on the internal version of the whiteboard. Collaborators can control what their name appears as to anonymous visitors.

To turn on and copy a whiteboard’s public link:

  1. Go to a whiteboard.
  2. Select Share.
  3. Turn the Public link toggle on. This will auto-copy the public link.
  4. Or if the toggle is already on, simply select Copy public link and share it.

To view what public whiteboard visitors see, you can copy the public link and paste it into your browser.

Be more expressive with panels

ROLLING OUT

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

ROLLING OUT

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

Transfer of page ownership between users

ROLLING OUT

When a page is created, the person who creates is now known as the owner of that page. We've made it possible for page owners to transfer ownership of their page to another person at any time. Space and site admins can also transfer page ownership from one user to another.

This way, if a current page owner leaves a project, team, or company, ownership of the page can then be granted to whomever is most appropriate, and maintenance and validity of the page remains fresh.

A page owner is the ‘point person’ for a given page and their name appears in the byline, under the page title.

Learn more about page ownership and how it can be transferred

Control what you see in your products

ROLLING OUT

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

ROLLING OUT

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.

Home has a new look

ROLLING OUT

Jump into work with Confluence Home, now with an improved look and feel. This visual refresh includes layout and iconography updates.

Visit Home to see these changes.

See comments appear, resolve, and reopen in real time

ROLLING OUT

When a new comment is created, a highlight will now appear on the page in real time. Similarly, comment replies - along with resolved or reopened comments - will also appear instantly in real time.

Restore and reattach inline comments, even after deleting highlighted text

ROLLING OUT

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.

Configure and display labeled content with clarity and ease

ROLLING OUT

You can now find and customize the Filter by label macro (formerly known as "Content by Label") more easily than ever, thanks to the following changes:

  • New and improved name and icon for instant discovery.
  • A simpler filtering experience with a more clearly organized dropdown menu.
  • An overall clearer and better organized set of options in the configuration modal, for faster and easier customization.

Collaborate and turn ideas into action with Confluence whiteboards

ROLLING OUT

Confluence whiteboards will be generally available to everyone over the coming weeks. Use whiteboards to collaborate and turn ideas into action, faster than ever before.

Whiteboards are great for collaborative activities, such as brainstorming ideas, running retrospectives, planning out and breaking down work for your team, prioritizing what’s coming next, creating diagrams and flowcharts, and more.

Take advantage of integrations with products like Jira. You’ll be able to turn sticky notes into Jira issues and create relationships between issues.

Compare plans and explore what’s possible with whiteboards.

Manage space access in bulk

ROLLING OUT

Admins can now save a bunch of time and repetitive tasks by adding a single user or group to all spaces on a site (or remove them from all spaces) in one bulk action.

This can be done for literally all spaces on the site, for all spaces except personal spaces, or exclusively for all personal spaces.

Catch up quickly with page comments summary

ROLLING OUT

Now, Atlassian Intelligence can summarize page comments for you, making it easier and faster to catch up on important feedback. Just navigate to the bottom of the page, above the first page comment, and select Summarize comments.

New comments since you last checked? Select the refresh icon to generate a summary that includes all the latest feedback.

Admins can now create automation rules for public links

ROLLING OUT

We're adding the ability to create automation rules directly from the public links setting on a page.

When an admin on a Confluence space with automation turns a page's public link on or off, they will see a prompt to create a new automation rule to manage public links.

Automatically build automation rules for public links

ROLLING OUT

Admins can now create automation rules to manage public links on their Confluence site.

When you use the public links settings, we'll show you a prompt to automatically build a rule for public links in new spaces.

Automatically build automation rules to assign guest users to a space

ROLLING OUT

Admins can now create automation rules to manage space assignments for guest users.

We'll show you a prompt to automatically build a rule to assign spaces to new guest users when you assign spaces in three ways:

  • Using the dropdown menu next to the guest user's name
  • Using the bulk assign screen
  • Setting a default space for guest users in Global Permissions

Confluence Page Verification

ROLLING OUT

Pages owners and admins can now add a new Verified status to pages. This supports page verification functions in Confluence automation.

Improved collaboration with image and video comments

ROLLING OUT

You can now add comments to images and videos in Confluence Cloud, making collaboration and adding context a breeze. ️

This update lets you add comments directly to images and videos on your pages. When viewing a page, hover over or focus on an image, and a new comment button will appear. While editing, select the image and use the new comment button in the toolbar.

Like text comments, you can easily add your thoughts and discussions. When a comment is added, a handy icon will appear in the corner of the image, letting you know there's a discussion brewing.

Just a heads up: Inline images can't be commented on yet, and each image or video can only have one comment thread.

Comment on whiteboards for further collaboration

ROLLING OUT

The commenting experience will now be available in whiteboards, alongside pages. Leave comments, @mention teammates, reply to conversations, and more with comments in Confluence whiteboards. You can see mentions and replies directly in your notifications.

Switch to comment mode in a whiteboard by selecting the comment icon in the toolbar on the right or use M on your keyboard. Once you're in comment mode, click anywhere on the whiteboard to create a comment.

Introducing Spaces report: Empower your space management

ROLLING OUT

Unlock comprehensive space management with our new Spaces report feature. Export detailed CSV reports on space activity, creation, and more directly from Confluence. This feature is ideal for admins seeking insights into space usage, activity, and storage.

Key changes:

  • Exportable CSV reports for product admins, detailing each space's key metrics.
  • Reports include space key, name, type, status, creation date, last activity, and storage used.
  • New Spaces report page under Data management for easy access and report management.
  • Supports organization, site, and product admins across Standard, Premium, and Enterprise plans.

This feature also provides essential space management data previously unavailable in Confluence. It aids in identifying inactive spaces, managing storage, and enhancing external collaboration, significantly improving admin efficiency and decision-making.

Classify your sensitive work

Help people recognize when they’re viewing or working on sensitive information by classifying your pages, blogs, issues, and requests. Space admins and project admins can also set a default classification level for work created in their space or project. More about data classification

An organization admin has to set up classification levels for your organization before they’re available in Confluence, Jira, and Jira Service Management. Once they’re available, you can classify your work.

Recommendation emails

ROLLING OUT

What's new or different?

Introducing recommendation emails—a weekly list of recommended and popular content, relevant to the spaces that each Confluence user has access to.

Customize a dynamic info hub for your entire company with Company Hub

ROLLING OUT

Company Hub allows you to customize a beautiful and dynamic company-wide information central within Confluence, where employees can go for up-to-date announcements, news, key resources, and more.

Product admins can add a custom name and color scheme along with images, visual cards, links, and more to instantly craft a hub that looks and feels like your company's go-to destination.

This feature is currently in beta and rolling out gradually to our Premium and Enterprise customers.

Streamlined space import process

ROLLING OUT

We've revamped the space import process in Confluence, making it easier and more intuitive. Now, track your import progress directly on the same page with fewer clicks.

Key changes:

  • The import progress is now displayed on the same page immediately after initiating the import, for both failure and success cases,
  • The user interface has a more modern look.
  • The new path is: /wiki/admin/space-import

To access the updated Import spaces settings, Confluence admins can navigate to Settings (wheel icon) > Data management > Import spaces.

Table alignment options

ROLLING OUT

With this update, you can now align tables on your page to the left or center, giving you greater control over the layout and presentation of your content.

What’s New:

You can easily align your tables to the left or center of the page. A new button has been added to the table toolbar, allowing you to quickly select your preferred alignment. When you insert a table in full-width pages - these are now left aligned by default.

How to use:

  1. Insert or select a table on your page.
  2. Select the new alignment options button in the table toolbar.
  3. Select your desired alignment: left or center.

This update provides a simple way to enhance the visual structure of your documents, making them more consistent, engaging, and easier to read.

Smart card confluence page automation action

ROLLING OUT

We're adding an action to Automation for Confluence that lets you automate the creation of Smart Links in the content tree.

Search directly from the content tree

ROLLING OUT

Now you can filter items in the content tree by title, making it faster and easier to find what you're looking for.

Just select the magnifying glass below the Content header and start entering a keyword from the item's title.

We're replacing previews with summaries in hover cards

ROLLING OUT

Now, when you hover over a page title in the content tree, you'll see an AI-generated page summary instead of a preview, giving you richer, more detailed information about what you can expect to find on the page.

This change only applies to Premium and Enterprise customers with Atlassian Intelligence enabled. Everyone else will continue to see a page preview on hover.

Quick react from Confluence content creation notification emails

ROLLING OUT

We've added emojis directly to content creation notification emails about pages and blog posts, allowing you to easily engage collaborators with a quick reaction. With a simpler reactions experience contextually available, users can reduce tool-switching by reacting directly from the email.

Fixed column widths for tables

ROLLING OUT

We’re pleased to introduce a new feature that enhances your control over your tables. You can now set column widths to fixed, ensuring that your table layout remains consistent even on narrow screens. This option is available in Table options in the table toolbar and is unchecked by default, allowing tables to scale as they always have. For those who prefer their tables to respond dynamically to screen sizes, we’ve increased the maximum scaling to give your tables even more flexibility.

How to use:

  1. Insert or select a table on your page.
  2. Select the Table options icon in the table toolbar.
  3. Select the Fixed column widths option to prevent your table columns from scaling down on narrow screens.

This update allows you to maintain the integrity of your table layouts across different screen sizes, providing a more consistent viewing experience.

Bitbucket

Introducing iterative review

NEW THIS WEEK

We are excited to announce the introduction of Iterative review, a feature designed to help your team get pull requests completed faster by removing the need to re-review code you’ve already seen. Now when an author pushes new commits based on your pull request (PR) feedback, you’ll have the option to focus on just those new changes. We will be rolling this out to you intermittently beginning on June 18 with 100% of users having this feature on June 24. You can read more about what iterative review can do for you in our latest community post.

Cache key support for self-hosted runners

ROLLING OUT

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.

Compass

Upgrade your Compass GitHub app to allow Compass to ingest pull request data

ROLLING OUT

Accept the updated permissions for your Compass GitHub app to authorize Compass to enrich the PR data/insights we show you in Compass.

Upgrade your Compass GitHub app:

  1. In GitHub, go to the organization settings for the organization that you've connected the Compass app to.
  2. Select GitHub apps on the left sidebar.
  3. Select the Review request link.
  4. Enter your GitHub password.
  5. Select Accept new permissions.

You're now on the latest version of the Compass GitHub app.

Powered by Confluence and Scroll Viewport.