• Atlassian Administration
• Jira platform
• Jira
• Jira Service Management
• Jira Product Discovery
• Confluence
• Bitbucket
• Compass

Prevent people from exporting Jira issues

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.

Filter the user list with added roles

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

The roles we’re introducing include:

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

To filter the user list by roles:

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

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

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

Option 1: Manually set up user provisioning

Recommended when you need:

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

Learn how to add an identity provider for this option

Option 2: Automatically set up user provisioning

Recommended when you need:

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

Learn more about Azure AD for nested groups

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

Learn more about identity providers

Control whether members use API tokens to authenticate

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

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

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

To try out the API token setting:

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

Find Atlassian Administration settings faster

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

To use the Administration search field:

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

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

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

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

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

Create custom domains for your Jira products

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

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

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

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

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

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

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

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

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

Changes for Atlassian Intelligence across products in Premium and Enterprise plans

Starting May 6, Atlassian Intelligence is now automatically activated in all Premium and Enterprise plans of our Cloud products at no additional cost.

Tthis change now applies to existing cloud subscriptions unless an organization admin has previously opted out as per the email notices sent between March 20 and April 2. Note that the activation process will roll out for Trello and Bitbucket starting in June.

With Atlassian Intelligence, your teams can now accelerate their work, unlock knowledge, and make better decisions faster.

We know that data security and privacy remain a top concern. Atlassian is dedicated to building its solutions in alignment with our responsible technology principles, and will continue to follow our existing data security and privacy practices.

Organization admins can deactivate Atlassian Intelligence at any time and manage Atlassian Intelligence preferences from Atlassian Administration (Settings, then Atlassian Intelligence).

We’re replacing Beacon with Guard Detect

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

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.

Collapsible transition labels in the New Workflow Editor

This is the second small but mighty improvement to the workflow editor so your workflows are easier to read.

This change adds collapsible transition labels to the new workflow editor for both company-managed and team-managed projects. When you're managing workflows in the new editor, you can hide transition elements to reduce the amount of clutter on your screen. Oh, happy days!

Other small but mighty changes to the workflow editor include:

• New global transitions and lozenges in the New Workflow Editor
• New shared transitions in the New Workflow Editor for company-managed projects

Read our community post about these changes to learn more.

New shared transitions in the New Workflow Editor for company-managed projects

This is the third small but mighty improvement to the workflow editor so your workflows are easier to read.

Based on customer feedback, this change updates how Shared transitions render in the new workflow editor for company-managed projects. The lines for shared transitions are more compact, which should help reduce clutter on busy workflow diagrams.

For right now, this change only applies to company-managed projects; support for team-managed projects will come later.

Other small but mighty changes to the workflow editor include:

• New global transitions and lozenges in the new workflow editor
• Collapsible transition labels in the new workflow editor

Read our community post about these changes to learn more.

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

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.

Introducing limits to how many items you can add to an issue

To enhance the reliability and efficiency of our platform, we’re introducing new limits to how many comments, attachments, and links you can add to an issue.

Use Atlassian Intelligence (AI) to break down work

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

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

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.

New global transitions and lozenges in the new workflow editor

This is the first small but mighty improvement to the workflow editor so your workflows are easier to read.

This change specifically targets workflows made using the old editor view. Through customers' feedback, we've heard that when these workflows are opened in the new editor view, they're often hard to read, misaligned, and generally not nice.

To solve this, we’ve updated how the global transitions and the status lozenges render in the new editor view. See the image for a before/after comparison.

Other small but mighty changes to the workflow editor include:

• Collapsable transition labels in the New Workflow Editor
• New shared transitions in the New Workflow Editor for company-managed projects

Read our community post about these changes to learn more.

Bringing Plans and Overviews together!

We’re bringing together the best of Jira Software and Jira Work Management into a single project management tool, so all your teams now have a shared place to get sh*t done.

As of this release note, we're launching the migration of Overviews in Jira Work Management into Plans in Jira Software.

Find out how this supercharges your planning experience

Simplifying the Toolchain settings page

The "Toolchain" page within "Project Settings" has undergone a transformation! It's now a focused discovery page with a centralized hub for admins to effortlessly discover and install first-party (1P) and third-party (3P) integrations.

This change means the page will no longer serve its previous function of managing connected tools and opsgenie teams. We've also removed the Edit connections button from the "Code" page that previously linked to the "Toolchain" page.

If you need to manage security containers, head to the “Security” page in Jira. From there, you can utilize the connection manager sidebar.

Finally, we've introduced a new Swap container button on the "On-call" page. This button replaces the Change connected Opsgenie team button.

Improved search using summary and description fields

We’re boosting performance in the issue navigator by changing how the search field works behind the scenes. When searching by text, results will be based on the Summary and Description fields.

Before this change, results were based on multiple text fields such as Summary, Description, Comments, and any custom text fields, which caused results to be slower to load.

If you’d prefer to search using text fields, select More + to view additional field filters, then select Text.

To try it out, head to the issue navigator by going to your project, then select Issues in the sidebar.

Copy and share a link to your Jira dashboard

We're adding a "Copy link" button to let you share your Jira dashboards in other Atlassian products, such as on a Confluence page, whiteboard, or database. These links can be displayed as a card in Confluence to make it easier to share your Jira data with others.

Move data between sites with cloud-to-cloud migration

We're introducing cloud-to-cloud migration to make it easier for you to move users and projects from one cloud site to another. Cloud-to-cloud migration can help you combine data between two or more cloud sites, split a cloud site into multiple cloud sites, duplicate a cloud site, or move specific projects from one cloud site to another.

Org and site admins can access this feature by logging in to the cloud site you want to move your users and projects from, then going to Settings > System > Migrate cloud site.

Add status while creating an issue

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

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

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Advanced Roadmaps - New navigation

Advanced Roadmaps has a new look that makes it look and feel more like the rest of Jira Software.

To state it simply, the nav now lives on the left-hand side. This new layout opens Advanced Roadmaps up to a whole new world of designs and new features (whoops, not sure if I was supposed to say that 🤭).

Even though this is rollout to all users, we'd still love to hear your thoughts about how it effects your work, or your ideas for improvements. Use the Give feedback button which is still located in the upper right of your screen.

If you opted in the Early Access Program from last month, you won't notice a change. However, this layout is now the new default view for Advanced Roadmaps and can no longer be disabled.

Read more about these changes in our community post.

Control what you see in your products

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

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

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

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

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

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

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

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

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

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

To connect pending Bitbucket workspaces on the Code page:

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

To connect pending Bitbucket workspaces using the development dialog:

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

Read more about integrating Bitbucket with Jira

Use filters to search and display Jira issues

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.

Colourful categories

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

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

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

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

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

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

To get started with the incidents feature:

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

To turn it on manually:

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

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

Finish setting up your development tools from the issue view

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

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

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

To get started:

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

Hide unused fields when creating issues

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

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

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

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.

See how your issues relate to each other in the timeline

We’ve made it easier to see the relationship between parent and child issues in the timeline.

These changes are being rolled out, so don’t worry if you can’t see them yet - they’ll be there soon!

In the timeline, all child issues will now appear under their parent issues so you can better visualise how your work relates to one another. This feature was previously only available with subtasks and their parent issues.

As well as this, you can now create child issues for any issue type (except subtasks) in the timeline.

To create a child issue from the timeline view:

1. Select Create child issue ( + ) in the row of the issue you’d like to create a child issue for.
2. Enter a summary of what needs to be done for this child issue.
3. Select enter on your keyboard to create the task, or escape to cancel.

As an added bonus, we’re increasing the number of child issues you can see in the list view to 500 so you can see even more of your work at once.

Maximum cardinality limit on multi-value attributes in Assets

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.

Customize your navigation

Project admins can control what the team sees in the project view navigation. Display what's most important to your team, and hide what's not. Any changes that are made to the navigation will be visible for everyone who has access to the project.

Project admins can customize the following in their business project:

• Set the default view for the project
• Hide a tab from the project view navigation
• Add a tab back to the navigation if it has been removed
• Reorder the tabs

Find out more about customizing the navigation in your business project

Unblock user invitations

Good people of Jira. No more support tickets will be required to deal with blocked invitation emails!

Organization admins can now unblock user invitations that aren't accepted due to email suppression.

Use our new Unblock user invites feature alongside the User directory to monitor and troubleshoot sent invitations that haven’t been accepted.

Organization admins can use Unblock user invites to request an unblock, and then resend user invitations by following the on-screen prompts.

Resent invitation emails will generally arrive within one hour.

In Jira navigation, select Settings > System settings > Unblock user invites.

A list of undelivered invitations will display. In the case of emails that Atlassian blocks due to too many failed attempts to deliver, you'll see an option to Unblock user invite. After a short delay while the request is completed and the email is unblocked, you’ll be presented with an option to resend the user invitation again, displayed as Resend user invite.

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

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.

Find your attachments even faster

We’re introducing new filters so it’s even easier to find the attachment you’re looking for.

We’re slowly rolling out this feature, so don’t worry if you can’t see this yet.

If this is already available for you, you can now use brand new filters in Attachments to find a specific attachment.

You can filter attachments by:

• who added them
• the type of attachment (image, document, spreadsheet, and more)
• the date it was added to an issue

More about using filters to find attachments

Customize your projects with a photo background

Project admins can capture the theme of each project with a different gradient, color, or custom photo. Customizing the project background is a simple way to give your business projects a unique identity.

To change the background, go to a business project and select the paint bucket icon next to the project name. More about changing business project backgrounds

The team field in Jira issues now shows the team icon

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.

Drag and drop to reparent issues

We’ve made it easier to reparent issues in the timeline and list views.

We’re slowly rolling out this feature, so don’t worry if you can’t see this yet.

In the timeline and list views, you can now reparent a single issue by simply dragging and dropping it underneath a new parent issue.

Jira: Import from ClickUp

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

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

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

View your work suggestions in Jira

Jira work suggestions are now available on scrum and kanban boards.

Work suggestions are task recommendations that are automatically curated for you from across multiple connected tools. These contextual, timely, and actionable suggestions help you decide which task to pick up next. This removes bottlenecks and helps you keep momentum in your and your team’s day-to-day work.

Jira work suggestions are enabled for everyone by default. You can view your work suggestions by selecting your avatar on a Jira board. The work suggestion panel appears only when customized suggestions are available for you. You can choose to hide or show the work suggestions panel from the View settings menu on your Jira board.

Read more about Jira work suggestions

To view your work suggestions:

1. Go to your Jira board and select your avatar. The Work suggestions panel opens only when customized work suggestions are available.
2. Select the suggestion to view more information about the task and take action.
3. If you don’t want to see work suggestions on your board, select View settings and disable the Work suggestions toggle. You can enable it again at any time.

Heads up when you hit 5,000 issues on your board + backlog

View, edit, and interact with your board and backlog — even if you've reached the 5,000 max issue limit.

This means your board admins get a heads-up to adjust the board filter, and teams can continue to work as usual.

To adjust the board filter, navigate to More ... > Configure board.

Scroll to the Board filter and adjust what's included and excluded using Jira Query Language (JQL).

Jira plans, warning filter update

Your planning tool warnings centre is now updated with a condensed list of settings you can switch on. We're also moving the “Filter issues with warnings” toggle from inside the Warnings dropdown menu to the Filters dropdown menu, so you can see all the details there.

Moving data from Asana to Jira just got easier

The Asana importer directly moves project data from your Asana account into a software project, saving you the effort of manually moving data while keeping it accurate. With a few clicks, admins can easily set up a software project, map Asana project fields, and import project data into the new software project.

To directly import your data using the Asana 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 software project.
4. In the import from an app section, select Asana.

Read more about the Asana importer

Minor UI updates to AI issue triage

We've made some minor updates to the AI issue triage feature. Issues that can't be updated are now grouped together to allow for easier scanning and comprehension at a glance.

Add status while creating an issue

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

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

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

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

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

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

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

Reports now available for Assets

Get a a comprehensive overview of your Assets performance, simplify your analysis process and gather valuable insights at a glance with the new reports dashboard for Assets in Jira Service Management.

Things to note:

• This functionality will disabled for customers who have signed HIPAA and have tagged Jira Service Management. We are working to enable it but this will take a few more days.

• Customers who have moved their Jira Service Management instance to the Switzerland Data Residency region will not have any data available in reports.

To get started with the reports for Assets dashboard:

• Go to Assets
• Select Reports (to the left of Configuration)

Use filters to search and display Jira issues

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.

Hide unused fields when creating issues

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

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

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

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

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

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.

Beta: Group alerts using Atlassian Intelligence

This Atlassian Intelligence feature is in beta. Read more about Atlassian Intelligence features.

Atlassian Intelligence groups related alerts and offers insightful suggestions, helping your team manage alerts and resolve issues more effectively. Alert grouping lessens 'alert fatigue' for your on-call agents. Rather than dealing with each alert separately, they can view a collective summary of similar alerts through an alert group. Over time, Atlassian Intelligence learns to recognize new alerts, identify patterns, and improve grouping based on user feedback.

To use the alert grouping feature, make sure that your organization admin has activated Atlassian Intelligence from Atlassian Administration. To access the feature, go to the Alerts page and switch to AI view. This works only if you’re using the new alerting feature that's natively available in Jira Service Management.

Read more about alert grouping

The team field in Jira issues now shows the team icon

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

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.

Internal note visibility restrictions for Jira Service Management

Soon you’ll be able to restrict the visibility of internal notes based on your project roles and groups.

Sometimes, teams need to hold private discussions about customer requests, and in the case of particularly sensitive topics these discussions may need to be confidential between only a few team members (such as those in your HR or Legal teams).

With the ability to restrict the visibility of internal comments, you can now continue those confidential discussions on the issue itself, without having to transfer to email or use other tools to keep the information private.

To set the visibility for internal notes, navigate to an issue and open the issue view. Find the comment section, and start creating an internal note. Then, select the Comment visibility button. Select which group or project role you’d like to restrict this comment to. Now, save your comment.

Only the comment creator and users added to the selected group or project role will see this comment once it’s saved, meaning you can continue to work knowing your confidential request information will stay private to you and your team.

Find out more about project roles in Jira Service Management, or learn how to create and manage your groups.

Attach a form directly from the request type configuration page

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

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

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

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

Learn more about the GitHub for Jira app.

Use AI to generate new content or improve existing content

Generate new content in your ideas descriptions and comments – brainstorm new content, summarize or shorten the content you already have, find action items, and improve your spelling and grammar.

Learn more about Atlassian intelligence.

Calculate delivery progress based on story points

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

Creators can configure the delivery progress field:

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

Learn more details about the estimation rules and configuration options.

New global fields page

You can now reuse fields across Jira Product Discovery projects and different Jira products. Global fields are managed centrally, so all field properties are the same across all projects and are updated from a single place.

Find more information about global fields

To reuse fields:

1. Select the settings icon from the navigation bar and then Products.
2. Under Jira Product Discovery, select Global fields.
3. Select Create global field, select the type of field you want to create, and select Create.

JPD Project fields page

Project admins can now manage project, global, and system fields in a dedicated field management section under project settings. Find more about field management in the documentation

To access the new fields management page, in your discovery project, select Project settings, then Fields.

polaris.view-header-redesign

We've shipped a few navigation improvements to make you feel more confortable when using JPD.

The new field editor is now available

We've improved the field configuration experience.

Admin center: Home entry point

The Mission control entry point in Home now intelligently displays for Confluence admins on Premium or Enterprise plans, streamlining access to vital site settings.

Key changes:

• Mission control button in the left nav now appears for Confluence product, site, or organization admins.

• Visibility of Mission control entry is exclusive to Premium or Enterprise plans, aligning with feature availability.

Smart card confluence page automation action

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

Be more expressive with panels

In addition to the five preset panel options, you can customize panels by choosing one of the 20 background colors available.

Panels can have emojis, or you can remove the emoji to meet the needs of your content. The emojis available to you are the same set that you already use in Confluence; this includes custom emojis you and your teammates added.

1. Add a panel to a page by typing /custom panel or by selecting Custom panel from the insert menu.

2. Use the floating toolbar to choose a background color and pick an emoji if you want one.

Automatically get a personal space

A personal space in Confluence is a place of your own to jot down new ideas, introduce yourself to your team, keep track of tasks, store important items or files, polish content before sharing with others, and more.

You can choose to leave the space open for others to visit and collaborate, or you can restrict the pages so that no one else can see them.

If you don't already have a personal space, one will be created for you after you've logged in and viewed a page. There are three ways to get to your personal space:

• Select Spaces in the global navigation bar. Your personal space is automatically starred for easy access.
• Select your profile icon at the top right of the global navigation bar and select Personal Space.
• Select Home in the global navigation bar. All starred spaces are shown on the right.

Learn more about personal spaces

Transfer of page ownership between users

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

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

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

Learn more about page ownership and how it can be transferred

Control what you see in your products

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

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

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

Template suggestions in the page editor

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

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

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

Home has a new look

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.

Restore and reattach inline comments, even after deleting highlighted text

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

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

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

Configure and display labeled content with clarity and ease

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

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

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

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.

Introducing content generation with richer context

Get smarter content creation with the AI-powered features in the Editor! With this update, you can now access information from your Jira and Confluence instances. Just share a link, and the AI will use data from these sources, making your content creation more insightful and comprehensive.

• Smartlinks: Use Smartlinks to seamlessly integrate information from Confluence pages and Jira issues. Simply paste a link, and the AI will automatically consider the content when crafting your prompt.
  Try: Give me a tl;dr about this project <link to project page>
• Content summarization: Get AI-powered summaries of articles, comments, Jira tickets, and Confluence content. This can help you quickly understand complex topics and extract key insights.
  Try: Summarise the work that has been done on this ticket <link to Jira ticket>
• Comprehension assistance: Leverage AI to translate user stories into technical content, highlight important points in documents, group fragmented information, and map relevant details. This streamlines your workflow and saves you valuable time.
  Try: List all the open action items from this page <link to meeting notes>

Admins can now create automation rules for public links

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

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.

Request access to a space

Can't access a space you need to access? Now you can send an access request for an admin to review.

The request will go to the space's creator, who will be notified about it inside Confluence and via email.

As an admin, you'll be able to review the request and easily add the user to Space permissions and choose which permissions they should have.

Automatically build automation rules to assign guest users to a space

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

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

Space admin Mission control

Space admins can now use Mission control in Confluence!

This change allows greater access to analytics and space management capabilities. It also allows site admins to dig deeper into information at the space level. Note: Mission control is only available for administrators with Premium or Enterprise plans.

To access Mission control:

1. Select Space settings in the left navigation bar.
2. In the new Monitoring and tools section, select Mission control.
3. View the dashboards and info in the Activity and Content management sections.

Improved collaboration with image and video comments

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.

Settings refresh: Configuration and Security

We did some spring cleaning to give a few interfaces a modern look and streamlined experience!

Key changes:

You’ll notice a more intuitive, single-page experience. We added icons, preview cards, avatars, and success/failure flags when you make changes. We’ve also localized menu options and removed these deprecated fields:

• External user management

• Custom stylesheets for spaces

• Secure administrator sessions

You can find the updated pages in the left nav, or, with their new URLs:

• Global templates and blueprints: admin/templates-and-blueprints
• Configure code macro: admin/code-macro-configuration
• Security configuration: admin/security-configuration

Configure Confluence Cloud to send emails on behalf of your domain

Organization admins can now configure custom domain emails in admin hub. Once configured, Confluence admins designate a custom domain email as their organization's site sender, so their users will receive Confluence notifications from that customized email address. More on configuring customize domain emails

Introducing Spaces report: Empower your space management

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.

Recommendation emails

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.

Embed your Jira dashboards in Confluence

You will now be able to copy a link from a Jira dashboard and paste it into Confluence as a smart link embed. This makes it easier to share your Jira data with other Confluence users.

Cache key support for self-hosted runners

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

Introducing 100MB file size limit

Starting on May 6, we will begin rolling out a 100MB file size limit for Git pushes to Bitbucket Cloud repositories. Learn more about the new file size limit and join in on the conversation via our community post.

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

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.