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

New roles and other improvements to the original user management experience

We updated the users and groups pages in the original user management experience. You’ll notice a new look and feel generally, including a new profile layout, on top of other usability and performance improvements. It’s also easier to navigate pages with many results and use filters to find specific users or groups.

Roles: You can now assign some app roles that weren’t previously supported in the original experience. These roles are Jira Service Management stakeholder and customer and Compass basic user.

Statuses: Has site access, No site access, and Account disabled statuses are now Active, Suspended, and Deactivated, respectively. You can filter your users list by these statuses, which come with colored indicators for quick recognition. Status is also now more prominent in a user’s profile.

Users: All actions in your users list are now in the more actions menu, including a new shortcut to remove a user from the site. To see or change a user’s roles, go to their profile, which now shows you specific app roles they hold.

Groups: Your groups list now shows you how many members are in a group and how many apps a group has a role for. You can also filter for groups that have a role for a specific app. In a group profile, you can search for a member and also see when they were last seen in the current site.

Soon, you’ll be able to manage your users and groups across multiple directories (sites) in one place. More about user management improvements

To explore these changes:

1. Go to your site administration in Atlassian Administration.
2. Select Users to see the new users list. Select any user to see the new user profile.
3. Select Groups to see the new groups list. Select any group to see the new group profile.

Your organization-wide default data classification level now applies to Jira

Data classification is the process of categorizing the sensitivity of information.

Previously, a default data classification level could only be applied to Confluence apps. We've now expanded this to include Jira, allowing you to set a default data classification level across both apps. This level will automatically apply to all unclassified content within these apps.

If you've already set a default data classification for your organization, it will now apply to all unclassified content in Jira, in addition to Confluence. If no organization-wide default classification level is set, content in Confluence and Jira will remain unclassified by default. However, you still have the option to set a default data classification level for specific spaces and projects.

Data classification is a feature that requires Atlassian Guard Premium.

To apply a default data classification level across Confluence and Jira in your organization:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data classification.
3. Select More actions (•••) > Manage settings.
4. Choose the classification level.
5. Select Update.

Introducing multiple webhooks for audit log in Atlassian Administration

We’re excited to announce a major enhancement to audit log integrations in Atlassian Administration, you can now register up to three webhooks per organization!

To register a webhook URL:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Audit log.
3. Select Settings.
4. Select the Webhook tab.
5. Select Add webhook.
6. Enter a Name for the webhook.
7. Enter the Webhook URL (the destination where you wish to receive real-time activity updates).
8. Optionally enter secure authorization credentials to authenticate access to a protected resource. Encode the username and password as Authorization: Basic <credentials>.
9. Select Add.

You can edit or remove a webhook if you need to.

Rename managed teams in Atlassian Administration

Earlier this year, we introduced Managed Teams as a new type of team that is synced to a group with the caveat that the team would have to share the name of the group. In June, the team names could be changed from the Team profile but with this release, we've made it so managed teams can now be renamed in Atlassian Administration as well.

To rename managed teams in Atlassian Administration, both new and existing teams can be named when being connected to a group. For teams that have already been connected:

1. Go to the group page with the connected team in Atlassian Administration.
2. Find the Team field in the side panel and select the ... button.
3. Select the "Edit team" option in the menu.

Rovo customer admins can now add bookmarks

Admins (organization, site or product) on sites with Rovo can now add bookmarks to highlight particular URLs in Rovo Search, based on specific search terms. You can bookmark any URL - it doesn’t need to be in your Atlassian products or previously found in search.

There are two different methods to add bookmarks depending on whether you are a organization admin, or a site/product admin.

How to add or edit Rovo Search bookmarks

Copy specific Jira Service Management and Jira Work Management projects to your sandbox

Copy only the projects you need to save time setting up your Jira Service Management and Jira Work Management sandbox. Understand how to select data to copy

To copy specific Jira Service Management and Jira Work Management projects from your production to its sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Sandbox.
3. Select Copy production data for the Jira Service Management or Jira Work Management product.
4. Select Specific projects.
5. Select the service or work management projects you need.
6. Follow the prompts to copy data to your sandbox.

More about what we copy to sandboxes

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.

Accessibility and style improvements to tables and page layouts

We restyled tables and updated the layout of pages. This improves accessibility and readability in Atlassian Administration.

You can see the changes on most pages in admin.atlassian.com.

Apply a default classification level for your entire organization

Data classification is the process of categorizing the sensitivity of information.

Apply a default classification level that can be enforced across your entire organization, enabling you to implement data classification quickly at scale. This classification level will be applied to all unclassified content within the organization.

This process requires Atlassian Guard Premium.

To apply a default classification level across your entire organization:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data classification
3. Select More actions (•••) > Manage settings
4. Choose the classification level
5. Select Update

Copy specific Jira projects or Confluences spaces 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 Jira projects or Confluence spaces from your production to its sandbox:

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

Learn about what we copy to sandbox

Apply a default classification level for all Confluence products in your organization

Data classification is the process of categorizing the sensitivity of information.

Apply a default classification level that can be enforced across all your Confluence products in your organization. This classification level will be applied to all unclassified content within Confluence.

This process requires Atlassian Guard Premium.

To apply a default classification level for all Confluence products in your organization:

• Go to admin.atlassian.com. Select your organization if you have more than one.
• Select Security > Data classification
• Select More actions (•••) > Manage settings
• Choose the classification level
• Select Update

Prevent your team from using new Bitbucket workspaces without your approval

You can now proactively manage product requests for Bitbucket from admin.atlassian.com. This feature provides you with more oversight to control Shadow IT and billing.

After you select admin review required, you can approve or deny new Bitbucket requests from your managed accounts. This gives you greater control over where your team does their work.

This is available for Bitbucket as part of a beta program. It’s also available for Jira, Jira Service Management, Confluence, and Trello with an Enterprise subscription.

More about product requests

To manage product requests for Bitbucket:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Product requests.
3. Select Request settings. If this is your first time updating these settings, you may need to select Update request settings.
4. Next to Bitbucket, select Require admin review under the Request setting dropdown.

The next time one of your managed accounts tries to sign up for a product, they’ll receive a prompt to enter a reason for their request. After they create the request, all organization admins receive an email, letting them know someone created a request.

Prevent people from downloading attached files

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

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. Our findings showed that the types organizations needing to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policies currently block exports:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Limit mobile app sessions for users

You can now control when a mobile app session expires from an authentication policy. You’re able to update the mobile app session setting with the number of days for a session. This setting applies only to managed accounts in an authentication policy.

To ensure uninterrupted access to the mobile app, we prompt users to re-authenticate before their session expires.

Mobile app session applies to these mobile apps:
Jira Cloud
Confluence Cloud
Opsgenie (Atlassian Accounts only)

To update the mobile app session expiration:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Authentication policy.
3. Select the policy you’d like to Edit.
4. Enter number of days for when the Mobile app session expires.

Understand authentication policies

Control access to Compass with IP allowlisting

You can now apply IP allowlists to your Compass sites so that users can only access Compass from specific IP addresses. This gives you an extra layer of security.

IP allowlists for Compass requires a Premium subscription.

To apply an IP allowlist to Compass:

Go to admin.atlassian.com. Select your organization if you have more than one.
1. Select Security > IP allowlists.
2. Select Create allowlist.
3. Enter allowlist details.
4. For Applies to, select Compass.
5. Select Create.

Read more about IP allowlists

Introducing your new user requests page

We’re consolidating your access requests into one convenient new page called User requests. We’re also moving it from site administration to your organization.

Why? To give you better visibility over access requests from all sites in your organization. Plus, we’re introducing a new feature called User interests, where you can keep track of and review trending user interest in new apps.

The new experience will be available to Organization admins, and Site admins with centralized user management. Read more on user management

To get started:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > User requests
3. Select Access requests or User interests

SCIM API keys expire in one year

We're changing the expiration date for SCIM API keys from an infinite lifespan to a one year expiration date: This change applies only when you:

-set up user provisioning for the first time
-regenerate an existing SCIM API key

This change does not affect existing SCIM API keys for now.

We’re making this change to reduce security risk for any leaked or stolen keys and to encourage you to rotate your keys. If a key is leaked or stolen, its limited lifespan prevents attackers from using it indefinitely to access sensitive information.

When is this changing?
-On December 15, 2024, SCIM API keys expire in one year. This includes a SCIM API key that we create when you set up user provisioning or when you regenerate a SCIM API key.

How to view the SCIM API key’s expiration date when you set up user provisioning:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your Identity provider Directory.
4. Select Set up user provisioning and follow the prompts.
5. View API key expires date in User provisioning.

How to view the SCIM API key’s expiration date when you regenerate an API key:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your Identity provider Directory.
4. Select Regenerate API key from […} and follow the prompts.
5. View API key expires date in User provisioning.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Tailor your Jira Service Management sandbox setup

We're excited to introduce a new feature that allows you to save time by copying only the specific Jira Service Management (JSM) projects you need to your sandbox. This enhancement streamlines the setup process, ensuring you have exactly what you need without unnecessary clutter. Additionally, audit logs now track the copying of specific projects, providing a clear record of changes for better management and oversight. Understand how to select data to copy

To copy specific Jira Service Management (JSM) projects from your production to its sandbox:

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

Learn about what we copy to sandbox

Choose what an API key does in your organization

You can now choose what an API key can do with scopes, which are specifically the actions an API key has permission to perform. You’re able to allow APIs to view, write, and delete content in your organization.

To create an API key with scopes:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > API keys.
3. Select Create API key.
4. Enter a Name that makes it easy to remember the API key.
5. Select the expiration date for the API key. Keys can last no longer than a year.
6. Select API scopes to choose what the API key can do in your organization.
7. Review your API key information.
8. Select Create to save the API key.
9. Copy your API key and save it somewhere safe. You can't recover the API key later.

See how Rovo usage is trending in your org

Atlassian Rovo uses AI-driven insights to help you turn information into action. To follow usage trends, view the number of requests your users have sent to Rovo Chat or Agents. Use the date range filter to see usage trends over time.

Explore Rovo features

To view usage trends for Atlassian Rovo:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the AI usage tab.
4. Navigate to the Requests sent to Rovo chart.

Org insights, now with better organization

We’ve updated the Insights page so there’s less scrolling to find the right user and activity charts. There are now tabs on the page to group related charts.

To view your organization’s refreshed Insights page:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select a tab to see your charts.

Copy dashboards from one Jira app to another

When you copy data from one Jira app to another, you can choose to copy:

• All dashboards
• Dashboards that are linked to the projects you want to copy.

Gadgets added to dashboards are also copied.

To copy dashboards:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Settings > Data transfer.
3. Select Start copying.
4. Select Create copy plan.
5. On the How it works page, select Next.
6. Select Jira products.
7. Select your source and destination.
8. Select the projects you want to copy.
9. On the Select data you want to copy page, select one of the following options:
   • Only dashboards linked to selected projects
   • All dashboards
   • Don't copy dashboards
10. Select Next and follow the steps to copy data.

Removal of trusted user role

We’re removing the trusted user role on March 27, 2025. This change applies to customers who have the original user management experience.

From March 27, 2025, you’ll no longer be able to assign this role to a user. Existing trusted users will still be able to access products and product administration. They won’t be able to invite users or add a product to a site.

Trusted users currently belong to a group that’s hidden from Groups. This group assigns trusted users their user and product admin roles. When we remove the trusted user role, we’ll unhide this group so you can continue to manage its users as a group. It will appear in Groups as trusted-users-<site ID>.

We’re making this change to bring customers who have the original user management experience closer to the centralized user management experience. You can read more about this in our Community post.

We recommend you inform your trusted users of this change. To find the trusted users for a site, go to admin.atlassian.com > Products. Navigate to the site, then select “Trusted” in the “Any role” filter.

If you need to give a user the ability to invite new users or add products to a site, make them a site or organization admin. How to assign admin roles

Find out which external users have customer role access to Jira Service Management

You can now track external users that have customer role access to Jira Service Management.

To see this information, you can export a CSV file in Atlassian Administration.

To export the CSV file of external users:

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

2. Select Security > External users.

3. From the External user policy or test policy, select … > Export external users

How to export external users

Reactivate your inactive custom domains

You can now reactivate your previously suspended custom domain. Instead of remaining suspended, your custom domain will be marked as inactive, allowing you the option to activate it whenever you want.

If you're unable to activate your custom domain you may see an Error status, Provisioned status, or an error notification next to your CNAME records. To fix this, you can troubleshoot your custom domain.

To activate your custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select the Custom domains tab.
4. For the domain you want to activate select More Actions (…) > Activate domain.

Manage access to analytics for all apps

We're introducing a new setting for analytics, which enables admins to choose whether or not the apps they're using can send data to third-party analytics tools. Check the documentation for the permissions you may need to access the new setting.

By default, this setting is enabled, which allows data sharing for all new app installations. However, admins can choose to enable or disable this setting at any time from the Connected apps page, even before a new app is installed on to a site. Admins can also configure this setting for individual apps at any time.

Manage your integrations and automations with service accounts

You can now create service accounts to manage automations, integrations, and apps for your Atlassian organization.

You’re able to manage the service account lifecycle the same way you manage a user account. You can create and edit the account. You can also give the account app permissions, edit the details of the service account profile, and create an API or OAuth token with scopes for the service account.

To create a service account:

1. Go to Atlassian administration. Select your organization if you have more than one.
2. Select Directory> Service accounts.
3. Select Create a service account.
4. For service account name, enter an alphanumeric Name with 6 to 30 characters.
5. For the optional Description, we recommend you enter the name of a person or app that uses the account.
6. Select roles for the apps that the service account needs to access. You can also add the service account to a group.
7. Select Create.

After you create a service account, you can create an API token or an OAuth token for the service account.

Admins can now see Rovo indexed objects for each third-party connector

Organization admins can now see the number of indexed objects against each Rovo third-party connector. To find out more about indexed objects and Rovo quotas, see Rovo usage quotas.

To see the object count:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Settings > Rovo.
3. Expand the site where you’ve connected a third-party app.

Control access to external user email and notifications

We’re improving how you manage access to email content and notifications for external users. You can now set email and notification visibility in your external user policy.

This means you control whether external users receive content in emails from apps like Jira and Confluence. You can also control if external users receive mobile app push notifications.

To control email and notification visibility, you can choose to:

Allow - Allow external users to receive content in their emails and mobile push notifications.
Block - Block external users from receiving content in their emails and mobile push notifications.

To update email and notification visibility:

1. Log in to admin.atlassian.com > Security > External users.
2. Select a policy.
3. Select Allow or Block for Email and notification visibility.
4. Update the policy.

Monitor user API tokens without a subscription

You no longer need an Atlassian Guard Standard subscription to monitor the usage of user API tokens.

At no extra cost, you can view when a token expires, when it was last used and who created it. You can also revoke a token if you need to. You can track these details about user API tokens only for your managed accounts.

Explore user API tokens

To view user API tokens:

1. Log in to admin.atlassian.com > Security
2. Select User API tokens.

We're renaming 'products' to 'apps'

At Team ‘25, we announced a shift in how we think about and refer to our suite of individual products, now called ‘Atlassian apps’, or ‘apps’ for short.

We’ve started rolling out this terminology change (from ‘products’ to ‘apps’) across Atlassian Administration experiences. Over the coming months, we’ll continue to roll this out to admin emails, support documentation, audit logs, URLs, and more. You may see both terms used as we work through this change.

The way you manage Atlassian apps like Jira and Confluence in Atlassian Administration remains unchanged.

Read more about this change on Atlassian Community

Experience improved reliability and loading time when using Discovered products

In response to recent customer feedback, we’ve made some important updates to the Discovered products screen and process.

We’ve redesigned the screens to improve loading time, and restructured the code to improve the reliability of rendering. These changes should prevent loading failures where customers have high numbers of discovered products. How to review discovered products

To get started:

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

Atlassian Intelligence & Rovo: Filter active users by site and date range

To better assist you in monitoring adoption trends, we've enhanced the ‘active user’ charts for Atlassian Intelligence and Rovo. You can now filter these charts by:

• • Date range:* View usage trends over specific time periods.

• • Site:* Identify where artificial intelligence features are being used most (if your org has multiple sites with Atlassian Intelligence or Rovo activated).

Understand how Atlassian Intelligence is activated for products, and how Rovo is activated for sites.

To view usage charts for Atlassian Intelligence and Rovo:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the AI usage tab.
4. Navigate to the relevant chart.

You will only see charts for the artificial intelligence tools that are activated and being used in your organization. More on gaining insights into product usage

Keep your team focused by temporarily blocking changes to Atlassian apps

You can now stop receiving changes to Atlassian apps during business periods, such as tax seasons or holidays. Schedule a freeze window, up to 60 days in advance, to keep your team focused during such periods. More about freeze windows and which types of changes won’t roll out during a freeze window

This is currently in beta. Visit our post on Community to learn more or give feedback.

To schedule a freeze window.

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Apps > Freeze windows.
3. Select Create freeze window and then follow the prompts.

SharePoint connector now has blocklist and allowlist

The Rovo SharePoint connector now includes support for both blocklist and allowlists. This gives finer control into what content is indexed by Rovo and Atlassian from your SharePoint instance. As an admin, you can configure these while you connect for the first time, or by managing an existing connector.

Improved audit log webhook registration

We've enhanced the webhook registration process to simplify how you edit webhook details.

To edit the details of a registered webhook:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Audit log.
3. Select Settings.
4. Select the Webhook tab.
5. Select Edit details to update the details.

Runs on Atlassian program for cloud apps

We've rolled out a new program for cloud apps called Runs on Atlassian.

Apps that qualify for the program automatically get the Runs on Atlassian badge on their listing page. You can also browse and filter for Runs on Atlassian apps on the Atlassian Marketplace.

Runs on Atlassian addresses the following requirements from customers:

• Apps exclusively use Atlassian-hosted compute and storage.
• Apps support data residency that matches data residency provided by the host product.
• Customers are in control of data egress, such as analytics and logs, and can fully block data egress at any time.

Learn more about the program and what it means for you and your organization.

Provision employee identity information from your identity provider

You can now provision the employee identity (ID) for managed accounts in your organization. When you provision managed accounts through SCIM to your organization, you can view the employee ID for a managed account in their account profile.

To provision employee ID, you need to update the attribute in your identity provider with the following employeeNumber attribute:

urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber

How to map identity provider attributes for Okta, OneLogin, or Microsoft Azure AD

After you update the attribute and sync your managed accounts, you can view the employee ID in their account profile.

To view employee ID:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory > Managed accounts.
3. Select Show details for a user.
4. Select More details.

SCIM API keys set to expire

Your existing System for Cross-Domain Identity Management (SCIM) API keys currently have an infinite lifespan. Starting on April 28, 2025, we will set your keys to expire between May 1, 2026 and May 1, 2027.

What is an existing SCIM API key?
An API key generated before January 1, 2025.

Who does this change apply to?
Identity providers that provision users with SCIM to an Atlassian organization.

This change does not apply to these identity providers: Google Workspace or Microsoft Azure AD for nested groups.

Why are we making this change?
To encourage you to rotate your keys to reduce the risk of leaked or stolen keys.

What action do you need to take?
You don’t need to do anything at this time.

When we make this change you can view the expiration date for your existing SCIM API key.

To view the expiration date of your SCIM API key:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your identity provider Directory.
4. Select Provisioning.
5. View API key expires date in Provisioning.

More about user provisioning

Actor filter in audit log is now available to all organizations

We're excited to announce that the actor filter within the audit log in Atlassian Administration is now available to organizations using the original user management experience. This enhancement allows more organizations to efficiently track and manage activities.

To determine which user management experience your organization is using, follow these guidelines:

• Centralized experience: In Atlassian Administration, Users is located in the Directory.
• Original experience: In Atlassian Administration, Users is located in Apps > site.

Create Jira Product Discovery sandboxes

Set up projects, change configurations, and test on a Jira Product Discovery instance within an isolated environment. Sandbox is available for Jira Product Discovery on the Premium plan. More about sandboxes

To add a Jira Product Discovery sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Apps from the navigation bar.
3. Select Sandbox from the sidebar.
4. From the table of sandbox URLs, select Add and select Jira Product Discovery. (If you don’t have a sandbox site, select Create sandbox to create one.)

Discovered apps: clearer admin details

To help you better manage your Discovered apps (Shadow IT), we now display the organization admin’s name and profile picture in the table. We’ve also added a summary of how the user count is calculated. How to review discovered apps

To view details of discovered apps:

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

Atlassian Administration: improved navigation and visual refresh

We’re excited to share that on August 4, we’ll start rolling out our improved navigation, new sidebar categories, and refreshed look and feel across Atlassian Administration. These changes will be rolled out progressively, so you may see just the new navigation or the full experience. During the rollout, you’ll be able to switch between the classic and new experience. More details in the community post

Once rolled out, you can view the new navigation and categories in Atlassian Administration.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

New activities added to audit log in Atlassian Administration (June edition)

We have added new activities to the audit log in Atlassian Administration. You now view these new categories: Encryption actions, Anti Abuse, Focus user actions, Goals user actions, Service account actions.

Additionally, we've expanded the audit log capabilities with new activities for: Jira Service Management Assets Actions, Jira Service Management Product Actions, Loom user actions

These enhancements provide greater visibility and control over user and system activities, ensuring improved security and management within your Atlassian environment.

Explore the audit log activities database to view a comprehensive list of all activities that occur within an Atlassian organization.

Go to insights from mobile app policies

We added a link to mobile usage insights on the mobile app policies page. You can now navigate to mobile insights easily after creating or updating a mobile app policy.

To view mobile app usage information:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the Mobile usage tab.

If you have a mobile app policy, you can now also navigate to this page from Mobile app policies:

1. Select more actions (•••) in the page header.
2. Select View mobile usage. This takes you to Insights, on the Mobile usage tab.

Monitor all AI user activity in your org from a single chart

We've merged the Active Atlassian Intelligence users and Active Rovo users charts into a single chart: Active AI users.

This new chart offers a streamlined view of user activity, making it easier to monitor and analyze AI feature usage across your organization.

To view this change:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the AI usage tab.
4. Navigate to the Active AI users chart.

Improved usability and performance of user profiles

We made user profiles easier to use. This change applies to customers who have the centralized user management experience.

We moved the Apps and Groups tables into tabs. You can now choose how many apps or groups to show in each table, so you can see as many as you want at a glance. This update also adds filters to help you find certain apps or groups when there are many results.

We made the user status more prominent so you can easily see if the user has access to your organization or not.

More user management improvements

To go to a user’s profile:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory.
3. Select the user.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Set a session expiration for mobile app users

We added a link to authentication policies on the mobile app policies page. You can set mobile app session expiration for your managed accounts in an authentication policy.

We recommend you set a mobile session to 30 days.

To set mobile session expiration in an authentication policy:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Authentication policies.
3. Select Edit for the policy you want to modify.
4. Look for Mobile app session expiration in the Session controls section. Enter the number of days for a mobile session.
5. Select Update to update the policy.

If you have a mobile app policy, you can now also navigate to this page from Mobile app policies:

1. Select more actions (•••) in the page header.
2. Select View mobile session. This takes you to your authentication policies.

More control over Admin API key scopes

We’re separating this Admin API key scope: API keys and tokens. You could only choose the API keys and tokens scope together, but now you can choose one or the other. We want to give you more control when you select an Admin API key scope.

What do you need to do?
When we make this change, we automatically assign the scope to API tokens only. If you want to assign the API key scope, then you need to create a new API key and select the scope.

To assign API key scope:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Settings > API keys.
Select Create API key.
Enter a Name that makes it easy to remember the API key.
Select the expiration date for the API key. Keys can last no longer than a year.
Select scopes> Read API key scope
Review your API key information.
Select Create to save the API key.
Copy your API key and save it somewhere safe. You can't recover the API key later.

More about API keys with scopes

Transfer data: Copy Atlassian teams

When you copy data from one Jira app to another, Atlassian teams are copied along with users and groups. Within Atlassian, you can switch between apps using the button in the top left corner of the navigation bar and find Teams from the list of available apps.

New ‘Source’ filter for Jira Service Management customers

We’ve added a new ‘Source’ filter that makes it easy to sort and view customers by how they were added to your Jira Service Management site. This helps you manage and understand your customer base more easily.

This filter has two options: select ‘Manual’ to view customers who were added directly through Jira Service Management, or select ‘Synced’ to display customers provisioned from an external identity provider.

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Products from the header.
3. Under Sites and products, select the site that contains Jira Service Management.
4. Under the Jira Service Management section on the nav bar, select Portal-only customers.
5. Select the Source filter and select an option.

Read more about managing accounts for Jira Service Management customers

New activities added to audit log in Atlassian Administration (July edition)

We have added new activities to the audit log in Atlassian Administration. You now view these activities under: Confluence user actions, Focus user actions, Loom user actions, Settings, Team management and User management.

These enhancements provide greater visibility and control over user and system activities, ensuring improved security and management within your Atlassian environment.

Improved usability and performance of group profiles

We made group profiles easier to use. This change applies to customers who have the centralized user management experience.

You’ll find the group description and summary of members and apps in a card, similar to a user profile. We moved the Members and Apps tables into tabs. You can now choose how many members or apps to show in each table, so you can see as many as you want at a glance. This update also adds search and filters to help you find certain members or apps when there are many results.

More user management improvements

To go to a group’s profile:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory > Groups.
3. Select the group.

Improved usability and performance of the groups list

We made improvements to the organization’s groups list so it’s easier to use. This change applies to customers who have the centralized user management experience.

Use the Apps filter to find groups that grant roles to a specific app. Add users or grant access to a group in the actions column, without navigating to the group profile.

Choose how many groups to show per page, so you can browse your groups list more efficiently. You can also sort groups by their name with this update. We also updated the look and feel of the page.

More user management improvements

To see your organization’s groups list:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory > Groups.

Reducing ‘issue’ terminology in Jira

We’re reducing the use of 'issue' terminology in an effort to simplify our language and better suit all team types.

Smart Links are now available in more fields

Add and view Smart Links in URL and short text fields. This will apply to your issue, list, board, and backlog views.

From your list or issue view, copy a valid URL link into a URL or short text field.

Read more about using Smart Links

Smart Links available in more fields

Add and view Smart Links in URL and short text fields. This will apply to your issue, list, board, and backlog views.

From your list or issue view, copy a valid URL link into a URL or short text field.

Highlighted search terms in in-product help

When you search in in-product help, we'll highlight your search terms in results so you can quickly see how the results relate to the terms you've entered.

To search in in-product help, select the help (question mark) icon in the navigation and enter your query in the search field.

Note: In-product help is available in many screens in Jira, including in software, service desk, and work management projects. There may be some screens where in-product help isn't available yet.

Edit your help center's home page layout and add rich content to it

With this release, admins will have more control over their help center's home page, allowing them to tailor it to fit the needs of their audiences. They will be able to:

• hide and reorder sections on the home page to create a more organized experience
• add layouts, images, and rich content to make the help center visually engaging and user-friendly.

This will help admins create a more customized and appealing help center for their different audiences.

Nest media and codeblocks in quotes

We’ve added the capability to nest media (images, videos, etc.) and codeblocks inside of quotes in the editor. This allows for better context when formatting quotes.

• • Media in quotes*: Users can now embed images, videos, and other media types within quotes, enhancing visual context.

• • Codeblocks in quotes*: Codeblocks can now be nested inside quotes, making it easier to reference and highlight code snippets within discussions.

New and updated virtual agent Channel management

This update simplifies channel management and enhances the visibility and usage of the virtual agent across your Jira Service Management projects.

Streamlined configuration: For a more efficient admin experience, manage all channel configurations from a single Jira Service Management channel home.

Centralized channel visibility: View all connected channels with the virtual agent in one place.

Unified testing: Test draft intents and AI Answers directly from the web preview, eliminating the need for specific Slack request channels.

Read more about how to use the virtual agent in your customer channels

A new home for help center customization features

Quickly access customization options for your help center. All customization features related to the help center are have now moved under the Customize button in the top navigation. From there, you can manage announcements, add login page messages, customize the look and feel, manage topics and portals, and edit the layout of your help center.

Creating a Jira issue can now trigger an automation in Confluence

We're adding a new trigger to Confluence automation that will let you run a rule when a new issue is created in a specified Jira project.

Space and product admins can build a rule by navigating to a page and selecting the Automation (lightning bolt) icon.

1. Select Issue created in Jira as your trigger.
2. Select Connect to connect Confluence to your Jira project.
3. If your organization has multiple Jira sites, you will need to select a Jira site from the Create connection menu.
4. Select one or more projects from the dropdown menu.
5. Continue to build your rule.

Collect higher quality information with business forms

Gather better quality information with new functionality for business forms.

Choose from more fields including parent, category and people. Have more control by making fields optional or required to submit when building a form. You can also add more detailed guidance for people submitting a form, by adding field descriptions.

Manage your form fields

To find updates to business forms, you’ll need project admin access:

1. Open a business project and navigate to Forms in the project navigation.
2. Select an existing form or select + Create form
3. Find all new functionality while building your form.

As part of the shutdown of the "External Assets Platform", the ability to create, add, or modify "External Assets Platform" custom fields has now been removed

As part of our ongoing efforts to deliver the most streamlined and integrated service management solution, the ‘External Asset Platform’ will be shut down.

Learn more about the shutdown of the 'External Assets Platform'.

This change will take place in two stages: currently, we are removing the ability to create new "External Assets Platform" custom fields, add these fields to projects, or modify the contents of existing "External Assets Platform" custom fields.

Ultimately, all existing "External Assets Platform" custom fields will be removed, along with any data contained in them. If you have not yet begun backing up your data from your "External Assets Platform" custom fields, we recommend you do so immediately using the provided script.

Efficiency improvements in the calendar view

In our ongoing effort to streamline tasks and enhance your experience with the calendar view, we’re rolling out the following improvements:

• Load more issues without pagination — We’ve replaced the page numbers at the bottom of the calendar with a single Load more button. Selecting this will keep currently loaded issues in view while loading the next 50.

• Real-time updates — If you create, update, or delete an issue, other team members viewing the calendar will see those changes in real-time without reloading the page.

• Hide done items via URL — If you switch on the toggle to hide done items, the parameter hideDone=true will be added to the page’s URL. If switched off, the parameter will be removed. You can use these URLs to share exactly what you’re seeing, without unnecessary configuration. This change is only applicable to business projects.

• Manage issue types — While creating issues in the calendar, you’ll notice a new option to Manage types in the issue type dropdown. Selecting this gives you quicker access to the issue type configuration page in project settings. This change is only applicable to software projects (to match existing functionality in business projects).

• Improved sorting — When a day in the calendar contains multiple items, you’ll notice a consistent sorting pattern that better shows the continuity of longer events and prioritises important context like sprints and releases. Sprints will always appear at the top of the day, followed by multi-day events, releases, and single-day events.

Unless otherwise stated, these changes will be available on software projects, business projects, plans, and Jira Service Management.

To try out these improvements, head to the calendar by going to your project, then select Calendar in the sidebar.

The 'External Assets Platform' Custom Field now includes a shutdown notice

The ‘External Asset Platform’ will be shut down on 17 December 2024 as part of our ongoing efforts to deliver the most streamlined and integrated service management solution.

Learn more about the shutdown of the 'External Assets Platform'.

Now, when you view the 'External Assets Platform' custom field, a DEPRECATED notice will appear in front of the custom field with a warning icon. If you click on the warning icon, you will see additional information and a link to the shutdown notice page that is linked above.

When you create a new custom field of the 'External Assets Platform' type, a warning about the shutdown will also be displayed.

Finally, for existing 'External Assets platform' custom fields that appear within Jira issues, a warning icon will appear next to the custom field name. If you hover over the warning icon, you will see additional information about the shutdown.

Collect more relevant work requests with Jira forms

Collect only the relevant details from your stakeholders. By creating conditions, you can now show specific questions based on responses to previous questions.

To begin creating conditions on a form, you’ll need project admin access:

1. Open a Jira project and navigate to Forms in the project navigation.
2. Select an existing form or select + Create form.
3. Add a priority field, or any custom multi-select or single-select fields to the form builder.
4. Select that field from the form builder to edit.
5. Select Add condition.

New Okta actions available in Automation!

We’re excited to announce that we’ve built a new integration with Okta! This integration makes it possible to create a connection between your automation rules and Okta, giving you new ways to use Automation to handle your user lifecycle management needs. The connection with Okta can be made from Automation in Jira Service Management with these two new actions:

Create user in Okta – auto-creates a user in Okta.

Retrieve user details from Okta – checks if a user already exists in Okta, so you can avoid duplicating users.

Read more about how to use these actions and connect your automation rule to Okta.

Introducing 'work' as the new collective term for items tracked in Jira Cloud

As more teams make Jira their home for work, we’re committed to improving the language in our tools to better reflect the diverse ways you define and manage your work.

We’re introducing work as the new collective term for all items tracked in Jira. We’re also exploring ways to incorporate the language you use for your own work types.

• Read more about these changes on the Atlassian Community.

This change builds upon our previous efforts to reduce the use of 'issue' terminology in Jira.

Beta: Generate work item descriptions from Confluence links using AI

AI can assist in generating work item descriptions when you simply paste Confluence links into Jira. By using the context from the Confluence link placed in the description field of the work item, AI creates structured content to generate and improve the description.

To generate work item descriptions:

1. Paste a Confluence link in a work item’s description field. If a Confluence link is already present, edit the description field.
2. Select Improve description.
3. Once the description is generated, select either Insert below or Replace to update the work item description.

Jira: Use JQL performance suggestions to optimize your company-managed board.

See how you can improve your Jira board’s performance. Use JQL suggestions tailored for you.

Go to your board:

1. Select (…) More actions then Configure board.
2. Go to Board filter.
3. If your JQL is missing a top-level project term, you’ll see a JQL suggestion with the title Edit filter to improve performance.
4. Select Edit filter query to review and save your filter with the suggested improvement.

Jira: Fixing JQL query errors using AI is now generally available

We’re excited to announce that AI-powered JQL error fixing is now generally available in Jira.

This feature automatically detects and suggests fixes for common issues, like syntax errors and typos, saving your time and effort when troubleshooting queries. It helps you quickly get to the work you need by making JQL easier and more reliable.

Simply enter and run your JQL query. If there are any errors, they’ll be listed below the editor, along with an AI-generated, error-free query that you can review and instantly apply.

Jira: AI work item creation from Microsoft Teams is now generally available

We’re excited to announce the general availability of AI-powered work item creation from Microsoft Teams chat.

You can now use AI to create Jira work items directly from Microsoft Teams chats. AI analyzes your chat context to quickly generate work item details, saving you time. The content is automatically localized to the language set in your MS Teams settings, ensuring clarity and relevance. Additionally, the AI-generated descriptions follow a pre-defined structure based on the work type, maintaining consistency. Using AI is the default creation method, but you can turn it off anytime while creating work items.

To create Jira work items in Teams using AI:

1. Add Jira Cloud to the team, channel, or meeting chat.
2. On a message in your chat, select the More options (···), then select Create issue in Jira.
3. Choose a project and work item type.
4. If not already selected, select Use Atlassian Intelligence to generate the summary and description to allow AI to generate the work item details.
   • The app remembers your previous selection and apply it each time until you decide to change it.
5. Fill in any additional fields as required and select Create to create the work item.

Rovo search in Jira now includes label, reporter, and status filters

You can now filter your Rovo search results in Jira by label, reporter, and status. This update makes it easier to find the content you need by narrowing down your search using these new filter options.

To use the new filters in Rovo search within Jira:

1. Open Jira and go to the Rovo search experience.
2. Enter your search query as usual.
3. Use the new filter options for label, reporter, and status to refine your results.

A more stable way to display media in Jira’s work item view editor

Media in Jira’s work item view editor will now use pixel widths instead of relative sizing. This change helps prevent media from resizing unexpectedly while content loads, providing a more consistent experience.

Resize using the new handle: Resize your images using the drag handle located on the sides of the images. Your image will proportionally grow or shrink based on how much you drag it in and out.

Resize using the new pixel entry: Select the image, enter the size in pixels you want, and hit ‘return’. Simple!

What happens to my previously inserted images? Pages containing legacy images, which are not pixel entry or custom sizes, can be easily transformed to the new image resizing format by simply selecting the 'Convert to pixels' option while choosing the image. The images that require conversion will be indicated by a yellow dot located in their top-right corner.

Category field editing is now available in All work

You can now create, delete, and update the Category field options directly in Jira's All work view in both company-managed and team-managed projects. This gives project administrators more flexibility to manage categories without leaving the All work view.

To edit Category options in All work:

1. Make sure you are a project administrator.
2. Ensure the Category column is visible in your All work view.
3. Navigate to the header cell for the Category column.
4. Select the "More actions for Category" button to open a dropdown menu.
5. Select the "Edit field" option in the dropdown.
6. Create, delete, or update Category options as needed in the side panel that appears.

Jira's full screen mode now delivers a more consistent and immersive experience

We’re extending and refining Jira’s full screen mode, introducing a more consistent, immersive, and productive experience across all major Jira views.

To try the updated full screen experience in Jira:

1. Open any major view in Jira, such as a board, backlog, or work item view.
2. Select the full screen icon in the top right corner of the view.
3. Explore the updated layout and navigation in full screen mode.

Your organization-wide default data classification level now applies to Jira

Data classification is the process of categorizing the sensitivity of information.

Previously, a default data classification level could only be applied to Confluence apps. We've now expanded this to include Jira, allowing you to set a default data classification level across both apps. This level will automatically apply to all unclassified content within these apps.

If you've already set a default data classification for your organization, it will now apply to all unclassified content in Jira, in addition to Confluence. If no organization-wide default classification level is set, content in Confluence and Jira will remain unclassified by default. However, you still have the option to set a default data classification level for specific spaces and projects.

Data classification is a feature that requires Atlassian Guard Premium.

To apply a default data classification level across Confluence and Jira in your organization:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data classification.
3. Select More actions (•••) > Manage settings.
4. Choose the classification level.
5. Select Update.

Request access when you can’t view a work item

You can now request access to a work directly. This allows you to quickly ask project admins for permission to view a work item or project, so you’re not left at a dead end.

To request access to a work item:

1. Open the work item you don’t have permission to view.
2. Select Request access on the “You don’t have access to this work item” screen.
3. You’ll see a confirmation that your request has been sent to the project admins.

To review and grant access as a project admin:

1. Next to your project's name in the sidebar, select More actions (•••), then Project settings.
2. If you're in a company-managed project, select People.
3. If you're in a team-managed project, select Access.
4. Select Access requests to see pending requests.
5. Review the request and assign the appropriate project role to grant access.

Company-managed projects: Currency and percentage formatting now available on number fields

We’ve added new formatting options for number fields in company-managed projects. You can now format any number field to show a number, currency symbol, or percentage symbol. This feature enhances the presentation of numerical data and provides an easy way to track information like budgets, estimates, costs, and more.

To try out a number field with currency or percentage formatting:

1. From Jira admin settings, select Fields.
2. Select Create new field, or select More actions (•••) and then Edit field next to an existing number field.
3. In the Format section, select either Currency or Percentage.
4. If you selected Currency as the format, you can then select a Currency type (for example, USD or AUD).

Archive a work item in any plan

Regardless of the plan you’re on, you can now archive work items that you no longer need.

And if it turns out you do need that work item, you can reverse the archival.

Available for Free, Standard, Premium, and Enterprise plans.

You can archive a work item directly from the work item or from the Board or List view. Go to More actions (…), then select Archive.

An admin might need to grant the Archive work items permission.

In company-managed projects:

1. Navigate to your Project settings, then select Permissions.
2. In the top right, select Actions.
3. Select Edit permissions.
4. Find Archive work items, then Update.
5. Select which roles you'd like to grant archive work item permissions to, then select Update.

In team-managed projects:

1. Navigate to your Project settings, then select Access.
2. Select Manage roles.
3. To create a new role with archive work items permissions:
   • Select Create role
   • Tick Archive work items, and any other applicable permissions
   • Fill in the remaining fields, then select Create.
4. Or, add the permission to an existing custom role:
   • Select the custom role.
   • Tick Archive work item, and any other applicable permissions.
   • Select Update.

We're making it easier to find Confluence in Jira

If you've been given access to Confluence, you'll see a spotlight highlighting how you can navigate to the in-Jira version of Confluence, called Project Pages. This way, you'll be able to find and create documentation right in Jira.

Add people to a project when you invite them to Jira

You can now add people to a specific project when you invite them to join Jira. This means you can land your teammates in the right place as soon as they join Jira, and they can get started without needing to track down a specific project first. 

To add someone to a project:

1. Select Teams from the sidebar to open the Teams app.
2. Select People.
3. Select Add people. 

You can also hover over Teams in the sidebar, select Add , then select Invite people.

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

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.

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.

Create Confluence whiteboards directly from your Jira backlog

With Confluence whiteboards, you can plan freely and execute quickly. Create a whiteboard directly from your Jira backlog, copy backlog issues to the whiteboard, and plan however you want.

Here are some suggestions for things you can do with Confluence whiteboards:

• Use award-winning templates such as a prioritizing and planning matrix
• Import Jira issues directly into your new planning whiteboard
• Link sticky notes and issues to show dependencies and timelines
• Turn sticky notes into Jira issues
• Engage teammates with real-time, group editing
• Collaborate using stamps, timers, and more

If an admin has three or more issues in their backlog, they'll see the button that allows them to add Confluence and start using a whiteboard. Once a team has Confluence, anyone with access to Confluence — including admins and end users — will see the button on their backlog that allows them to create a whiteboard.

You can remove this button anytime by turning off all product recommendations at in your Jira settings. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Development feature for software projects in Jira is now generally available

Update: General availability rollout is paused

We're pausing the general availability of Development in Jira and returning it to beta for further improvements. The beta feature remains available on limited sites. If it's already enabled for your site, you can continue using it as outlined below. We'll share updates as we work toward general availability. Thank you for your understanding and feedback.

Development in Jira is available for software projects. It unifies data from your connected code, CI/CD, and security apps into a single view, giving you clear visibility into your team's work and engineering health. With key software development metrics and proactive work suggestions, you can quickly spot and address delivery bottlenecks, helping your team stay productive and deliver software faster.

All software projects have Development enabled by default. Jira project admins can enable or disable the Development feature by going to Project settings, then to the Features page, and using the toggle next to Development. Alternatively, project admins can add Development to the project’s navigation by selecting Add to navigation (+) and then selecting Development.

When enabled, everyone with project access can go to Development from their software project’s navigation.

New navigation: A faster way to find work

Key parts of the top navigation have moved to the sidebar, aligning Jira with other software tools you use daily. The new navigation is centred on customization capabilities and ease-of-use improvements, featuring:

• A customizable sidebar you can personalize to the unique way you work

• Expand or collapse sidebar options to maximize screen space when needed

• A horizontal project navigation admins can customize to each project

Find out more about the new navigation

Improved performance and reliability for CSV exports

If you need to export your Jira issues, you’ll notice a faster and smoother experience due to the following improvements:

• Speed and reliability — the export process is faster and can handle a large number of fields and extensive data sets
• Tracking and control — you can monitor the progress of your export, and cancel if needed

To try it out, go to the Issues page in your project. Select Export, then select a CSV export option.

Note that only one CSV export can be processed at a time.

Speed up your next Jira import with configuration files

When importing multiple projects using CSV files, a configuration file can help you save your preferences, such as project settings, Jira fields, and user information, and use it for future imports. In the new import experience, select Download a configuration file at the end of your next Jira project import. Upload it with a CSV file in another import to bring in the same preferences without the hassle of selecting the same fields once again.

To use a configuration file during an import:

1. From the navigation bar, select Projects > Create project > Import data.
2. Select the app from which you’d like to import your data from. If you can’t find your app in the list, select CSV to use any CSV file to import your data.
   • If you select Asana, ClickUp, monday, or Trello, you can directly import data without a CSV file.
3. Select Upload a configuration file (optional) and upload the configuration file you downloaded from a previous import.
4. Select Next and continue with the import.

Read about configuration files

Enhancements to work item hierarchies in the issue navigator

We've introduced the ability to view work item hierarchies, providing a clear and concise overview of related tasks at a glance. Additionally, you can now easily add work items directly from the list.

This update improves clarity, structure, and scalability. It allows you and your teams to efficiently manage tasks in both team-managed and company-managed projects.

Prefer a flat list view?

If you prefer working with a flat list of work items, you can easily customise your view.

Go to View settings and select Hierarchy

Insight settings are being removed from software projects

As part of our ongoing effort to simplify project settings for admins, we're removing the option to configure insight settings in Jira software projects. Insights will continue to show as normal, but board admins and project admins won't be able to enable or disable specific insights, and any insights that were previously disabled will now be enabled. This means that all insights available in a project will be visible to any user who selects Insights from the board or backlog.

To send us feedback about this change:

1. In your Jira software project, select Board or Backlog.
2. Select Insights.
3. Scroll to the bottom of your Insights and select Give feedback.

Updates to creating linked issues for business projects

We’ve made some changes to the way you create linked issues in business projects.

Group by fields in the All work tab

We're introducing grouping in the All work tab. You can now view work items grouped by Status, Assignee, Priority, Sprint, Story Point, Story Point Estimate, and Category.

To group work items in the All work tab:

1. Make sure you are in the list view in All work.
2. Select the Group button.
3. Choose one field that you’d like to group your list by.
4. Your list will then be grouped by your selection and will only be visible to you.

Beta: Link similar work items using Atlassian Intelligence

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

Use AI to surface and link work items that are similar to yours. Linking similar work items that have been worked on in the past can help you understand the complexity of planning and be a great resource for referring to prior art when coding.

To find and link similar work items using AI:

1. Open your work item.
2. Select Improve work item in the issue details section.
3. Select Link similar work items.
4. Select Link next to each work item to link them one by one, or select Link all to link all at once.

The work items are linked with a ‘relates to’ link type.

Map data to Jira issue types to organize your project better

In the new import experience, we're adding a capability for administrators to set up[ issue types|https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/] and hierarchies. This can help you categorize and organize your team’s work by either assigning Jira issue types (epic, task, story, bug, and/or subtask) or creating custom issue types before importing.

When importing data, map column headers from your CSV file to issue type, issue ID, and parent fields. In the next screen (Map values to issue types), you can map the values within the selected issue type column to Jira issue types or create custom issue types. More about mapping data to Jira issue types

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Automatically clone an issue when it’s done

You can now set an issue to automatically clone once its status has been updated to anything defined as “Done” in your project’s status categories. No need to create the same issue over and over for the tasks you regularly need!

Clone issues will automatically inherit all the same fields as the issues they were cloned from - except for attachments, start dates, due dates, links, and child issues. They’ll even inherit the “Clone when issue is done” automation rule, so you can keep the fun going.

Read more about automatically cloning issues

To clone an issue automatically:

1. Open a Jira issue and select Actions.
2. Select the toggle next to Clone when issue is done to switch the automation on or off.

Prevent people from downloading attached files

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

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. We found that organizations that needed to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policy currently block exports:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Summary view now available in software projects

Project summaries are now available across all Jira Cloud software projects! The _s_ummary view helps you monitor your project's progress by giving you a high-level overview of your team’s work. It includes a snapshot of your project's status, recent activity, priorities, team workload distribution, and epic progress.

All Jira software projects have the summary view enabled by default. To view a project summary, navigate to your project, and then select Summary.

Read more about the summary view

Manage work types when creating issues in team-managed projects

To help keep your work types updated as your needs change, we’ve added the ability to manage work types when creating issues in team-managed software and business projects.

When creating an issue from the top navigation bar, admins can now create and edit work types, or navigate to the work type settings page for more options.

You must be a project admin to be able to add and edit work types when creating issues.

To create work types when creating issues:

1. Go to your team-managed project.
2. Select Create, then Work type.
3. Select Create work type.
4. Add a name, description and icon for the new work type, and select Submit.

To edit work types when creating new issues:

1. Go to your team-managed project.
2. Select Create, then Work type.
3. Select Edit work type.
4. Update the name and/or description of the work type, and select Submit.

To manage work types when creating new issues:

1. Go to your team-managed project.
2. Select Create, then Work type.
3. Select Manage.
4. You will be redirected to the work type settings page.

Introducing a brand new way to complete bulk actions in the issue navigator

We’re introducing a toolbar in the issue navigator so users can update multiple issues even more seamlessly.

To use the new toolbar:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. Use the issue checkboxes.
   2. Hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. You can either select Edit fields to make edits to fields in your issues or Change status to transition your issues.

Software projects: Improvements to start and due date fields for scheduling work in the calendar

Use the issue view to quickly schedule work in your calendar. An issue's start and due date fields dictate how work is scheduled, so we've made the following improvements:

• For new software projects: Start and due date fields are now enabled by default so you can quickly schedule issues without configuring the fields beforehand.

• For existing software projects (if fields aren’t already enabled): Admins will notice additional information in the issue view to Enable date fields. Depending on your project type, admins will see the option to Configure fields (in company-managed projects) or Enable (in team-managed projects). Selecting Configure fields will take you to the issue layout settings page, where you can add fields to issue types. Selecting Enable will add the fields straight away.

To get started with this change, open an issue in your software project’s calendar or timeline view.

How to schedule work in the calendar

The 'External Assets Platform' Custom Field is shutting down

The ‘External Assets Platform’ is shutting down as part of our ongoing efforts to deliver the most streamlined and integrated service management solution. Learn more about the shutdown of the 'External Assets Platform'.

If you’re a customer currently using the ‘External Assets Platform’ to add context to your Jira issues, we recommend you consider adopting Assets in Jira Service Management, available to Premium and Enterprise customers. Assets allows you to use the Assets objects custom field to display your objects on Jira tickets, and gives you the ability to display your Assets data within Confluence, along with many other features.

Jira: Grant permissions to manage versions (releases) in one project only

You can now assign a dedicated Manage Versions permission in Jira and Jira Service Management projects without giving full project admin access. Users with this permission can create, release, archive, merge, edit or delete versions within a specific project only. This applies to company-managed projects in Jira and Jira Service Management, and team-managed projects in Jira only.

Jira automatically grants this permission to users with project admin permissions.

To grant the Manage versions (releases) permission in a company-managed project:

1. Go to a project’s settings then select Permissions.
2. Using the Actions menu, select Edit permissions.
3. Under Project permissions, look for Manage versions (releases). Add the roles, groups, or people you’d like.
4. Select Update to save your changes.

To grant the Manage versions (releases) permission in a team-managed project:

1. for tea,-managed projects, select Access then Manage roles.
2. Select Create role, then find Manage project name versions (releases).
3. Add the roles, groups, or people you’d like.
4. Select Update to save your changes.

Introducing a brand way to delete multiple issues in the issue navigator

We’re introducing an easier way for users to delete multiple issues from their projects.

To delete multiple issues from the issue navigator:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. Select Delete to delete the selected issues.

The end is near for Epic Link and Parent Link fields

For a little over a year, we've been working to combine the Epic Link and Parent link fields in company-managed projects into the new universal Parent field (which you can read about here). To prevent data loss, the values from both fields have been automatically ported into the Parent field.

With this change, the values in the Epic Link and Parent link fields are no longer visible on the Issue view. If your issue view still includes these fields, simply swap it for the Parent field instead.

Read more in our documentation

It just got easier to keep on top of your unread comments

We’re introducing an unread badge in the Comments column in the list view to help you easily identify work items with unread comments. This allows you to stay on top of important discussion and collaborate with your team.

To make sure you get to try this feature, we’ll be automatically adding the Comments column to all list views.

Join the conversation and give us early feedback

Create unique, customizable pages in your help centers

Jira Service Management Premium and Enterprise users can create and design landing pages in their help centers.

Admins can use landing pages to curate and efficiently organize help resources for specific subjects or audiences in a visually appealing manner. These stand-alone pages have customizable layouts to which admins can add rich content, images, videos, links, and more.

To create a landing page:

1. Go to the help center of your choice.
2. Select your avatar, and from the dropdown, select Landing pages.
3. Select Create page.
4. Give your page a name and description and select Create.

Read more about creating, customizing and managing landing pages.

More historical data available in velocity charts

Velocity charts in Jira now show data from more sprints, giving you a clearer picture of your team's productivity over a longer period of time. We've also added an average line so you can easily track your team's average output at a glance. Read more about the velocity chart

To view the velocity chart:

1. Start in your Jira software project.
2. Select Reports.
3. Select Velocity report if you're in a team-managed project, or Velocity chart in a company-managed project.

See all your Asset attributes now in Forms

Take the guesswork out of selecting the right Asset when filling out a form and find all attributes now visible on Asset form fields. Previously when filling out a form, customers would only be able to see the object name which made it hard to know what option to select. Now you’ll see the same attributes listed alongside each object - just like you do on request types.

Add and remove fields from field configurations; new tools to optimize fields in your projects

We’re introducing a number of improvements to the way field configurations and field configuration schemes work. In addition, we’re also adding some new tools which make it easier to remove unused work types and fields from schemes. Here are more details about what’s changing.

You can now remove and add fields to field configurations

Removing a field from a field configuration is similar to hiding it. However, when a field is removed, its configuration isn’t preserved. It will need to be entered again if the field is re-associated.

Adding a field to a field configuration is similar to unhiding it. Once unhidden, it becomes available to the projects associated with the field configuration scheme.

You can manage field associations in the Jira admin panel or using the new field association REST API.

We’re releasing tools which allow you to optimize fields

These tools will automatically identify and remove unused work types from a scheme, as well as unused fields from a field configuration scheme and field configuration. For more details about these tools, see this Atlassian community announcement or type: entry-hyperlink id: 5m0df9oFEgswh305bKEQ1v

Unlocking another level of help center customization

The Jira Service Management help center is getting a sleek and modern design update across all its pages, offering new opportunities for customization. Admins will be able customize the help center navigation and manage background and text color for sections in their home page.

To customize the navigation:
1. Go to the help center of your choice.
2. Select Customize, then Customize look and feel from the navigation.
3. Scroll down the side panel to find the navigation color settings.

To manage section settings:
1. Go to the help center of your choice.
2. Select Customize, then Edit page layout from the navigation.
3. Select the section you want to customize and manage its settings on the side panel.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

Public access is now available for Jira forms

We are adding a Public access option to the forms available in Jira business and software projects. Any user, including those without a Jira license, will be able to submit a response through a public form.

Only people with project admin permissions will be able to create a public form, and these will be available for all licence editions and both team-managed and company-managed projects. In addition, Jira admins will be able to disable public forms on their site. There is one setting for team-managed projects and one for company-managed.

An unlicensed user can submit a response through a public form, but they will need a Jira license to view and collaborate on the work item created from their submission.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

We've launched a new prioritization project template

When you set up a new project in Jira, you can use project templates. There are many to choose from, including specific templates from different apps like Jira Product Discovery and Jira Service Management.

We've just added a new template for projects that are all about gathering ideas and prioritizing them. With this new prioritization template you can list ideas and add data to them. You can then use this data with common frameworks (such as RICE) to prioritize. The project has multiple views, like an effort and impact matrix, list, or roadmap view, so you can see and share your priorities in a way that suits you.

Anyone who has Jira Product Discovery and permission to create projects can use this template.

See the Premium features in-product before starting a trial

We're introducing a new and faster way to understand and upgrade to Jira Service Management Premium trial. Whenever you choose to upgrade to Premium or start a trial, you will see a modal which lists all new features available to you.

Now you can create roadmaps from your Jira timeline

Sometimes, you need a custom roadmap view to share your work plans with certain stakeholders. You may not need to include specific dates, for example. Now, you can access Jira Product Discovery from the Jira timeline view. Look for a button that says "Create roadmap" when you select the "Share", " Today," or "Timeline mode" buttons.

You can use Jira Product Discovery to create custom roadmaps, then share them with anyone, even if they don't use Jira.

Only people who are admins and don't already have Jira Product Discovery will see this change. You dismiss it anytime.

Plans in Jira - More Program boards per plan!

In Plans, you can now have up to ten active Program boards at one time in a plan. A Program board is considered 'active' if it has an end date in the future.

Previously, you could only have two.

Project delete improvements

We’re making the project deletion process easier to follow. When a project is moved to trash and marked for deletion, you have a 60 day window in which to restore a project. After that, the project will be permanently deleted.

With this change, if you don’t require the 60 day grace period, you can select 'Delete now' from the project trash list menu. A ‘Deleting now’ message confirms the project deletion process is underway.

Jira: Reparent work items in list view

You can now select (drag and drop) work items to reparent them. This makes it easier to restructure work without losing your place.

To reparent a work item:

1. Make sure you're in the list view within your project
2. Select (using drag and drop) the work item you want to reparent.
3. Move it to the new location (drop it). This will update the hierarchy.

We're making it easier to compare plans during a trial

When you're in a trial, you can now click on the trial button in the top navigation and see the plan options available to you. This way, it'll be easier for you to understand the plan that is best for your team based on the features that plan includes. You can also easily upgrade and pay from the plans page.

Edit your workflows quicker and easier with the power of AI!

In Jira sites that have Rovo enabled, the New Workflow Editor now includes an AI Workflow builder agent that can help add, change, or delete statuses and transitions in a workflow. It can also answer questions about the key differences between the old and new workflow editor.

While the agent is still learning, you can prompt it to add or remove the following rules from an existing workflow:

• Restrict who can move a work item
• Update a work item field
• Validate a work item field value
• Change an assignee
• Check a work item field value

Then select Update workflow on the workflow diagram to save the changes it suggests.

Avoid accidentally deleting work items

We’re changing the way Premium and Enterprise users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you can now choose to archive it, or confirm that you want to delete it.

Compact format in the All work tab for team-managed and company-managed projects

Introducing a single row height layout and reduced scrolling, making it easier to scan and manage your work at a glance.

• Go to your project
• Select the All work tab to view the work in a single row height format.

Linking related Confluence content using Atlassian Intelligence is now generally available

We're excited to announce that linking related Confluence content to work items using Atlassian Intelligence (AI) is now generally available.

With AI, you can effortlessly find and link related Confluence content to your work item, so you always have all key information at your fingertips. This allows you to fully understand the work context needed to make progress.

To find and link related Confluence content using AI:

1. Open the work item.
2. Select Improve work item, then Link Confluence content.
3. Select Link for individual links or Link all to link all related Confluence content at once.

Read more about linking Confluence content

Add media from web links

You can now add media, including images and videos, directly from web links into your Jira work items. This is an update to the existing image upload process. Once you select the Add image, video, or file from the toolbar or / command, you can now upload files or media from links.

Watch multiple work items from the backlog and All work tab

Stay updated about the work that matters to you by watching multiple work items in either the backlog or the All work tab. When you watch a work item, you’ll be notified when important changes occur.

To watch or stop watching multiple work items from the backlog or All work tab:

1. Select multiple work items from the backlog or All work tab. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting work items
   3. hold the Shift key to select a group of adjacent work items
2. Select Watch options, then select either:
   1. Start watching to receive updates
   2. Stop watching to stop updates

Create and manage email templates for stakeholder notifications

Jira Service Management Premium and Enterprise users can now save time and customize stakeholder notifications on the go with email templates.

Email templates provide an easy and efficient way to customize stakeholder notifications. They eliminate the need to draft new emails from scratch, especially when teams are responding to incidents, allowing for quick customization and notification. Templates ensure consistent messaging by structuring emails to include all necessary information. You can also use predefined placeholders and dynamic fields, which help minimize the likelihood of omitting critical details.

To create an email template:

1. Go to Settings, then Products.
2. Under Jira Service Management, select Incident management.
3. Go to Email templates.
4. Select Create template.
5. Type in name, sender and reply address, upload header image, if any, and type in the email body.
6. Select Save template.

Find out more about creating and managing email templates.

A cleaner All activity tab in work items

We’ve updated the All tab in the activity section of each work item. This improves readability and reduces clutter.

It's easier to scan and understand updates in a work item’s history, at a glance:

• Entry grouping: Similar updates are now grouped together to reduce clutter.

• Modern UI: Improved alignment, formatting, and date presentation for a cleaner look.

• Progressive disclosure: Long descriptions and details are now collapsible, reducing excessive scrolling.

This more structured and intuitive layout helps you quickly access relevant updates without the overwhelming detail.

Jira Plans - Turn releases off and on in your plan

Releases are a powerful tool for planning work for software teams, but for Marketing or Design teams? Not so much. For planners who don't need to see releases information from their plans, you can now hide it for a simpler planning experience.

When you turn releases off in your plan, you’ll no longer see:

• the Releases tab
• the Releases field from the timeline as well as any filters that use it
• release markers on the timeline, calendar, and program board
• the option to group work items by assigned releases in the View settings menu
• any rolled up dates based on releases

For a full breakdown of this new feature, read more in our documentation.

Jira: Create work items in a group in list view

You can now create work items directly within a group in the list view. This feature automatically adds the group field (such as assignee) to the new work item, streamlining your workflow.

To create a work item in a group:

1. Go to the list view in your project.
2. Select the group where you want to create the work item.
3. Select Create to add a new work item, which will automatically include the group field.

Jira: Improvements to the child work item panel

The child work item panel is faster to load and more responsive.
You now get smoother scrolling, better performance and real-time, instant updates (without needing to refresh).

Performance and reliability improvements for Assets in Jira Service Management

As announced last year, we’re rolling out several changes to the Assets platform in Jira Service Management designed to improve the system's overall performance and reliability. This includes adding new limits and removing support for several AQL operators, functions, and endpoints. See the following Changelogs for more details:

https://developer.atlassian.com/changelog/#CHANGE-1739

https://developer.atlassian.com/changelog/#CHANGE-1915

https://developer.atlassian.com/changelog/#CHANGE-1905

https://developer.atlassian.com/changelog/#CHANGE-1906

https://developer.atlassian.com/changelog/#CHANGE-2198

Jira: Introducing an improvement to attachment previews

Introducing Grid view for attachments.

This change improves the organization and visualization of attachments.

Attachments appear in a grid view rather than the strip view and list view. You'll still be able to switch to another view, and save that as the default if you prefer.

Grid view helps you to more easily navigate through your content.

Customize project backgrounds with images and color gradients.

Jira admins can add different colors and images to project backgrounds.

Available in both team-managed and company-managed projects

To change the background you must be a Jira project admin using the new navigation.

To set a theme in a company-managed project:

1. Go to a board in a company-managed project
2. Hover on the project name on the left sidebar
3. Select (…) More actions
4. Select Set project background
5. Choose a theme

 To set a theme in a team-managed project, you can either follow the same steps as a company-managed project or:

1. Go to a team-managed project
2. Select (…) More actions next to the project name
3. Select Set project background
4. Choose a them

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

Limits to work type schemes and field configurations are coming in 2026

We recently announced that Jira will limit the number of work types that can be used in a project to improve performance and reliability of large sites starting in February 2026. Work type schemes will be capped at 150 work types per scheme, and field configurations will be capped at 700 fields.

In our recent post in the Atlassian Community, we cover what tools are available to help you clean up your sites in preparation for this change.

Subscribe to your change calendar and explore the new filters

We’ve made major improvements to the change calendar to help you stay on top of change events and avoid conflicts across your services, Assets objects, and teams.

Subscribe to change calendar from your external calendar
You can now generate an iCal link and subscribe to your change calendar from apps like Google Calendar, Apple Calendar, and Outlook. This lets you stay updated on change activity without logging into Jira Service Management.

New JQL filtering in change calendar
Use JQL to filter work items shown in the calendar view. Filter by affected services, affected Assets objects, change types, or any custom fields, so you can focus on exactly what matters.

Show or hide change events by type
Choose which types of change events to display on the calendar, including freeze windows, maintenance windows, and standard work items.

Link your change calendar with affected services and Assets objects
You can now select affected services and Assets object fields when creating a new change window. This helps surface change conflicts more clearly and ensures better risk insights for service-dependent work. Read how to connect Assets schemas with changes

Generate a subscription link directly from your change calendar following these steps:

• Navigate to Operations > Change calendar in your service project.
• Select Subscribe to change calendar icon in your toolbar.
• Choose the event types and calendar format, then generate your calendar link.
• Paste the link into your external calendar app (Google, Apple, or Outlook). Read more about subscribing to change calendar

Once subscribed, you’ll automatically see any future updates to change events in your external calendar.

You don’t need to take any action to start using the new filters or event fields. They’re already available in the change calendar and the change event creation form.

Jira Plans: Navigation and accessibility improvements on the Dependencies view

We've added extra keyboard navigation and accessibility features on the Dependencies view in Plans. With this release, you can now:

• use your mouse or trackpad's scroll function to either pan across the view or zoom in or out. You can switch between these using the Zoom on scroll checkbox in the view menu where you usually select the zoom level.
• quickly view linked work items using Highlight linked work item in a card's ••• menu
• go to different sections of your dependencies view using the Skip to menu

All of these improvements are accessible via keyboard actions.

Additional fields now editable in the All work list view

You can now edit Confluence items and linked Goals from the All work list view.

Confluence items and comment summaries are also now included when exporting work items to CSV or HTML.

• In the All work tab, view work items in list view.
• Select Configure columns in the column bar to add the Confluence items or Goals fields to the list view.
• They can now be edited directly in the list.

New 'offer options' standard flow in the virtual service agent

We heard your feedback about the escalate standard flow creating too many work items, so we've introduced a new standard flow, called offer options. Depending on the situation and the channel, offer options is sometimes used instead of escalate.

Offer options is configurable, and lets you choose 1–3 options to present to your customers. These appear as buttons:

• Raise a request starts the escalate standard flow, which lets the customer know a request has been raised and creates a work item.
• See search results takes the customer to the relevant portal, and shows search results based on their first message in the conversation.
• Ask another way tells your customer to try rephrasing their question.

Read more about the 'offer options' standard flow, or find out how to configure 'offer options' in the virtual service agent.

Refined drag and drop experience in the work item

We’re refining the drag and drop experience in the work item to make it more consistent and intuitive across different views in Jira.

We’re running an experiment with two variations.

Search all apps from Jira

You can now use the "All" tab and a new "Search all apps" option in Jira quick search. This update makes it easier to find content from multiple Atlassian apps in one place.

1. Open Jira and select the search bar at the top of your screen.
2. Find and select the new "All" tab in the search dropdown.
3. Use the "Search all apps" option to expand your search beyond Jira.

Link your team to Jira projects and Confluences spaces

You can now associate teams with projects in Jira and spaces in Confluence, making it easier to find the teams who work in any given project or space. You'll see linked teams at the top of the Jira project page and a Confluence space's main page, as well as connected projects and spaces on a team's profile.

You can link your team to a Jira project or Confluence space from the "Team links" section at the top of the team profile. You can also link a team from the Jira project or Confluence space themselves:

1. Go to the Jira project or Confluence space's main page that you want to link.
2. At the top of the page, select the team icon next to the project or space's name.
3. Enter your team name(s) in the search field and select the team(s) you want to link.

New plans background save process

No more waiting around for plan changes to save.

Now, you can keep working in your plan while changes save in the background. If there's any errors or incomplete fields, we'll prompt you to reopen the unsaved changes modal and resolve the problem.

Jira Plans - Sprint capacity calculations now includes completed sprints

Completed sprints are now included in capacity calculations on the timeline and program board in Plans. This ensures a more accurate reflection of the team's velocity.

How to view capacity in your plan

Reorder starred projects in the sidebar navigation using drag and drop

You can now reorder the starred projects in your sidebar navigation to more easily organize your projects according to your preferences.

Here's one way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Hover over the starred project you want to move.
3. Drag the project to your desired position.
4. Drop it to set the new order.

Here's another way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Select the More actions for the starred project you want to move, then select Move in sidebar.
3. Select where you'd like to move it in the order.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Create and reorder work items faster in the All work tab

We’re rolling out sibling create and drag and drop re-ranking in the All work tab, so it’s easier to structure and prioritise related work items without switching views.

You can now quickly create a new work item at the same level (a sibling), and re-rank work items by using drag and drop (select and move) when sorted by rank.

Now available for both team-managed and company-managed projects in the All work tab.

Key benefits:

• Plan faster by creating structured work items in context.
• Prioritise quickly with drag and drop (select and move) ranking.
• Avoid unnecessary actions and switching views.

1. Go to the All work tab.
2. Check that your view is sorted by Rank.
   1. Select a work item, then drag and drop (move) to reorder based on priority.
   2. Select a work item, then + Sibling to create a related work item.

Jira: Collapsible sections in work items

You can now collapse sections in a work item view to reduce scrolling and highlight key information.

To use collapsible sections:

1. Open a work item in Jira.
2. Find the section you want to collapse, such as Description or Activity.
3. Select the chevron or section title to collapse or expand it.

Due date notifications now available

As the assignee of work items that are overdue or due today, you'll now receive daily notifications within Jira and via email. Each notification links to a pre-filtered page showing your overdue and due work items. Manage your due date notification preferences by:

1. Select your profile image at the top-right navigation.

2. Select Notifications, then you can manage how you receive notifications for overdue work items.

For more details, join the conversation and provide feedback on our Atlassian Community.

Create custom roadmaps directly from your project menu

Jira Product Discovery is an Atlassian app that allows people to create custom roadmaps. You can add or edit information such as dates, assignees, and more.

You may now see a recommendation in your project menu about Jira Product Discovery roadmaps. You can select this recommendation, add Jira Product Discovery, and create a new project with a custom roadmap template.

Only admins will see this recommendation. It is being rolled out to people on Free Jira plans first, then it will roll out to Standard and Premium Jira plans in the next few months. You can dismiss it at any time or go to admin.atlassian.com to manage your recommendation settings.

Parent Key is now included in CSV exports of work items

When exporting work items into a CSV file, the Parent work item key is included alongside Parent ID and Parent Summary.

Jira: Consolidated actions in the work item view

In Jira’s work item view, we’ve moved the Vote and Feedback actions into the More actions (•••) menu. Previously, these actions were available outside of the menu. This change simplifies the work item view and makes it easier to focus on key actions.

To see this change, navigate to your Jira project. Select a work item to open the work item view, then select More actions (•••).

Jira: A wide view for work items

Reduce visual clutter and surface essential details only by switching your work item to the wide view layout.

To switch your layout:

1. Open a work item in Jira.
2. Select Switch layout.
3. Choose Wide view.

Jira: AI-powered related Confluence content suggestions are now proactive

Jira now uses AI to automatically suggest relevant Confluence content to link to your work items. When you link existing Confluence content to a work item, Jira proactively surfaces related content from your site’s Confluence while respecting access permissions. You can review the content results and link them to the work item so your team always has all the key information needed to fully understand the work context and make progress.

To get started:

1. Open a work item.
2. Select + Add.
3. Select Existing Confluence page. We’ll show you a list of related Confluence content in the Confluence content section.
4. In the Link related Confluence content panel, select Show results to expand the results.
5. Select Link to add content items individually, or Link all to add them all at once.

Plans - Plan Settings refresh

We've redesigned the Plans settings pages to be easier to use and prettier to look at. There's no new functionality with this release.

This improvement focuses on rewriting settings for clarity and framing your plan configuration in a more useful way. The notes below outline what's changed.

More custom project template editable settings are here for workflows and issue layouts

We’re excited to announce we’re supercharging company-managed custom project templates for Enterprise users.

More flexible controls means less need for admin support.

Jira admins can clone selected source project settings and empower end-users with the new CMP permissions to Manage Issue layouts and Edit workflows within projects created using custom templates.

To allow these settings, go to the source project and select More actions (•••) then Edit template. From the template name and description screen select Next.

Select the project settings you wish to clone and make editable for template users with required permissions and select Save.

The custom project template will appear to everyone you’ve allowed within the list of project templates available when they select Create project.

Improved object view in the Assets object graph

We're thrilled to announce a major update to the Assets object graph, designed to streamline your workflow and enhance your user experience. This update brings a host of new features and improvements that make managing your object data more intuitive and efficient.

Team-managed projects: Currency and percentage formatting now available on number fields

We’ve added new formatting options for number fields in team-managed projects. You can now format any number field to show a number, currency symbol, or percentage symbol. This feature enhances the presentation of numerical data and provides an easy way to track information like budgets, estimates, costs, and more.

You must be an admin to edit fields.

To try out a number field with currency or percentage formatting:

1. Start in a team-managed project.
2. Next to your project's name in the sidebar, select More actions (•••), then Project settings.
3. Select Fields.
4. Find the number field you’d like to configure, select Actions (•••), then Edit field.
5. In the Format section, select either Currency or Percentage.
6. If you selected Currency as the format, you can then select a Currency type (for example, USD or AUD).

Improve visual and hierarchy of the Quick actions menu in the work item

We’ve improved the Quick actions menu in the work item with a cohesive visual look, and better action hierarchy and grouping, making it easier for you to find and use the tools you need.

We’ve also added Goals and recommendations to the menu.

Open a work item and select the Add button under the summary.

Inline editing now available on boards in company-managed software projects

You can now directly edit the summary, parent, and estimate fields on boards in company-managed software projects. This reduces the need for multiple clicks and navigation steps, allowing you to update work items more efficiently.

To edit fields directly on the board:

1. Navigate to a board in a company-managed software project.
2. Select the field you want to edit, such as a summary, parent, or estimate.
3. Make your changes and select Enter, or click away to save your changes.

Import workflow from Marketplace feature has been deprecated

With this release, users will no longer be able to import workflows hosted in marketplace apps.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

Jira: Create work items inline in the Backlog with AI (beta)

You can now use AI to generate multiple work items directly inline in the Backlog, based on content from a Confluence link.

AI analyzes the linked Confluence page and suggests relevant work items for you to review and create—all without switching context. It supports cross-site linking and respects your existing access permissions to Confluence content.

AI-powered work creation helps you save time, reduce manual effort, and streamline backlog management by quickly turning documentation into actionable tasks.

To get started:

1. Go to the Backlog in your Jira project.
2. In the inline create field, select Generate from Confluence.
3. Search or paste a Confluence link, then select Suggest work items.
4. Review the suggestions. Then, accept them individually or all at once to create work items.

Improvements to the Fields pages in Jira Admin - Part 1

We're rolling out the first phase of our improved fields management experience in Jira that we announced in the Atlassian Community at the start of June. Our post outlines the full list of changes as well as how this fits into our larger plan. The Atlassian Community is also where we'll share updates, announce future changes in full detail, and engage with the community to make sure we're delivering an experience that meets your needs.

This first release includes changes that make field management simpler and more efficient for Jira admins, such as a redesigned Fields page (formerly Custom fields) that now shows fields created by Jira or plugins (i.e., System fields). You can also create and add new fields to configuration schemes without leaving the page, and filter and sort fields based on Field category type.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

New ways to associate a field to a field configuration scheme in Jira Admin

When this feature rolls out, admins will be able to:

• associate a new field to all of the field configurations used by a scheme without leaving the page, and
• view and edit which field configurations that field is a part of via the More actions (•••) menu on the Fields page

This work is part of our ongoing efforts to improve Fields management in Jira.

Attachments now supported for the 'Send customized email’ action in Automation

We’ve introduced the ability to add attachments to emails sent as part of your automation rules.

Once a rule has been saved or enabled, you’ll be able to upload files as part of the email content. When the rule executes, any uploaded files will be included as attachments to the emails that are sent.

This capability will be available when using the Send customized email action as part of your Jira automation rules, and will become available for use in other Atlassian apps in the future.

Read more about the Send customized email[ action in Automation.|https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-customized-email]

This highly-requested update includes:

• Attachment support: You can now add up to 10 attachments (in most file formats with a total size of 4MB) to your automated emails.
• Secure storage: All attachments are stored securely in Atlassian’s media platform, ensuring reliability and compliance.
• Easy preview: Once uploaded, you can open a preview of an attachment by selecting a card in the Attachments field.

To add attachments to your automated emails:

• Add the Send customized email action to an automation rule, then fill in the email details in the Settings tab.
• Select the Content tab, then from the Attachments field browse or drop the files you want to attach to the email.
• Select Update.

Note that the rule must be saved or enabled before you can add attachments to the email action.

Display work items from the All work tab as a Smart Link

You can now paste a link from the All work tab into the editor on Confluence pages, work item descriptions, or comments as a Smart Link. You can select from four different views to show the right context for your team, and update work items directly from within the editor.

To display your team’s work as a Smart Link:

1. Select the All work tab in your project.
2. Select the URL in your browser and copy the link.
3. Paste the link into a Confluence page, work item description, or comment.
4. Select your preferred view: URL, inline, card, or embed.

Read more about Smart Links in Jira

More functionality in the new workflow editor, plus it's becoming the default experience

This release has two small improvements which means the New workflow editor can do everything that the old workflow editor could do. These changes are:

• You can set a name for your transitions when you create them, and rename existing transitions.
• When you change the name of a status that's included in a transition, the transition automatically updates to match the new name.

And with those changes, the New Workflow Editor is a worthy successor to the old one, and we're excited for it to become the new face of workflow changes in Jira.

That said, Jira will use the new workflow editor by default when editing global workflows unless you've set the old editor as your default in settings. If you set the old as your default workflow editing experience, then nothing will change for you, but we are planning to deprecate it soon.

For now, enjoy the vastly superior new workflow editor. Let us know what you think by sending us feedback through Jira.

Prompt inactive Confluence users to create content from work items

We're introducing a feature that encourages inactive Confluence users to create content directly from Jira work items. This feature targets users who haven't been active in Confluence for the past 28 days and belong to sites that have had Confluence for more than 14 days. When these users view certain Jira work items, they'll see a suggestion to create a relevant project document in Confluence.

To start using this feature:

1. Open a Jira issue of type epic, story, or bug.
2. Look for the Confluence content section.
3. Select the suggested template to create a project document in Confluence.
4. Follow the prompts to complete and publish your document.

Avoid accidentally deleting work items

We’re changing the way users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you must complete a two-step process to confirm the action.

To delete a work item:

1. Select the work item you want to delete.
2. Select More actions (•••), then select Delete.
3. To go ahead with deleting the work item, type “delete” in the text box.
4. Select Delete (this option will only be available after you type “delete” in the text box).

We're deleting unused field associations

Starting today (June 16, 2025), we’re beginning the process of removing unused field associations from your field configuration schemes. We expect this process to take several weeks from today. Once finished, this will improve the performance and stability of your Jira instances.

If this causes any issues in your projects, we have documented the steps for adding fields back in this Atlassian community announcement. The page also covers how we determine which associations to delete. If you have any questions about this scheduled deletion, you can ask them in the comments section of the linked announcement.

Selecting dates in Jira is now easier

We’ve made improvements to the way you select dates and times in Jira, making it more efficient to schedule work and keep your team on track.

Key changes:

• Smart defaults: The placeholder date has been updated to the current day’s date and time.
• Keyboard navigation support: You can now press "tab" or "enter" to confirm a selection.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Allow Slack apps to trigger on-call alias responses

You can now allow Slack apps, workflows, or webhooks to trigger Jira Service Management ChatOps responses using schedule aliases.

Previously, ChatOps only responded to alias messages sent by users. Now, when an app posts a message with an alias, you can allowlist it directly from the message shortcut menu. Once allowlisted, ChatOps will respond just like it does for user messages, making it easier to integrate bots, monitoring tools, and workflows into your on-call process.

To allow an app:
Hover over the alias message sent by the app, select the More actions menu > More message shortcuts > Allowlist app

Easily share and maintain your team-managed project

We’ve improved how project admins share team-managed projects in Jira.

Admins on Standard and Premium Plans can now see the project’s current access level at a glance from the project view. Plus, you can now Copy a link directly from the project view, making it even easier for you to share your current project view with your team.

Read more about access in team-managed projects.

To copy a link for your current project view:

1. Select Copy from the top right of your current project view. This will copy the URL of your current project view to your clipboard.
2. Share the URL with anyone you like!

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Use AI to generate sprint goals

We’ve introduced AI-generated sprint goals so teams can quickly set their focus based on the Summary and Description of the work items in the sprint.

When you start or edit a sprint, you can choose to use the AI-generated content as is or tweak it to suit your needs.

To create an AI-generated sprint goal:

1. Create a new sprint and add work items.
2. When you’re ready, select Start sprint.
3. (Or, edit an existing sprint with work items.)
4. Find the AI-generated sprint goals below the sprint goal field.
5. Select Insert, refine, then Update or Start sprint.

Proactive child work item suggestions powered by AI

Get context-aware child work item suggestions proactively generated by AI.

This feature recommends relevant child work items based on the details of the parent work item, helping you save time, reduce manual effort, and stay organized. When you accept a suggestion, a new child work item is created and linked to the parent work item.

You can also hide the proactive suggestions and manually use AI to generate child work items when it suits you.

Read more about AI features

To get proactive, AI-powered child work item suggestions:

1. Open a work item.
2. Select + Add, then select Subtask. You’ll see a list of suggestions for child work items in the Subtasks section.
3. In the Create suggested child work items panel, select Show results to expand the results.
4. Select Create to add individual work items, or Create all to add them all simultaneously.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

The Edit page action is now available in Jira Automation

We've made the Edit page action available for use in Jira Automation. Previously, you could only use it in Confluence Automation.

The Edit Page action enables your rule to edit and add content to an existing page in Confluence. It can now be used alongside other actions, including those from Rovo AI agents.

Control playbooks visibility using JQL

You can now use JQL in the playbook details section to control playbook visibility. This helps agents see only the most relevant playbooks, improving process efficiency and reducing noise. Read more about playbook details.

Create work items from a Loom with AI

You can now use AI to generate multiple work items directly inline in the Backlog, based on content from a Loom video.

AI analyzes the linked Loom video and suggests relevant work items for you to review and create, without switching context. It supports cross-site linking and respects the permissions you apply to the video.

AI-powered work creation helps you reduce manual effort and fast-track backlog management.

To get started:

1. Go to the Backlog in your Jira project.
2. In the inline create field, select Generate from Loom.
3. Search or paste a Confluence link, then select Suggest work items.
4. Review the suggestions. Then, accept them individually or all at once to create work items in the backlog.

Suggestions of people to tag in comments

When adding a comment in a work item, you will now see suggested people to tag, making it easier to involve the right people in discussions.

Format numbers as currency or percentages in team-managed business projects

We’ve added the currency symbol ($) and percentage symbol (%) to the number custom field to help you track budgets and spending.

Once set up, cards on your business board, fields on your forms, and work items directly, or in the All work tab, will show numbers in the format set by your project admin.

To create a custom number field:

1. If you’re not already there, navigate to your team-managed business project.
   • For cards on your board: Select Project settings, then Work types. Select Add work type from the sidebar, or edit an existing work type.
   • From the All work tab: Select Add column (), then Create another.
   • From a work item: Select Edit fields (⚙️) in the details section.
   • Navigate to the Forms tab.
2. Choose Create a field, then choose Number as the field type.
3. In the Format dropdown, select Percentage or Currency.

We’re removing the default text renderer

To improve consistency, reduce bugs, and provide a better editing experience across all of Jira Cloud, we’ll be removing the default text renderer.

This will:

• Ensure consistent formatting and rendering behavior.
• Eliminate confusion and data loss due to mismatched renderers.
• Provide a unified editing experience across all Atlassian Cloud products.

What’s changing:

• Jira now only supports the wiki text renderer (which allows a user to enter wiki markup to produce HTML content).
• You’ll no longer see the option to configure a default text renderer.
• Any fields currently using the default text renderer will be migrated automatically.

Reply and react directly in comment notifications

You can now reply to comments and add reactions directly from your notifications in Jira and Confluence making it easier to acknowledge discussionsTo reply or react to a comment from a notification: without losing context.

To reply or react to a comment from a notification:

1. Open your notifications at the top-right in Jira or Confluence.
2. Find a comment notification.
3. Reply or react to comments from within the notification hub.

Your reply or reaction will be saved and the notification will update automatically.

Export default fields

We’ve made exporting your data even easier by making improvements to Jira’s CSV export functionality. This streamlines the process of exporting work items by using your preferred settings.

To use your default fields with a saved filter:

1. Select a saved filter in All work view, or select a saved filter under Filters in the sidebar.
2. Select More actions (…) menu at the top-right.
3. Choose Export.
4. Select Export CSV (my defaults) or Export Excel CSV (my defaults).
5. Your exported file will contain only the columns you have set as your "my defaults".

Easier ways to view and edit your sprint commitments

This change makes it easier for you to spot and adjust sprint commitments in your backlog.

Now you can:

• Quickly understand if the sprint is over or undercommitted, with new icons and recommended improvements. The up arrow shows if the sprint is overcommitted, the down arrow shows it's undercommitted, and the tick indicates it’s just right!
• Automatically view the related sprint in the insights panel by selecting the sprint commitment icon in the backlog.
• Turn the sprint commitment icons on or off, as you like, via your View settings (company-managed projects only).

We’re cutting down on messaging for new users

We’re streamlining Jira for new users by reducing the amount of messages displayed in the first few weeks. As a new user, you’ll only see the most helpful tips and tricks, so you can focus on organizing work and collaborating with your team.

Jira forms with public access now support attachments

Attachments are now supported in forms set to public access. This means that when someone submits a response to a public form, they can also upload an attachment, such as an image or video, to add more context. The attachment can then be viewed and accessed via the work item created from the form submission. There is a limit of 100MB per attachment.

Add a comment summary to improve your work item description

To help make sure key decisions or details aren't lost over time, you can use AI to summarize the comments in a work item.

Select Add to description to combine the summarized comments with an improved version of the existing description, or select Copy to add it manually.

Jira: Conditional formatting now available in All Work

You can now apply and edit conditional formatting rules directly within All Work, not just in the list view. This allows for consistent formatting and easier management of your work items.

To apply conditional formatting:

1. Go to the All Work tab in your project.
2. Select (…) More actions then Format rules.
3. Edit or apply rules as needed.

Jira: Changes to More actions in work items

We’re making it easier for you to find what you use the most e.g. Move, Delete, Log work.

We’ve removed actions that aren’t frequently used from More actions. This includes Take a Tour, Add/Change parent, Configure, Find your field, Find out more.

1. Select a work item.
2. Select More actions (•••).
3. Explore the streamlined experience.

The people and teams directory has moved to the Teams app

Previously, "Teams" was a navigation item in both Jira and Confluence that would show the people and teams directory within each respective app. These directories have been moved to[ the Teams app|https://support.atlassian.com/atlassian-account/docs/what-is-the-teams-app/], which you can find in the list of app shortcuts at the bottom of the app sidebar or in the app switcher in the top left corner. Aside from the location and how you access the directory, there are no other changes in how the directory is used.

Hide empty sprints in the backlog

You can now hide empty sprints from the backlog in software projects that use scrum. This helps you focus on sprints with active work and keeps your backlog organized.

To hide empty sprints in your backlog:

1. Select Backlog.
2. Select View settings.
3. Select the toggle next to Empty sprints to hide sprints that don’t contain any work items.
4. Select the toggle again to show empty sprints.

Quickly reorder work in a sprint

Instead of dragging and dropping work within your sprint (aka ranking work), you can now quickly reorder work according to Work type, Work item key, Version, Epic, Status, Estimate, Priority, Assignee, or Summary.

Open the More actions (•••) menu on a sprint in your backlog, then select Reorder work items to change how your work is ranked.

Sync Slack threads with Jira comments

Keep your Jira work items up to date by syncing conversations from Slack directly to Jira comments, or comments to threads.

When you paste a work item link in a Slack channel, select Sync thread to connect the discussion. Replies in Slack will appear as Jira comments, and Jira replies will sync back to Slack, so your team never loses context.

To get started, paste a link to a Jira work item in a public or private Slack channel and follow the steps.

Updated flow for turning off email notifications

We’ve updated the unsubscribe process for notification emails to make it more reliable. When you turn off notifications for a work item, you’ll now see a confirmation page, and the action will only complete once you confirm. This ensures unsubscribes are always intentional and keeps you in control of your notifications.

Data Manager has completed the Open Beta period

Data Manager has completed the Open Beta period

We’re pleased to announce that Data Manager has now completed the Open Beta period and will be available as a standard feature to all users with an Atlassian Cloud Premium or Enterprise instance of Assets.

Data Manager has completed the Open Beta period

Import Data Manager objects directly into a schema in Assets

Create a new import and select “Data Manager import”, then select a Saved Search from a Data Manager object class. Run your import to bring Data Manager objects into a schema in Assets. Learn more about importing objects from Data Manager into a schema in Assets.

We've also made improvements to how we handle fields that contain secured information in Adapters:

Secured fields in Adapters are now both encrypted and masked

After you create or edit a job in Adapters, those fields that contain secured information (such as passwords and API keys) are now both encrypted and masked. When entering information into a secured field, you won’t be able to choose the masking string of twenty asterisks (********************) as a value. Learn more about configuring a flat file, database, API-based, or Powershell-based job.

Note: Data Manager does not currently comply with FedRamp, BYOK encryption, or the requirements of Data Portability as outlined in the Atlassian Privacy Policy. For more information, please see the Atlassian Customer Agreement.

We're making it easier to find Confluence in Jira

If you've been given access to Confluence, you'll see a spotlight highlighting how you can navigate to the in-Jira version of Confluence, called Project Pages. This way, you'll be able to find and create documentation right in Jira.

Use Atlassian Intelligence to draft a reply

You can now use Atlassian Intelligence to draft replies (beta) for your customers. The replies will be based on comments added by agents while resolving similar requests.

To use Atlassian Intelligence to draft a reply:

1. Select any issue from Queues.
2. Select Add internal note or Reply to customer.
3. Select Atlassian Intelligence from the toolbar, and then select Draft Reply. Alternatively, use /draftreply.

You can copy, insert, or edit the reply as needed.

Enhancements to work item hierarchies in the issue navigator

We've introduced the ability to view work item hierarchies, providing a clear and concise overview of related tasks at a glance. Additionally, you can now easily add work items directly from the list.

This update improves clarity, structure, and scalability. It allows you and your teams to efficiently manage tasks in both team-managed and company-managed projects.

Prefer a flat list view?

If you prefer working with a flat list of work items, you can easily customise your view.

Go to View settings and select Hierarchy

Announcing a new way to streamline processes across your projects with Journeys

Build end-to-end journeys that automatically connect work items across both service and software projects in Jira Service Management. Here you’ll be able to get a view of all the work that needs to happen as part of a specific process, and the relationships between the specific teams doing the work.

You’ll also able to control when, where and how these work items get created so you can increase efficiencies by streamlining all the various processes that may cross multiple departments. This could include processes such as employee onboarding or off-boarding that require action from different teams who may not be in the same project.

All you have to do is set a trigger so a journey type knows when to start creating and linking work items across projects. You can also pause the progress of a journey by stopping subsequent work items from being created until a dependency on another work item’s status is met. Plus map Automation rules to specific work items in a journey that may require additional functionality or flexibility.

Read more about journeys

To start using Journeys:

1. From your company-managed service project, select Project settings, then Features.
2. Under Features lab, turn the toggle on next to Journeys to enable this feature.

If you participated in our early access program, this feature will be enabled for you by default.

Automation suggestions in issue and alert views

In the issue and alert views, you’ll now receive automation rule suggestions to help improve your team’s efficiency and simplify the alert management workflow. These suggestions are generated based on keywords found in the issue summary and description, and offer relevant automation options that can be beneficial for your team. By implementing these rules, you can reduce manual tasks, save time, and ensure more consistent management of issues and alerts.

If you are an admin:

• To set up and enable the rule for your team, click Build this rule.
• To modify an existing rule, click Edit in rule builder.
• By default, automation suggestions are visible to everyone. To control who sees these suggestions, go to Project Settings > Features > Automation Suggestions. Turning it off will prevent your team from receiving suggestions.

If you’re an agent:

• You can request your admin to build and enable the suggested rules for you.
• To view details about a suggestion, click View rule.
• To quickly send a request to your admin, click Copy message to copy the message and send it to your admin.

Edit your help center's home page layout and add rich content to it

With this release, admins will have more control over their help center's home page, allowing them to tailor it to fit the needs of their audiences. They will be able to:

• hide and reorder sections on the home page to create a more organized experience
• add layouts, images, and rich content to make the help center visually engaging and user-friendly.

This will help admins create a more customized and appealing help center for their different audiences.

Dedicated page for Atlassian Intelligence answers in the virtual service agent

We've moved the toggle for Atlassian Intelligence answers in the virtual service agent out of the Settings page and into its own AI answers page.

To turn Atlassian Intelligence answers on or off in your project's virtual service agent:

1. From your service project, select Project settings, then Channels & self service, then Virtual service agent.
2. Select AI answers.
3. To activate Atlassian Intelligence answers, turn the toggle on next to Atlassian Intelligence answers, and then select Activate.
   • Atlassian Intelligence answers will start working immediately in all of your connected channels.
4. To deactivate Atlassian Intelligence answers, turn the toggle off next to Atlassian Intelligence answers, and then select Deactivate.
   • Atlassian Intelligence answers will stop working immediately in all of your channels.

Read more about Atlassian Intelligence answers.

Address gaps in your knowledge base with suggested topics

You can now quickly identify the topics that require knowledge base articles in your project with suggested topics powered by Atlassian Intelligence. This feature gives your team a headstart on knowledge articles you should be creating to deflect requests and increase self service among your customers.

To generate a list of topics, we analyze the details of recent requests in your project and check for related articles. The list of suggestions will be refreshed every 7 days, ensuring that your team remains informed of the most relevant topics.

Read more about suggested topics in knowledge base.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Prevent people from downloading attached files

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

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. We found that organizations that needed to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policy currently block exports:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Get more work done in less time with suggestions in Jira Service Management

We’re introducing suggestions on the issue view to help your teams gather context and start working on issues quickly based on a list of actions. Powered by Atlassian Intelligence, this feature is currently available for service requests and incidents only.

To turn on suggestions for a project:

1. From your service project, select Project settings, then Features.
2. Turn on Suggestions.

After the feature is turned on, the suggestions will appear automatically in the issue view for requests and incidents along with other context fields.

Read more about suggestions.

Tailor your Jira Service Management sandbox setup

We're excited to introduce a new feature that allows you to save time by copying only the specific Jira Service Management (JSM) projects you need to your sandbox. This enhancement streamlines the setup process, ensuring you have exactly what you need without unnecessary clutter. Additionally, audit logs now track the copying of specific projects, providing a clear record of changes for better management and oversight. Understand how to select data to copy

To copy specific Jira Service Management (JSM) projects from your production to its sandbox:

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

Learn about what we copy to sandbox

New AI features to find similar issues, triage issues, and more

We’re excited to announce that the following Atlassian Intelligence-powered features in Jira Service Management are now generally available:

Similar requests panel that helps agents easily find issues similar to the one they’re working on.

Customer sentiment that helps you quickly understand how customers are feeling based on their comments.

Triage issues that suggests new request types for multiple issues in your queue.

Read more about Atlassian Intelligence features in Jira Service Management.

Introducing a brand new way to complete bulk actions in the issue navigator

We’re introducing a toolbar in the issue navigator so users can update multiple issues even more seamlessly.

To use the new toolbar:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. Use the issue checkboxes.
   2. Hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. You can either select Edit fields to make edits to fields in your issues or Change status to transition your issues.

Virtual service agent in email is now generally available

We’re excited to announce that the virtual service agent in email is now generally available. You can activate the virtual service agent in email so that your customers can find the help they need. When your customers send requests to the email address connected to your project, the virtual service agent responds using Atlassian Intelligence answers.

Find out more about using virtual service agent in email

New automation rules and the Service Triage Agent

We’re introducing new automation rule templates that trigger the Service Triage Rovo Agent and use its responses to automate field updates for requests in your service project.

Currently, we’ve introduced the following templates:

• A rule that updates the summary based on the issue description
• A rule that updates the priority for an issue based on similar requests
• A rule that updates the request type for an issue based on similar requests
• A rule that generates a summary of the issue when it’s closed

For example, when a new request is created in your project, Service Triage can suggest a priority based on similar requests and update the priority field if the suggested value is different from the current value. The Agent also adds an internal comment to describe the updates, so that anyone working on the request can view the changes.

The fastest way to get started is to use a template:

1. In your service project, go to Automation.
2. Select the Templates tab.
3. Select the Service Management category
4. Select a template and follow the prompts to configure it.

When you use the template, you’ll need to connect Rovo to your instance.

Read more about how to connect to Rovo.

Read more about Rovo Agents in automation.

The 'External Assets Platform' Custom Field is shutting down

The ‘External Assets Platform’ is shutting down as part of our ongoing efforts to deliver the most streamlined and integrated service management solution. Learn more about the shutdown of the 'External Assets Platform'.

If you’re a customer currently using the ‘External Assets Platform’ to add context to your Jira issues, we recommend you consider adopting Assets in Jira Service Management, available to Premium and Enterprise customers. Assets allows you to use the Assets objects custom field to display your objects on Jira tickets, and gives you the ability to display your Assets data within Confluence, along with many other features.

Jira: Grant permissions to manage versions (releases) in one project only

You can now assign a dedicated Manage Versions permission in Jira and Jira Service Management projects without giving full project admin access. Users with this permission can create, release, archive, merge, edit or delete versions within a specific project only. This applies to company-managed projects in Jira and Jira Service Management, and team-managed projects in Jira only.

Jira automatically grants this permission to users with project admin permissions.

To grant the Manage versions (releases) permission in a company-managed project:

1. Go to a project’s settings then select Permissions.
2. Using the Actions menu, select Edit permissions.
3. Under Project permissions, look for Manage versions (releases). Add the roles, groups, or people you’d like.
4. Select Update to save your changes.

To grant the Manage versions (releases) permission in a team-managed project:

1. for tea,-managed projects, select Access then Manage roles.
2. Select Create role, then find Manage project name versions (releases).
3. Add the roles, groups, or people you’d like.
4. Select Update to save your changes.

Introducing a brand way to delete multiple issues in the issue navigator

We’re introducing an easier way for users to delete multiple issues from their projects.

To delete multiple issues from the issue navigator:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. Select Delete to delete the selected issues.

The end is near for Epic Link and Parent Link fields

For a little over a year, we've been working to combine the Epic Link and Parent link fields in company-managed projects into the new universal Parent field (which you can read about here). To prevent data loss, the values from both fields have been automatically ported into the Parent field.

With this change, the values in the Epic Link and Parent link fields are no longer visible on the Issue view. If your issue view still includes these fields, simply swap it for the Parent field instead.

Read more in our documentation

Updated search and filtering options for queues ✨

Filter your queues further with dropdown filtering! This is a highly requested feature of queues that we're excited to announce for Jira Service Management. By default, the Request type, Status, and Assignee filters are always available, but you can also use More filters to add additional filtering options based on other fields in your project.

We've also updated the search bar in queues so that it can now search through almost all text fields on your work items, including the issue key.

Read more about queues.

Create unique, customizable pages in your help centers

Jira Service Management Premium and Enterprise users can create and design landing pages in their help centers.

Admins can use landing pages to curate and efficiently organize help resources for specific subjects or audiences in a visually appealing manner. These stand-alone pages have customizable layouts to which admins can add rich content, images, videos, links, and more.

To create a landing page:

1. Go to the help center of your choice.
2. Select your avatar, and from the dropdown, select Landing pages.
3. Select Create page.
4. Give your page a name and description and select Create.

Read more about creating, customizing and managing landing pages.

See all your Asset attributes now in Forms

Take the guesswork out of selecting the right Asset when filling out a form and find all attributes now visible on Asset form fields. Previously when filling out a form, customers would only be able to see the object name which made it hard to know what option to select. Now you’ll see the same attributes listed alongside each object - just like you do on request types.

Add and remove fields from field configurations; new tools to optimize fields in your projects

We’re introducing a number of improvements to the way field configurations and field configuration schemes work. In addition, we’re also adding some new tools which make it easier to remove unused work types and fields from schemes. Here are more details about what’s changing.

You can now remove and add fields to field configurations

Removing a field from a field configuration is similar to hiding it. However, when a field is removed, its configuration isn’t preserved. It will need to be entered again if the field is re-associated.

Adding a field to a field configuration is similar to unhiding it. Once unhidden, it becomes available to the projects associated with the field configuration scheme.

You can manage field associations in the Jira admin panel or using the new field association REST API.

We’re releasing tools which allow you to optimize fields

These tools will automatically identify and remove unused work types from a scheme, as well as unused fields from a field configuration scheme and field configuration. For more details about these tools, see this Atlassian community announcement or type: entry-hyperlink id: 5m0df9oFEgswh305bKEQ1v

Unlocking another level of help center customization

The Jira Service Management help center is getting a sleek and modern design update across all its pages, offering new opportunities for customization. Admins will be able customize the help center navigation and manage background and text color for sections in their home page.

To customize the navigation:
1. Go to the help center of your choice.
2. Select Customize, then Customize look and feel from the navigation.
3. Scroll down the side panel to find the navigation color settings.

To manage section settings:
1. Go to the help center of your choice.
2. Select Customize, then Edit page layout from the navigation.
3. Select the section you want to customize and manage its settings on the side panel.

AI drafts to help you write knowledge articles faster

To make it easier for your team to write articles, we’re releasing a new feature that uses Atlassian Intelligence to generate drafts for the most common requests you receive from your customers. AI drafts are based on details such as summary, description, and comments in issues.

To access AI drafts, you need to have an active knowledge base and Atlassian Intelligence turned on for your site.

To view AI drafts:

1. From your service project, go to Knowledge base.
2. Select Suggested topics.
3. Under the Topics column, you can view specific topics for which customers are submitting requests but your knowledge base doesn't have corresponding articles.
4. Select View draft.

Make necessary edits to the draft and create an article to add to your knowledge base.

Views added to queues in Jira Service Management

We're introducing the ability to choose how you view work items (issues) in your Queues in Jira Service Management. Providing more flexibility to support how your team likes to track and manage their work, this upgrade means there are now three ways to view each of your queues: as a list, a board, or a calendar.

The current default view of your queues will be renamed to 'list view' and will become just one of the ways you can view the work items in each queue. You can have different views on each queue and any views that you add will appear as tabs, allowing you to easily switch between the different views.

You need to be a Jira or project admin to add or remove views from your queues.

Add a view to a queue

1. From your service project, go to Queues and select the queue to which you'd like to add a view.
2. From your queue, select the Add to navigation button. You'll find it in the tab bar between the queue name and the search bar.
3. Choose the view you would like to add, then select Add to navigation.

Once you've added multiple views to a queue, you can use the tabs to quickly switch between them.

Remove a view from your queue

1. From your service project, go to Queues, then select the queue from which you'd like to remove a view.
2. From your queue's tab bar, hover on the view you would like to remove, then select Tab options next to the view name.
3. Select Remove. You can add the view again at any time.
4. In the Tab options menu, you'll also have the option to edit the name of each view and change its position on the tab bar.

Customize the settings for each queue's views

The ability to customize each view for each queue can be managed from Queue setttings.

1. From your service project, select the More actions menu next to Queues, then select Queue settings.
2. In the Actions column, select Edit queue to access the settings for that queue.
3. Here you can access the general settings for your queue, along with the specific settings for the list, board, and calendar views if you have added those views to the queue.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

New Workato action in Jira Automation

We’ve built a new integration with Workato. The integration connects your enterprise stack with Jira Service Management, unlocking powerful use cases for both IT and business teams.

With the new Workato integration you can connect and run Workato recipes, allowing you to fetch information and take actions across hundreds of applications directly from Jira Automation via the Trigger Workato recipe action in your automation rule.

Before using the Trigger Workato recipe step or action for the first time, Premium and Enterprise Jira Service Management Cloud customers will need to create a connection with Workato by:

1. Generating a Developer API token and a Platform API/auth token from Workato.
2. Using these credentials to create a Workato connection from Jira Automation.

You can create a connection with Workato by creating an automation rule that uses the Trigger Workato recipe action. This action triggers a Workato recipe that runs at a specific point in an automation rule. You can use smart values to access Workato request response data in subsequent rule actions.

Read how to create a Workato connection from Jira Automation

Read how to set up the Workato action in your automation rule

Connect and manage on-call schedules in Slack

You can now connect on-call team schedules to your team's Slack channel and receive notifications about any changes to on-call shift changes.

While connecting the on-call schedule to Slack, you can also set up an alias like !Hello that can be used to tag or @mention the current on-call member in a message. It lets you easily see who's on call and notifies the on-call member.

To link a schedule to your team's Slack channel,

• Run the command /jsmops oncall on the channel and click Connect schedule.
• Alternatively, you can run the command /jsmops connect schedule to start connecting the schedule.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

We've launched a new prioritization project template

When you set up a new project in Jira, you can use project templates. There are many to choose from, including specific templates from different apps like Jira Product Discovery and Jira Service Management.

We've just added a new template for projects that are all about gathering ideas and prioritizing them. With this new prioritization template you can list ideas and add data to them. You can then use this data with common frameworks (such as RICE) to prioritize. The project has multiple views, like an effort and impact matrix, list, or roadmap view, so you can see and share your priorities in a way that suits you.

Anyone who has Jira Product Discovery and permission to create projects can use this template.

Trigger an Automation rule during a virtual service agent conversation

Use the new run Automation rule step to trigger Automation rules during virtual service agent conversations!

Your customers won’t notice when an Automation rule is run – it all happens in the background while they're chatting with the virtual service agent.

Find out how to run an Automation rule in a conversation flow

See the Premium features in-product before starting a trial

We're introducing a new and faster way to understand and upgrade to Jira Service Management Premium trial. Whenever you choose to upgrade to Premium or start a trial, you will see a modal which lists all new features available to you.

Now you can create roadmaps from your Jira timeline

Sometimes, you need a custom roadmap view to share your work plans with certain stakeholders. You may not need to include specific dates, for example. Now, you can access Jira Product Discovery from the Jira timeline view. Look for a button that says "Create roadmap" when you select the "Share", " Today," or "Timeline mode" buttons.

You can use Jira Product Discovery to create custom roadmaps, then share them with anyone, even if they don't use Jira.

Only people who are admins and don't already have Jira Product Discovery will see this change. You dismiss it anytime.

Playbooks in Jira Service Management

You can now use playbooks to create clear, step-by-step instructions and automated rules for resolving issues. Similar to Standard Operating Procedures (SOPs), playbooks help standardize and optimize your issue resolution processes. Read more about playbooks.

To view a list of playbooks, go to Project settings > Playbooks.

Click a playbook to open it, or create a new playbook using the Create playbook button.

We're making it easier to compare plans during a trial

When you're in a trial, you can now click on the trial button in the top navigation and see the plan options available to you. This way, it'll be easier for you to understand the plan that is best for your team based on the features that plan includes. You can also easily upgrade and pay from the plans page.

Get notified when email requests fail

Project admins now receive notifications right in their inbox whenever emailed requests are not processed successfully. This proactive means of communication ensures that admins are informed timely of failed email requests or connection issues with email accounts connected to their project.

By default, notifications are sent to all listed admins of a project. There is also an option to send these notifications to a specific email address instead of all admins.

In cases where self-signup is disabled or a customer doesn't have access to a service project, we will also notify customers so they are aware their request was not processed.

To specify who receives these notifications for your existing connected accounts:

1. From your service project, go to Project settings, select Channels and self service, and then select Email.
2. Select Edit against the required email address.
3. Enter the email address of your choice in Error notifications email address.
4. Select Save.

Edit your workflows quicker and easier with the power of AI!

In Jira sites that have Rovo enabled, the New Workflow Editor now includes an AI Workflow builder agent that can help add, change, or delete statuses and transitions in a workflow. It can also answer questions about the key differences between the old and new workflow editor.

While the agent is still learning, you can prompt it to add or remove the following rules from an existing workflow:

• Restrict who can move a work item
• Update a work item field
• Validate a work item field value
• Change an assignee
• Check a work item field value

Then select Update workflow on the workflow diagram to save the changes it suggests.

Journeys chart added to project summary

A new Journeys chart has been added to the metrics and charts that can be found on the project summary page. Read about the project summary page in Jira Service Management.

Navigate to your service project, then select Summary in your project’s sidebar.

At the bottom of the page, you'll see the Journeys bar chart showing the count of in-progress journeys by journey name.

• Note that you'll only see the Journeys chart if Journeys is available in your project. Read more about journeys.
• If Journeys is available but you are yet to create or run any journeys, you'll see a placeholder for the chart with a message that there's no journey data available. Create and run some journeys to populate the chart with data.

Avoid accidentally deleting work items

We’re changing the way Premium and Enterprise users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you can now choose to archive it, or confirm that you want to delete it.

Create and manage email templates for stakeholder notifications

Jira Service Management Premium and Enterprise users can now save time and customize stakeholder notifications on the go with email templates.

Email templates provide an easy and efficient way to customize stakeholder notifications. They eliminate the need to draft new emails from scratch, especially when teams are responding to incidents, allowing for quick customization and notification. Templates ensure consistent messaging by structuring emails to include all necessary information. You can also use predefined placeholders and dynamic fields, which help minimize the likelihood of omitting critical details.

To create an email template:

1. Go to Settings, then Products.
2. Under Jira Service Management, select Incident management.
3. Go to Email templates.
4. Select Create template.
5. Type in name, sender and reply address, upload header image, if any, and type in the email body.
6. Select Save template.

Find out more about creating and managing email templates.

Add tags to alerts in Slack for better organization

If you're using the Slack integration with your alert management, you can now add tags to your alerts directly from Slack. This will help you organize, categorize, and filter your alerts based on specific criteria.

• To add tags to a new or an active alert, select the more actions menu (•••), then select Add tags.
• To add tags to a closed alert, select Add tags.

You can add multiple tags at once by separating them with commas.

A cleaner All activity tab in work items

We’ve updated the All tab in the activity section of each work item. This improves readability and reduces clutter.

It's easier to scan and understand updates in a work item’s history, at a glance:

• Entry grouping: Similar updates are now grouped together to reduce clutter.

• Modern UI: Improved alignment, formatting, and date presentation for a cleaner look.

• Progressive disclosure: Long descriptions and details are now collapsible, reducing excessive scrolling.

This more structured and intuitive layout helps you quickly access relevant updates without the overwhelming detail.

Jira: Improvements to the child work item panel

The child work item panel is faster to load and more responsive.
You now get smoother scrolling, better performance and real-time, instant updates (without needing to refresh).

Performance and reliability improvements for Assets in Jira Service Management

As announced last year, we’re rolling out several changes to the Assets platform in Jira Service Management designed to improve the system's overall performance and reliability. This includes adding new limits and removing support for several AQL operators, functions, and endpoints. See the following Changelogs for more details:

https://developer.atlassian.com/changelog/#CHANGE-1739

https://developer.atlassian.com/changelog/#CHANGE-1915

https://developer.atlassian.com/changelog/#CHANGE-1905

https://developer.atlassian.com/changelog/#CHANGE-1906

https://developer.atlassian.com/changelog/#CHANGE-2198

Jira: Introducing an improvement to attachment previews

Introducing Grid view for attachments.

This change improves the organization and visualization of attachments.

Attachments appear in a grid view rather than the strip view and list view. You'll still be able to switch to another view, and save that as the default if you prefer.

Grid view helps you to more easily navigate through your content.

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

Limits to work type schemes and field configurations are coming in 2026

We recently announced that Jira will limit the number of work types that can be used in a project to improve performance and reliability of large sites starting in February 2026. Work type schemes will be capped at 150 work types per scheme, and field configurations will be capped at 700 fields.

In our recent post in the Atlassian Community, we cover what tools are available to help you clean up your sites in preparation for this change.

phantom-3037-playbooks-admin-navigation-spotlight

You can now use playbooks to create clear, step-by-step instructions and automated rules for resolving issues. Similar to Standard Operating Procedures (SOPs), playbooks help standardize and optimize your issue resolution processes. Read more about playbooks.

• To view a list of playbooks, go to Project settings > Playbooks.
• Click a playbook to open it, or create a new playbook using the Create playbook button.
• To control the visibility of playbooks, go to Project settings > Features > Playbooks. By default, playbooks are visible.

You must have project admin permissions to view and access playbooks.

Subscribe to your change calendar and explore the new filters

We’ve made major improvements to the change calendar to help you stay on top of change events and avoid conflicts across your services, Assets objects, and teams.

Subscribe to change calendar from your external calendar
You can now generate an iCal link and subscribe to your change calendar from apps like Google Calendar, Apple Calendar, and Outlook. This lets you stay updated on change activity without logging into Jira Service Management.

New JQL filtering in change calendar
Use JQL to filter work items shown in the calendar view. Filter by affected services, affected Assets objects, change types, or any custom fields, so you can focus on exactly what matters.

Show or hide change events by type
Choose which types of change events to display on the calendar, including freeze windows, maintenance windows, and standard work items.

Link your change calendar with affected services and Assets objects
You can now select affected services and Assets object fields when creating a new change window. This helps surface change conflicts more clearly and ensures better risk insights for service-dependent work. Read how to connect Assets schemas with changes

Generate a subscription link directly from your change calendar following these steps:

• Navigate to Operations > Change calendar in your service project.
• Select Subscribe to change calendar icon in your toolbar.
• Choose the event types and calendar format, then generate your calendar link.
• Paste the link into your external calendar app (Google, Apple, or Outlook). Read more about subscribing to change calendar

Once subscribed, you’ll automatically see any future updates to change events in your external calendar.

You don’t need to take any action to start using the new filters or event fields. They’re already available in the change calendar and the change event creation form.

Set up operations from Your work

You can now easily set up operations from the Your work page in Jira Service Management if you haven't set them up yet.

With operations, you can empower your team to stay on top of alerts with advanced alerting and on-call capabilities.

* Integrate your apps and keep alert data in sync

* Route alerts to the right people


• Create and manage on-call schedules to respond to alerts faster

Additional fields now editable in the All work list view

You can now edit Confluence items and linked Goals from the All work list view.

Confluence items and comment summaries are also now included when exporting work items to CSV or HTML.

• In the All work tab, view work items in list view.
• Select Configure columns in the column bar to add the Confluence items or Goals fields to the list view.
• They can now be edited directly in the list.

Enable your project summary page in Jira Service Management

For projects that have never had the project summary page enabled, admins will see a prompt that provides information about the summary page, with the option to enable it in one step. Read about the project summary page in Jira Service Management.

Jira and project admins can enable a project’s summary page from the Feature lab. Once enabled, the project summary page can be viewed by both admins and agents.

1. From your service project, go to Project settings, then select Features.
2. On the Features page, look for the Feature lab heading and find the Project summary toggle.
3. Use the toggle to turn the feature on (or off).

New 'offer options' standard flow in the virtual service agent

We heard your feedback about the escalate standard flow creating too many work items, so we've introduced a new standard flow, called offer options. Depending on the situation and the channel, offer options is sometimes used instead of escalate.

Offer options is configurable, and lets you choose 1–3 options to present to your customers. These appear as buttons:

• Raise a request starts the escalate standard flow, which lets the customer know a request has been raised and creates a work item.
• See search results takes the customer to the relevant portal, and shows search results based on their first message in the conversation.
• Ask another way tells your customer to try rephrasing their question.

Read more about the 'offer options' standard flow, or find out how to configure 'offer options' in the virtual service agent.

Refined drag and drop experience in the work item

We’re refining the drag and drop experience in the work item to make it more consistent and intuitive across different views in Jira.

We’re running an experiment with two variations.

Search all apps from Jira

You can now use the "All" tab and a new "Search all apps" option in Jira quick search. This update makes it easier to find content from multiple Atlassian apps in one place.

1. Open Jira and select the search bar at the top of your screen.
2. Find and select the new "All" tab in the search dropdown.
3. Use the "Search all apps" option to expand your search beyond Jira.

Link your team to Jira projects and Confluences spaces

You can now associate teams with projects in Jira and spaces in Confluence, making it easier to find the teams who work in any given project or space. You'll see linked teams at the top of the Jira project page and a Confluence space's main page, as well as connected projects and spaces on a team's profile.

You can link your team to a Jira project or Confluence space from the "Team links" section at the top of the team profile. You can also link a team from the Jira project or Confluence space themselves:

1. Go to the Jira project or Confluence space's main page that you want to link.
2. At the top of the page, select the team icon next to the project or space's name.
3. Enter your team name(s) in the search field and select the team(s) you want to link.

Reorder starred projects in the sidebar navigation using drag and drop

You can now reorder the starred projects in your sidebar navigation to more easily organize your projects according to your preferences.

Here's one way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Hover over the starred project you want to move.
3. Drag the project to your desired position.
4. Drop it to set the new order.

Here's another way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Select the More actions for the starred project you want to move, then select Move in sidebar.
3. Select where you'd like to move it in the order.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Create and reorder work items faster in the All work tab

We’re rolling out sibling create and drag and drop re-ranking in the All work tab, so it’s easier to structure and prioritise related work items without switching views.

You can now quickly create a new work item at the same level (a sibling), and re-rank work items by using drag and drop (select and move) when sorted by rank.

Now available for both team-managed and company-managed projects in the All work tab.

Key benefits:

• Plan faster by creating structured work items in context.
• Prioritise quickly with drag and drop (select and move) ranking.
• Avoid unnecessary actions and switching views.

1. Go to the All work tab.
2. Check that your view is sorted by Rank.
   1. Select a work item, then drag and drop (move) to reorder based on priority.
   2. Select a work item, then + Sibling to create a related work item.

Jira: Collapsible sections in work items

You can now collapse sections in a work item view to reduce scrolling and highlight key information.

To use collapsible sections:

1. Open a work item in Jira.
2. Find the section you want to collapse, such as Description or Activity.
3. Select the chevron or section title to collapse or expand it.

Due date notifications now available

As the assignee of work items that are overdue or due today, you'll now receive daily notifications within Jira and via email. Each notification links to a pre-filtered page showing your overdue and due work items. Manage your due date notification preferences by:

1. Select your profile image at the top-right navigation.

2. Select Notifications, then you can manage how you receive notifications for overdue work items.

For more details, join the conversation and provide feedback on our Atlassian Community.

Create custom roadmaps directly from your project menu

Jira Product Discovery is an Atlassian app that allows people to create custom roadmaps. You can add or edit information such as dates, assignees, and more.

You may now see a recommendation in your project menu about Jira Product Discovery roadmaps. You can select this recommendation, add Jira Product Discovery, and create a new project with a custom roadmap template.

Only admins will see this recommendation. It is being rolled out to people on Free Jira plans first, then it will roll out to Standard and Premium Jira plans in the next few months. You can dismiss it at any time or go to admin.atlassian.com to manage your recommendation settings.

Jira: A wide view for work items

Reduce visual clutter and surface essential details only by switching your work item to the wide view layout.

To switch your layout:

1. Open a work item in Jira.
2. Select Switch layout.
3. Choose Wide view.

Improved object view in the Assets object graph

We're thrilled to announce a major update to the Assets object graph, designed to streamline your workflow and enhance your user experience. This update brings a host of new features and improvements that make managing your object data more intuitive and efficient.

Improve visual and hierarchy of the Quick actions menu in the work item

We’ve improved the Quick actions menu in the work item with a cohesive visual look, and better action hierarchy and grouping, making it easier for you to find and use the tools you need.

We’ve also added Goals and recommendations to the menu.

Open a work item and select the Add button under the summary.

Import workflow from Marketplace feature has been deprecated

With this release, users will no longer be able to import workflows hosted in marketplace apps.

Update more fields with AI triage

You can now update additional fields such as Priority and Assignee while triaging work items in your queues. When you triage work items, AI will suggest values for priority and assignee. If the suggestions don't match what you need for your work items, you can select more suitable values from the list and continue the bulk update.

We’ve made looking up Assets objects in Automation easier

You can now use filters to generate an AQL query when using the Lookup objects action in Automation. Simply select Basic to choose an object type plus any attributes, and an AQL query will be generated for you. This query will use attributes as placeholders for you to then customize with relevant smart values. The results of this query can also be used in other Automation actions using the lookupObjects smart value. Read more about using smart values for Assets.

Improvements to the Fields pages in Jira Admin - Part 1

We're rolling out the first phase of our improved fields management experience in Jira that we announced in the Atlassian Community at the start of June. Our post outlines the full list of changes as well as how this fits into our larger plan. The Atlassian Community is also where we'll share updates, announce future changes in full detail, and engage with the community to make sure we're delivering an experience that meets your needs.

This first release includes changes that make field management simpler and more efficient for Jira admins, such as a redesigned Fields page (formerly Custom fields) that now shows fields created by Jira or plugins (i.e., System fields). You can also create and add new fields to configuration schemes without leaving the page, and filter and sort fields based on Field category type.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

New ways to associate a field to a field configuration scheme in Jira Admin

When this feature rolls out, admins will be able to:

• associate a new field to all of the field configurations used by a scheme without leaving the page, and
• view and edit which field configurations that field is a part of via the More actions (•••) menu on the Fields page

This work is part of our ongoing efforts to improve Fields management in Jira.

Attachments now supported for the 'Send customized email’ action in Automation

We’ve introduced the ability to add attachments to emails sent as part of your automation rules.

Once a rule has been saved or enabled, you’ll be able to upload files as part of the email content. When the rule executes, any uploaded files will be included as attachments to the emails that are sent.

This capability will be available when using the Send customized email action as part of your Jira automation rules, and will become available for use in other Atlassian apps in the future.

Read more about the Send customized email[ action in Automation.|https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-customized-email]

This highly-requested update includes:

• Attachment support: You can now add up to 10 attachments (in most file formats with a total size of 4MB) to your automated emails.
• Secure storage: All attachments are stored securely in Atlassian’s media platform, ensuring reliability and compliance.
• Easy preview: Once uploaded, you can open a preview of an attachment by selecting a card in the Attachments field.

To add attachments to your automated emails:

• Add the Send customized email action to an automation rule, then fill in the email details in the Settings tab.
• Select the Content tab, then from the Attachments field browse or drop the files you want to attach to the email.
• Select Update.

Note that the rule must be saved or enabled before you can add attachments to the email action.

More functionality in the new workflow editor, plus it's becoming the default experience

This release has two small improvements which means the New workflow editor can do everything that the old workflow editor could do. These changes are:

• You can set a name for your transitions when you create them, and rename existing transitions.
• When you change the name of a status that's included in a transition, the transition automatically updates to match the new name.

And with those changes, the New Workflow Editor is a worthy successor to the old one, and we're excited for it to become the new face of workflow changes in Jira.

That said, Jira will use the new workflow editor by default when editing global workflows unless you've set the old editor as your default in settings. If you set the old as your default workflow editing experience, then nothing will change for you, but we are planning to deprecate it soon.

For now, enjoy the vastly superior new workflow editor. Let us know what you think by sending us feedback through Jira.

Prompt inactive Confluence users to create content from work items

We're introducing a feature that encourages inactive Confluence users to create content directly from Jira work items. This feature targets users who haven't been active in Confluence for the past 28 days and belong to sites that have had Confluence for more than 14 days. When these users view certain Jira work items, they'll see a suggestion to create a relevant project document in Confluence.

To start using this feature:

1. Open a Jira issue of type epic, story, or bug.
2. Look for the Confluence content section.
3. Select the suggested template to create a project document in Confluence.
4. Follow the prompts to complete and publish your document.

Add inline images to the 'Description' field on request forms

We're rolling out a Help Center enhancement that allows images to be directly embedded in the Description field of a request form. This enables help seekers to provide screenshots, diagrams, or other images related to their requests and gives the support team the context they need to resolve requests quickly.

To maintain a clear distinction between embedded content and additional supporting files and to avoid duplication in the activity feed, inline attachments will appear in the Description field, and file uploads will appear in the Activity section of the request, under the first comment.

This feature respects the attachment settings the admin has defined, which can be modified in the admin configuration panel for each request type.

In the request form:

• When attachments are enabled, users will see both the Attachment section and the inline image icon in the rich text editor toolbar within the Description field.
• When attachments are disabled, neither the Attachment section nor the inline image option will be displayed to honor the admin’s configuration selection.

To add inline images to the Description field when submitting a request from the Help Center:

1. Go to your Help Center and start a new request.
2. In the Description field, select the image icon in the rich text editor toolbar.
3. Upload or drag and drop an image to embed it in a specific position within the description. Repeat as needed.
4. Complete and submit the request.

We're deleting unused field associations

Starting today (June 16, 2025), we’re beginning the process of removing unused field associations from your field configuration schemes. We expect this process to take several weeks from today. Once finished, this will improve the performance and stability of your Jira instances.

If this causes any issues in your projects, we have documented the steps for adding fields back in this Atlassian community announcement. The page also covers how we determine which associations to delete. If you have any questions about this scheduled deletion, you can ask them in the comments section of the linked announcement.

Set the default comment behavior in the work item view

We're introducing the ability for admins to set the default behavior for comments on the work item view (in addition to transition screens, which has already been released).

Admins can now configure the default comment behavior at the instance level, ensuring that the setting aligns with their organization's communication preferences.

As part of this change, admins can choose whether comments default to 'Internal note' or 'Reply to customer' in both the transition screen and the work item view, enhancing control and flexibility in managing communications within a team's workflow.

To change the comment behaviour defaults:

• Go to Settings, then Products.
• In the Jira Service Management section, select Configuration.
• In the Default comment behavior section, select the desired defaults for both the work item view and transition screen.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Allow Slack apps to trigger on-call alias responses

You can now allow Slack apps, workflows, or webhooks to trigger Jira Service Management ChatOps responses using schedule aliases.

Previously, ChatOps only responded to alias messages sent by users. Now, when an app posts a message with an alias, you can allowlist it directly from the message shortcut menu. Once allowlisted, ChatOps will respond just like it does for user messages, making it easier to integrate bots, monitoring tools, and workflows into your on-call process.

To allow an app:
Hover over the alias message sent by the app, select the More actions menu > More message shortcuts > Allowlist app

Save playbooks as draft

Creating a meaningful playbook often takes time, and it may not always possible to have every detail ready upfront. To add flexibility to the playbook creation process, we’ve introduced a new Save as draft feature for playbooks.

With draft mode, you can:

• Save your work and return later to complete it.
• Build and refine playbooks at your own pace, without losing progress.
• Skip validations that are only required to turn on the playbook.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

The Edit page action is now available in Jira Automation

We've made the Edit page action available for use in Jira Automation. Previously, you could only use it in Confluence Automation.

The Edit Page action enables your rule to edit and add content to an existing page in Confluence. It can now be used alongside other actions, including those from Rovo AI agents.

Control playbooks visibility using JQL

You can now use JQL in the playbook details section to control playbook visibility. This helps agents see only the most relevant playbooks, improving process efficiency and reducing noise. Read more about playbook details.

Clearer status labelling for bypassed approvals

In an approval state of a workflow, we’ve changed the status ‘Cancelled’ to ‘Bypassed’ when an approval step has been skipped.

The 'Cancelled' label for approvals has been updated to 'Bypassed' to better reflect the action of skipping an approval step without implying the request itself was cancelled. This change aims to minimize confusion, especially for customers transitioning from server to cloud environments.

As part of this change:

• If a work item’s approval state is manually transitioned to a status other than ‘Approve’ or ‘Decline’, it will be recorded as ‘Bypassed’
• If an approval state is bypassed, any active approvals (including approver decisions) that exist for an approval state will be retained in the approvals activity history
• JQL queries will return work items with approvals activity, even if the approval is bypassed.

New ways to speed up incident response in Slack (plus Zoom support)

You can now automate more steps in your incident response process using Slack and Zoom, helping your team collaborate faster and stay in sync when it matters most.

New Slack automation actions for incidents

We’ve added new actions to Jira Automation that let you coordinate your incident response directly in Slack:

• Add bookmarks to the incident channel
• Add members to the channel using smart values or email addresses
• Add Slack apps to the channel for enhanced workflows
• Send channel messages with dynamic incident details
• Send direct messages to responders or key stakeholders

These actions are available for Jira Service Management incidents on Premium and Enterprise plans. Read more about automating incident management.

Bonus: Automatically start a Zoom call

You can now use automation to create a Zoom meeting directly from an incident, so your responders can jump into a call without delay. You can even automatically attach the meeting recording to the incident once it's available. Read how to create a Zoom meeting automatically for an incident.

Request access when you can’t view a work item

You can now request access to a work directly. This allows you to quickly ask project admins for permission to view a work item or project, so you’re not left at a dead end.

To request access to a work item:

1. Open the work item you don’t have permission to view.
2. Select Request access on the “You don’t have access to this work item” screen.
3. You’ll see a confirmation that your request has been sent to the project admins.

To review and grant access as a project admin:

1. Next to your project's name in the sidebar, select More actions (•••), then Project settings.
2. If you're in a company-managed project, select People.
3. If you're in a team-managed project, select Access.
4. Select Access requests to see pending requests.
5. Review the request and assign the appropriate project role to grant access.

Enable Free access level in Jira Product Discovery

If your site is on the Free plan, as of November 15th, 2024, everyone with creator product access will be a project admin. The access permission scheme cannot be changed.

Pin fields for ideas

You can now pin fields for ideas. This enhances the integration between Jira Plans (Premium) and Jira Product Discovery. Users can preview ideas directly within Plans, and hovering over an idea shows all fields pinned to it, providing a more seamless and informative experience.

To use this feature, the user needs to:

• Have access to Jira Plans and Jira Product Discovery.
• Have an Ideas column and have something pinned for these ideas.

Configure your financial year dates

Jira Product Discovery allows you to play with the timeline's time scale by enabling you to select the start date of your year.

Once you have updated the dates, you can always change them again by accessing the configuration options through the timeline settings panel. Click the dates in the timeline header and select Edit next to The year starts in…

The change is also reflected in the date fields. To change a quarter, select the date field name and make the changes in the menu.

Team field support update

You can now use the Team field in Jira Product Discovery and see it in Jira when you open a linked idea.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

New timeline marker

We've added a new marker to the timeline so you can see the current moment at a glance.

We've added a time marker to the timeline view so that you can see the current moment at a first glance

Bulk import ideas into Jira Product Discovery

Quickly import up to 50 ideas at once into a Jira Product Discovery list view. Copy and paste ideas directly in the creation field and then, fill in the fields inline. This feature is designed to make it much easier and faster for teams to move their ideas from other tools into their discovery project

Redirect when a view is not available

From now on, if a view isn't available for some reason, such as it has been deleted, we will automatically redirect you to a different view.

Filter and sort insights

You can now search through insights, filter them based on labels, reporter, impact or date and sort them by date or impact.

Edition Awareness in JPD

A new, dismissible edition awareness button now appears in the top-right navigation. Select this button to open a modal highlighting the benefits of the Premium plan, with clear calls to action to start a Premium trial or view plan options.If you dismiss the navigation button, an Upgrade button in your account menu will be spotlighted, ensuring you can still access upgrade options at any time.

If you’re a JPD Standard edition admin (and your site is not in trial or predunning), you’ll see a new, dismissible edition awareness button in the top-right navigation bar.

A clearer way to see who’s collaborating in databases

This update adds visual highlights to cells and cards in databases when multiple people are working together, making it easier to see where others are collaborating in real time.

To see the new collaboration highlights in databases:

1. Open any database content type in Confluence.
2. Invite or join others in editing the same database.
3. Look for highlighted cells or cards that show where your collaborators are working.

We're making it easier to find Confluence in Jira

If you've been given access to Confluence, you'll see a spotlight highlighting how you can navigate to the in-Jira version of Confluence, called Project Pages. This way, you'll be able to find and create documentation right in Jira.

Rovo customer admins can now add bookmarks

Admins (organization, site or product) on sites with Rovo can now add bookmarks to highlight particular URLs in Rovo Search, based on specific search terms. You can bookmark any URL - it doesn’t need to be in your Atlassian products or previously found in search.

There are two different methods to add bookmarks depending on whether you are a organization admin, or a site/product admin.

How to add or edit Rovo Search bookmarks

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.

A better way to browse, preview, and select page templates is here

From a blank page, page templates can now be previewed with improved clarity and context. Users can also browse all template options, or undo a template selection if need be, with greater ease.

Create Confluence whiteboards directly from your Jira backlog

With Confluence whiteboards, you can plan freely and execute quickly. Create a whiteboard directly from your Jira backlog, copy backlog issues to the whiteboard, and plan however you want.

Here are some suggestions for things you can do with Confluence whiteboards:

• Use award-winning templates such as a prioritizing and planning matrix
• Import Jira issues directly into your new planning whiteboard
• Link sticky notes and issues to show dependencies and timelines
• Turn sticky notes into Jira issues
• Engage teammates with real-time, group editing
• Collaborate using stamps, timers, and more

If an admin has three or more issues in their backlog, they'll see the button that allows them to add Confluence and start using a whiteboard. Once a team has Confluence, anyone with access to Confluence — including admins and end users — will see the button on their backlog that allows them to create a whiteboard.

You can remove this button anytime by turning off all product recommendations at in your Jira settings. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Enhanced inline commenting

You can now comment directly on inline elements such as emojis, statuses, mentions, dates, and inline cards (Smart links). Users can now leave comments on these specific elements, streamlining the commenting process and making it more intuitive and efficient for providing feedback and collaborating on documents.

Blogs are moving

To help you keep your spaces clean and tidy, we're hiding blogs for new spaces and current spaces where blogs aren't being used.

For all other spaces, we're moving blogs into the content tree so they're close to the rest of your work. You can find them in their own section, below Content.

To turn blogs back on, or turn them off if you're no longer using them:

1. Navigate to the space, then select Space settings.
2. Under Manage space, select Features (only space administrators have this option).
3. Select the toggle next to Blogs to turn them on or off.

Add hyperlinks to whiteboards

Hyperlinks can now be added to whiteboards text.

Easily share links with your collaborators on a whiteboard through free text or text within an element. Hyperlinked text will appear blue.

A unified way to share and manage access to content

Confluence sharing and access just got a revamp. It’s now clearer who has access to content and who needs access and how to give it to them. It’s also easier to distribute content, with more control over when and how you send notifications.

You can find visuals and a video walkthrough of the new experience in the announcement in Atlassian Community.

Prevent people from downloading attached files

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

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. Our findings showed that the types organizations needing to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policies currently block exports:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

We've simplified space creation

With just two kinds of pre-set spaces, each made to suit a specific purpose, creating a space is easier than ever before. Choose between Knowledge base and Collaboration, add a description to the overview, and dive into content creation faster than ever before with one of our suggested templates. Or, if you know you want something really specific, choose Custom to manually configure the features and settings for your space.

To read about these changes in more detail, check out the Community post.

To create a space:

1. Select Create from the Confluence navigation bar at the top of the screen.
2. Select Space from the dropdown menu.
3. Choose the option that best fits the purpose of the space you're creating.
4. Confirm your choice, making changes to the defaults as needed.

Creating a Jira issue can now trigger an automation in Confluence

We're adding a new trigger to Confluence automation that will let you run a rule when a new issue is created in a specified Jira project.

Space and product admins can build a rule by navigating to a page and selecting the Automation (lightning bolt) icon.

1. Select Issue created in Jira as your trigger.
2. Select Connect to connect Confluence to your Jira project.
3. If your organization has multiple Jira sites, you will need to select a Jira site from the Create connection menu.
4. Select one or more projects from the dropdown menu.
5. Continue to build your rule.

Whiteboards voting improvements

Run more flexible voting sessions in Confluence whiteboards with anonymous voting and the ability to mark yourself as done.

You can also delete old voting sessions, and hide votes on the whiteboard as needed.

Summarize changes to a page or blog post

Now when Premium and Enterprise customers visit a page for the first time in a while, they can use Atlassian Intelligence to generate a brief summary of changes since their last visit. Use this feature to quickly catch up on changes to a project plan after an important review, or to get a sense of what you missed while you were on vacation.

Atlassian Intelligence will only generate a summary if someone has edited the page since your last visit. If there aren't any changes to summarize, it will present you with a summary of the page to help you refresh your memory on the key points.

Atlassian Intelligence is available to all customers with Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

To summarize changes using Atlassian Intelligence:

1. Navigate to a Confluence page or blog post that you’ve visited before.
2. Select Summarize changes from the drop-down menu in the Summarize button on the top right.
3. Atlassian Intelligence will generate a summary of changes since you last visited the page or post.

You can copy the summary to your clipboard, rate the quality of the summary, and provide feedback on the feature using the buttons at the bottom of the summary panel.

Page previews are better than ever before

Premium and Enterprise customers will see a new and improved page preview when they hover over a page title in the content tree. This preview will contain a sampling of three short sentences taken from the page, selected and ranked for relevance by Atlassian Intelligence (AI).

Because this feature uses Atlassian Intelligence (AI), it is only available to customers on the Premium and Enterprise plan. There won't be any change to page previews for Free and Standard customers.

Prevent people from using public links in specific spaces

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 public links rule to prevent people creating and accessing public links in particularly sensitive Confluence spaces. Previously, this was only available for policies that covered classification levels or entire Confluence instances. How the public links rule works

The public links 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.

Creating Jira issues from Confluence is easier than ever with Atlassian Intelligence

Use Atlassian Intelligence (AI) to automatically generate issue summaries and descriptions when you create multiple Jira issues from a Confluence page.

This feature is only available to customers on the Premium and Enterprise plan.

To use Atlassian Intelligence to create Jira issues from Confluence:

1. Select the AI button on the bottom right of the page, then select + Create Jira issues. Confluence will generate a list of issues for you in the right side panel.
2. Hover over an issue and select the pencil icon to review the summary and description for accuracy, make any necessary changes, and add additional information as needed.
3. Select Create to save your changes and create the issue in Jira or Cancel to discard changes.
4. To remove an issue from the list, hover over the issue and select the X.

Create Jira issues from tables

We’ve made it easier to create Jira issues from tables on Confluence pages. Just highlight the relevant rows in your table and select “Create Jira issues”. We will generate a preview of your Jira issues and automatically prefill the issue description and summary using your highlighted text. You can then edit, delete or create the issues.

Confluence: Import multiple Miro boards

You can now easily import multiple Miro boards into Confluence, transforming them into editable Confluence whiteboards. This feature streamlines the process of migrating your content from Miro to Confluence.

To import your Miro boards into Confluence, anyone with create space permission can:

1. Navigate to the Confluence space where you want to import the boards.
2. Select the option to import Miro boards.
3. Follow the on-screen instructions to upload your Miro boards.
4. Confirm the import to complete the process.

Better database indexing to improve search results

We're making it easier to find information in Confluence by including the content within databases in search results. Previously, searches only considered database titles, but now, the text inside databases will also be indexed, providing more comprehensive and relevant search results.

Shapeable lines in whiteboards

Create more customizable lines and connectors in Confluence whiteboards. Added drag handles on lines now allow you to create more complex and flexible lines for all your diagramming and brainstorming needs.

Start dragging to get started. As you shape a line, more drag handles will appear.

Editor AI: Generate titles on publish

We're introducing a new feature that automatically generates a page title using AI when you attempt to publish a page without one. This update reduces the need for inserting a title before publishing a page.

What's new:

• AI-generated titles on publish: Automatically suggests a title when you publish without one.
• User confirmation required: You can accept or edit the AI-generated title before finalizing.

Open Smart Links in new tab

Open embedded Smart Links from Confluence in a new tab with easy access.

Curved lines in whiteboards

Create curved lines and connectors in Confluence whiteboards, in addition to the existing straight and dynamic lines, for more flexible and customizable diagramming.

To create a curved line, select a line on the whiteboard, select Line type, and choose the Curved option. Then start moving the drag handles to shape the line however you like.

Editor: Nested tables in Confluence

We are introducing support for nested tables in Confluence to address a key limitation in the cloud editor. You can now insert tables within tables up to one-level deep. This aims to assist migrations from the legacy editor to cloud, and improve content creation.

What's new:

• Nested table insertion: In the cloud editor you can now insert tables within tables, up to one level deep.
• Migration support: This feature aids in migrating content from the legacy editor, allowing pages with nested tables to be migrated to cloud.
• Improved editing experience: You can maintain complex table structures post-migration.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Inbound and Outbound links now available for page analytics

Confluence page analytics now feature inbound and outbound link click analytics. Inbound link analytics show pages that link to the current page and how often users arrive through those links. Outbound link analytics show click counts and click-through rates for links included on the page.

Analytics data includes Confluence active pages and blogs after Jan 31, 2025. Deleted and archived aren't included.

To access page analytics:

1. Navigate to a page.
2. Select the "X people viewed" link in the page's byline.
3. The Analytics summary displays. Select Links to see a summary of the top outbound and incoming links.
4. Select View more insights to enter the fullscreen Analytics page and view the Linked content tab.
5. Choose between the outbound and inbound links and select a time range or a set a specific date range.

Whiteboards improvements

Improvements to Confluence whiteboards include the ability to:

• attach lines to the same shape and snapping lines to shapes to improve precision and complexity in diagrams
• drag sections from their title, smart sections won’t action on every load
• bulk import all Jira issues from a JQL query
• click on the zoom percentage to easily adjust zoom level

Improved error for Smart Links in the content tree

When we can’t render the link you’ve inserted as an embedded Smart Link in the content tree, you’ll see why it can’t be displayed, and you can navigate you to the original link.

Editor: Default image insertion update

We're changing the default behavior for image insertion in the editor to always insert images as blocks rather than inline. This update addresses user feedback and analytics showing a preference for block images, enhancing document layout and usability.

Default block image insertion: Images will now be inserted as blocks by default, improving document structure.

Draggable line labels in whiteboards

Drag and reposition line labels anywhere on the line for greater flexibility and customization on your diagrams in Confluence whiteboards.

Find text easily within your whiteboards

Quickly find text within your whiteboards by using the familiar ctrl+f or cmd+f shortcut. This feature allows you to search for text across your board, making it easier to navigate and locate specific text elements without manually scanning through everything.

To use the new search feature in whiteboards:

1. Open a whiteboard and make sure to focus on the whiteboard.
2. Use ctrl+f or cmd+f to open the search menu.
   • You can also access the search feature from the top More actions (three dots) menu.
3. Input your search query into the search box.
4. Use enter or shift+enter to navigate through the search results.

Summarize differences between versions of a page

Now, Premium and Enterprise customers can use Atlassian Intelligence to generate a summary of differences between two versions of a page. This feature makes it easier to get a sense of what's changed between versions quickly.

Atlassian Intelligence is available to all customers with Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

To use this feature as a Premium or Enterprise customer:

1. Navigate to a page in Confluence Cloud.
2. Select ••• from the top right, then select Page history.
3. Select two versions to compare, then select Summarize differences.

Atlassian Intelligence will display a summary of changes made to the page between the versions you selected.

Third-party apps are now organized together and easier to find

From the More actions (...) menu of a page, you can now find and access third party apps from their own special section called Apps.

Version history now available for databases

You can now view and restore previous versions of your databases, giving you greater flexibility and control over your database content.

To view a database's history, open the database's ••• menu in the top right and select Version history.

From there, you can view previous versions of the database. You can restore a previous version by selecting it and then selecting Restore as new database. This will create a new database using that version’s content. Permissions on the new database will be the same as the original.

Editor: Select and drag multiple elements

We're introducing a new feature to the Confluence Cloud and platform editor that lets you drag and drop multiple selected elements. This update allows you to move multiple elements together using a drag handle.

What's new

• Multi-select drag and drop: You can now select and move multiple elements simultaneously by using the drag handle.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

Improved mission control and analytics with live docs

We've enhanced mission control and analytics in Confluence by integrating live docs into all charts and analytics. This update provides a more complete experience for managing and analyzing your content.

To explore the new live docs feature in mission control and analytics:

Go to your Confluence space.

Access the mission control or analytics section.

View and interact with the updated charts and analytics that now include live documents.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

Databases: Improved cell interactions

We're making it easier to interact with database cells by improving drag and drop functionality, updating styling for easier editing, and fixing bugs related to clearing behavior and menu interactions.

Loom AI-powered meeting notes in Confluence

When AI-powered meeting notes is enabled in Loom, a Confluence page containing the meeting recap, links shared in the meeting chat, and a recording link is automatically generated for each meeting recording and can be found in the user's personal Confluence space. The page is available when the meeting has ended, and is restricted to only meeting invitees.

If meeting recordings is enabled, users can turn on AI-powered meeting notes by toggling the "Generate meeting notes in Confluence" in their meeting recordings settings.

Visually organize ideas with mind maps in Confluence whiteboards

Mind map elements are now available in Confluence whiteboards. These are branching connectors between nodes that help you and your team visualize relationships between different aspects or subtopics of a central idea to brainstorm and structure information more effectively.

To use mind maps in Confluence whiteboards:

1. Open a Confluence whiteboard.
2. Select the "Mind maps" feature from the more (plus) menu in the main toolbar.
3. Start adding nodes and branches to create your mind map.

Convert pages to live docs in bulk

Space admins can now use content manager to convert pages to live docs. Live docs allow collaborative real-time editing without the need to publish.

1. In the left navigation bar, select the more actions menu in the space's name, then select Space settings.
2. Select Content manager.
3. A list of all space content displays. Select one or more pages.
4. A toolbar opens at the bottom of the screen. Select Convert to live docs.

You will see a progress bar and success message in the bottom left part of the screen.

New navigation: A faster way to find work

Key parts of the top navigation have moved to the sidebar, giving you access to multiple spaces at once. The new navigation is centered on customization capabilities and ease-of-use improvements, including:

• A customizable sidebar you can personalize to the unique way you work

• Expand or collapse sidebar options to maximize screen space when needed

• Navigation across all spaces and space settings for admins

Admins can now turn on the new navigation for their team.

Find out more about the new navigation

New interface for PDF export

We're introducing a new interface for exporting spaces as PDFs. This update streamlines the experience with a more intuitive interface without changing the output or permissions required for export.

Space admins can find the space name in the sidebar, select the more actions menu (three dots), and select Space Settings. Expand the Look and feel menu and select PDF export.

View reactions in email notifications

We're updating Confluence email notifications to display the actual emoji reaction a user has made to content or comments. This will only include standard emojis and not custom ones.

What's new:

• Display of reactions in emails: See the actual emoji reaction in email notifications.
• Improved clarity: Know exactly what emoji a user reacted with.

The Rovo button gives instant access to AI features in Confluence

The Rovo button is now available in Confluence. You can think of it as a front door to all your AI-powered actions. The button, displaying the Rovo icon, will float at the bottom right of your screen.

When the Rovo button is open, you can use the input field to enter a prompt and start a chat, or you can use it to search for available actions.

To start using the Rovo button in Confluence:

1. Open a Confluence Page, Live Doc, or Whiteboard.
2. Look for the Rovo button, it should be floating in the bottom right of your screen.
3. Select the button to explore available AI actions and tools.

Simplified space access in Confluence with roles (beta)

Say goodbye to the complex permissions table in Confluence. We're introducing a new way to manage space access using roles. This change makes managing permissions more consistent, predictable, and scalable by allowing you to assign preset roles to individuals or groups.

To get the full story, check out the Community post.

To manage space access with roles in your Confluence instance:

1. Read How to know if you’re ready for roles.
2. When ready, go to the New features section in Confluence administration.
3. Opt into the Manage space access with roles beta.
4. Create any custom roles you may need.
5. Assign roles to default access groups in Defaults for new spaces.
6. Assign roles to people in individual spaces (which you can do manually or in bulk).

Create work items using AI

You can now create work items using AI when Atlassian Intelligence is enabled for Jira or Confluence for your organization. The Jira and Confluence products must be on the same site.

Previously, you could only create work items using AI when Atlassian Intelligence was enabled for Confluence.

Recommendations in Slack

We're now sending weekly Confluence content recommendations to Slack users. These recommendations will help you discover relevant content, boost productivity, and stay connected with your team.

Get notified about your first page view

You will now get an in-app notification when a page you created is viewed for the first time.

Deprecating infrequently used macros

In 6 months on September 25, 2025, we will be removing some infrequently used macros from Confluence Cloud. To learn more about which macros are being removed, read our deprecation article, and look for macros whose “Status” column says “Will be removed from Confluence Cloud on September 25, 2025.” If you’d like to replace those macros with an alternative, you can use the Macro Usage feature of Confluence Administration to identify where they are being used.

A special look at refreshed and new experiences will be featured in-product

We're introducing a preview of some new and upgraded Confluence features that will vastly improve our user experience. Customers already enrolled in the beta programs for Live Docs or new content layout will see a large informative modal when they access Confluence showcasing these updates.

Use AI-powered brainstorming in Confluence whiteboards

You can now use smart creation on your Confluence whiteboard to summarize content, generate ideas and explore topics. This feature is informed by the content you have access to in the Teamwork Graph, and follow-up ideas, making it easier to brainstorm solo or with your team.

To access smart create:

1. Open a whiteboard in Confluence.
2. Select Smart create on the right hand action toolbar
3. Enter a prompt or topic you want to brainstorm, including any relevant links
4. Generate ideas and suggestions on your whiteboard.
5. Select any item on your whiteboard to use it as context for deeper exploration.
6. Collaborate with your team or continue solo, pulling on different threads as you go.

More filters in Rovo Search

Filters such as Confluence, Slack and Google Drive will now show in Quick find in Confluence and Atlassian Home as you start a search, making it easier to quickly filter to what you need.

Space owner ID is now available in API calls

We're introducing a new attribute returning the space owner ID to the public Get Spaces and Get Space APIs. This update provides developers with more detailed information about space ownership without affecting existing functionalities.

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

A seamless way to animate card reels in Company Hub

The new autoscroll feature in Company Hub allows you to animate a continuous reel of cards. This feature enhances the visual appeal of your content by automatically scrolling through cards, making it easier to showcase multiple items without manual intervention.

To enable and use the autoscroll feature in Company Hub:

1. Navigate to the Company Hub.
2. Add a new Cards element (/cards) or edit and existing one.
3. Select the Styles tab and turn on the "Autoscroll" feature to start animating your card reels.

Recommendations to help you get started with Confluence

When you join a team already on Confluence, you'll see recommendations on what to do next in the bottom right corner to help you quickly onboard and get up to speed. These prompts will help you: create a space, create a page, and create a whiteboard.

That means it’s easier to know what to do first in Confluence so that you’re getting the most out of it. You can dismiss these recommendations anytime.

Reading related pages is getting easier

When you're done reading a page on Confluence, you'll now see a message that will direct to you another related page so you can keep reading valuable information from your team.

Introducing the freehand pen tool on Confluence Whiteboards

The new pen tool in Confluence Whiteboards lets you draw freely on your digital canvas, making it easier to express your ideas visually. You can now create, edit, and format drawings directly on your whiteboard.

To use the new pen tool:

1. Select the pen icon from the main toolbar.
2. Begin drawing by clicking and holding your mouse or stylus. Release to finish your line.

Add Live Docs to the founding admin onboarding experience

For those with access to Live Docs, we've made it possible to add this feature during Confluence account setup for founding admins. Anyone who creates a new instance of Confluence can now select Live Docs as an option alongside other existing features such as pages, whiteboards, and databases.

To add Live Docs to your Confluence setup:

1. Begin setting up a new Confluence instance as a founding admin.
2. Navigate to the feature selection screen during the setup process.
3. Select Live Docs along with any other desired features.

Link your team to Jira projects and Confluences spaces

You can now associate teams with projects in Jira and spaces in Confluence, making it easier to find the teams who work in any given project or space. You'll see linked teams at the top of the Jira project page and a Confluence space's main page, as well as connected projects and spaces on a team's profile.

You can link your team to a Jira project or Confluence space from the "Team links" section at the top of the team profile. You can also link a team from the Jira project or Confluence space themselves:

1. Go to the Jira project or Confluence space's main page that you want to link.
2. At the top of the page, select the team icon next to the project or space's name.
3. Enter your team name(s) in the search field and select the team(s) you want to link.

Create Jira work items in the Confluence editor and in Live Docs

You can now create Jira work items directly from highlighted text in the editor and in Live Docs. This feature allows you to seamlessly move actionable work into Jira without having to publish your Confluence page or navigating to Jira.

To create Jira work items in the Confluence editor or in Live Docs:

1. Highlight the text you want to convert into a Jira work item.
2. Select the … overflow menu in the contextual toolbar.
3. Choose Create Jira work item.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Audio briefing: Listen to an AI overview of a page or live doc and its links

In just a few minutes you can catch up on long, detailed pages and live docs by listening to a briefing by Rovo.

• Look for the headphone icon on a Confluence page or live doc.

• Customize your experience to make your Overview short or long, and change the tone to professional, conversational, or playful.

• Include the info from up to 9 links embedded in the page or doc.

• Add more links to other Confluence pages and docs for even richer results.

• Start a briefing with the play button.

Please note that this new feature is generated by AI and you should verify the results. It’s your own personal work podcast, just press play.

Select the headphones icon on a Confluence page or live doc and customize or choose the Play button to start.

Weekly content recommendations

We're now sending weekly Confluence content recommendations to users connected on Microsoft Teams. These recommendations surface relevant content to help you stay productive and understand what's going on within your broader team.

A unified commenting experience across pages, live docs, whiteboards, and databases

We’ve introduced a unified comments panel across pages, live docs, whiteboards, and databases in Confluence. This provides a consistent experience that makes it easier for teams to collaborate and manage feedback, no matter where they work.

• Open a page, live doc, whiteboard, or database in Confluence.
• Select the comments icon on the action bar at the bottom right of the screen to open the new comments panel.
• Use the panel to view, reply, resolve, and manage comment threads.
• Comments are now visually aligned across all features.
• Navigate between comments using up/down arrows.
• Selecting a comment in the panel scrolls or zooms to its anchor in the content (paragraph, whiteboard area, or database cell).

Number fields now support three numerical options in databases

We are updating the definition of number fields to ensure greater consistency and clarity. With this change, number fields will now strictly accept only numerical values. Any custom format number fields that include special characters (such as text or custom prefixes/suffixes) will be moved to text fields. This ensures that number fields are used exclusively for numerical data.

Number fields now support three formatting options: number, currency, or percentage. These can be selected when customizing a number field.

If your existing custom number field contains special characters or text, it will be converted to a text field to preserve your data.

Last updated filter option in Confluence Search

In Confluence search, you can now filter results based on the person who last updated the content.

Diagramming agent brings mindmaps and flow diagrams to Confluence whiteboards

You can now use a diagramming agent in Confluence whiteboards to quickly create mindmaps and simple flow diagrams by submitting a prompt. This feature helps you visualize ideas and processes with less manual effort.

To use the new diagramming agent in Confluence whiteboards:

1. Open a Confluence whiteboard.
2. Select the option for the diagramming agent (look for a prompt or diagramming tool in the toolbar).
3. Enter your prompt describing the mindmap or flow diagram you want to create.
4. Review and adjust the generated diagram as needed.

Definitions are now available in Confluence comments

We've now made our definitions feature available within Confluence comments. Select an auto-highlighted acronym or word to look up a definition.

Reply and react to comments while reviewing notifications

You can now reply and react to Confluence comments directly while reviewing your notifications at the top right of your screen.

More shapes for richer flowcharts and architecture diagrams in Confluence Whiteboards

Now you can create more detailed flowcharts and lightweight architecture diagrams in Confluence Whiteboards. Access a wider variety of shapes directly from the editing toolbar, making it easier to represent complex processes and technical systems.

To use the new shapes in Confluence Whiteboards:

1. Select the shape in the toolbar at the bottom of your whiteboard.
2. Select the More shapes option to open the expanded shapes panel.
3. Browse or select from the new flowchart, advanced and architecture shapes to add them to your diagram.

Authenticate to view linked Jira work items in Confluence

You can now authenticate your account to view Jira work items from AppLinked sites.

To authenticate and view linked work items on Confluence:

1. Open the Confluence content where you want to view linked work items.
2. Locate the linked work items section.
3. If there are work items from AppLinked sites, follow the prompt to authenticate your account.
4. Once authenticated, the linked work items will be displayed.

Content access requests now stored on content items themselves

We've made it easier to manage access requests to content items by storing them directly in Confluence. Instead of relying on fleeting (or ignored) in-app notifications and emails, you can now view all pending access requests for a specific content item in the Share window. This helps you keep track of requests more efficiently.

To view and take action on content access requests in Confluence:

1. Open any content item in Confluence.
2. Select Share.
3. If there are pending access requests to that content, you'll see Requests top right.
4. Select Requests to open the content item's access requests screen.

Recent Smart Links now findable in Quick Find

Now, when you use the Quick Find search bar, you'll see recently viewed items that include third-party search results from searchable Smart Links. This change helps you access more relevant content quickly. All our searchable SmartLinks are supported except for Figma, which will be coming soon.

To see the new Smartlink results in Quick Find:

1. Open Confluence and go to the home page.
2. Select the search bar.
3. Look for your recently viewed items, which now include Smartlink results.

A new way to access and create automations in Confluence

Use automations from the Rovo button in Confluence. Now everyone can see and interact with automation rules directly from the Rovo button panel, making it easier to manage and create automations in your space.

To find and use the new Automations feature in Confluence:

1. Open any content type where the Rovo button is present, such as pages, live docs, or whiteboards.
2. Select the Rovo button.
3. Select the Automations button to view all admin-created automation rules.
4. Space admins can select the Create automations button to access the automation rule builder.

Add sections to your Company Hub with one click

We’ve made it easier to build your Company Hub by introducing a button that adds a section. This makes it easier than ever to expand your Hub.

To add a section to your Hub:

1. Select any existing section on your Hub
2. Select the + (plus) icon.

You’ll also see a plus icon at the bottom of your Hub.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

A new look for database tables

We have redesigned the database table interface with a modern look and we're introducing new features to streamline how you interact with data. This update includes enhanced selection options and a new action bar for more efficient editing and management.

Add a database to Confluence to check out the new changes, including:

• Redesigned Table UI:
  The database table now features updated styling, clearer headers, and improved visual hierarchy for easier navigation and readability.
• Checkbox Selection:
  You can now select individual entries using checkboxes or select all entries at once, making it easier to perform bulk actions.
• Action Bar:
  A new floating action bar appears when you select entries, providing quick access to editing and management actions directly from the table interface.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

The "Copy" option is now called "Duplicate"

We’ve updated the action for copying content in Confluence. The option previously labeled “Copy” is now called “Duplicate” in the more actions menu and content tree. This change aims to reduce confusion between copying content and copying a link.

1. Open the content tree or the more actions menu (three dots) on any content type.
2. Look for the “Duplicate” option (formerly “Copy”).
3. Select “Duplicate” to create a copy of your content.

Jumpstart creating your Company Hub with a template

We've introduced a new default template that appears when you first onboard to the Company Hub. This template is designed to better showcase visual elements, communicate Company Hub's value propositions more clearly, and make it easier to get started with a beautiful design, out of the box.

To find and use the new default template in Company Hub:

1. Open your Company Hub in Confluence on an account that has not created a hub before.
2. Follow the onboarding steps and give your Company Hub a name of your choosing.
3. Use the template to customize and create your own Hub.

Confluence lovability survey

We'd love to get user feedback via a contextual survey asking their opinion on Confluence lovability. You may be part of a group of users who have the change to rate Confluence.

If selected, you will see this message when you view a page:

• To what extent do you agree or disagree with the following statement?
  • Confluence is a product I love using.
• You will then have a chance to answer in a range of 1 to 7.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Add AI descriptions to dynamic cards

Dynamic cards now feature AI-generated descriptions. When you use dynamic cards in Company Hub or Confluence, you can now have a summary of the content added to the card.

AI-generated summaries can contain errors or inaccuracies. The use of AI in dynamic cards is optional and can be turned off.

Descriptions are now enabled by default on new dynamic cards elements. To remove the AI-generated descriptions, select the element, then the pencil icon to edit settings. Turn the Description toggle off.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

A modernized CSV export experience in space settings

The CSV export experience in space settings has been updated with a modern look and feel. You will notice stylistic improvements to the Export Space area, but the export to CSV functionality remains unchanged.

To use the updated CSV export experience:

1. Go to your Confluence space.
2. Select "Space settings" from the sidebar.
3. Choose "Export Space".
4. Select the "CSV" export option to see the refreshed interface.

A more complete audit trail in Confluence

We have onboarded all missing audit log events to the Audit Log Platform (ALP), ensuring a comprehensive and centralized audit trail across Atlassian apps. This change enhances visibility for administrators and supports compliance and operational monitoring.

To access and review the newly onboarded audit log events:

1. Go to the Administration section in Confluence.
2. Navigate to Security > Audit Log.
3. Review and monitor the audit events directly within this section.

Find content anywhere on your page with new improvements to Find and Replace

We've improved the Find and Replace feature, allowing you to search for content in more places, including statuses, dates, mentions, smart cards, and titles of expands. While you can now find content in these areas, replacing is not supported for them. We've also made color updates to provide better contrast.

Avatar visibility on Databases

We're excited to roll out the ability to see users' avatars on Databases. You can now see everyone who is concurrently working on a Database, just as you can see teammates on pages, live docs, and whiteboards.

Improved search filters findability

We've improved the discoverability of filters in quick find and search. In quick find, you can now filter by contributor and access more filters. In full-page search, we've added an apps filter above the search results.

Control notifications for team calendar events

Now you can decide whether to send notifications to watchers when creating or updating events in your Confluence team calendar. This new checkbox option gives you control over notifications, enhancing your ability to manage communication effectively.

To use this new feature:

1. Open your team calendar.
2. Create or update an event.
3. Look for the new checkbox option in the event creation/update window.
4. Select the checkbox if you want to send notifications to watchers.

Improved Database Creation: Templates & Import Options

Templates and import options are now organized into separate tabs, making it easier to start a new database. You can select from an expanded library of over 11 templates or import your own data.

Open the database creation screen and select either the Templates or Import tab to select your preferred method.

Contributors will now be mentioned in the subject line of your Confluence Daily Digest email

We are personalizing the subject lines for Confluence Daily Digest emails to include contributors’ names so users can quickly scrape core updates of the email right from the subject line itself.

The people and teams directory has moved to the Teams app

Previously, "Teams" was a navigation item in both Jira and Confluence that would show the people and teams directory within each respective app. These directories have been moved to[ the Teams app|https://support.atlassian.com/atlassian-account/docs/what-is-the-teams-app/], which you can find in the list of app shortcuts at the bottom of the app sidebar or in the app switcher in the top left corner. Aside from the location and how you access the directory, there are no other changes in how the directory is used.

You can now ask for edit access from more Confluence content types

The “Ask to edit” option in the overflow menu is now available on databases, whiteboards, and blogs, along with published pages and live docs. This makes it easier to ask for edit access directly from wherever you’re working in Confluence.

To ask for edit access:

1. Open a database, whiteboard, blog, published page, or live doc in Confluence.
2. Select the ••• more actions menu in the top right corner.
3. Select Ask to edit.
4. Your request will be sent to the content owner, and you’ll be notified when they approve it.

Use third-party secret providers in Bitbucket Pipelines

Bitbucket Pipelines is excited to introduce third-party secret integration. This powerful new feature allows you to seamlessly retrieve secrets directly from your preferred secret store. This functionality is now available for Bitbucket Cloud-based runners, and self-hosted runners.

To get started with this feature, you'll need to code your own middleware to let Bitbucket communicate with your third-party secret provider.

Then, you'll need to configure your Bitbucket pipelines to retrieve the appropriate secrets at runtime.

If your pipelines are using a self-hosted runner, you'll also need to point that runner to your middleware.

All of these steps are detailed in our help documentation.

ARM cloud runners in Pipelines

Note: This feature is only available to Standard and Premium Bitbucket Cloud customers.

Our release of Linux-based ARM runners in cloud allows you to build and deploy software for ARM-based systems with all the benefits of our fully managed CI/CD platform.

To use the new cloud ARM runners in your pipeline, make the following modifications to your bitbucket-pipelines.yml file:

• Set the ARM runtime in your pipeline’s YAML file, available as a global option or can be set as a step-level option. Declaring it as a global option will result in all steps in the file running on ARM.
• ARM builds require you to use an image that is ARM compatible, meaning you must explicitly declare an image for your build, and that image must support ARM.

See the help documentation for more details.

Use variables in any part of your Pipelines .yaml

In the past, variables in Bitbucket Pipelines were scoped to only operate within script sections of a Pipelines workflow. This limited their usefulness and restricted users from being able to fully parameterize their workflows.

Today we are releasing an enhancement that will allow variables to be used within any section of a Pipelines .yaml file, and not just within scripts. This new capability will allow you to use variables to parameterize things like cache keys, artifact names, build images, and anything else you might need. For more detailed information, check out the Variables and secrets help document.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Code suggestions are here to help you and your team collaborate on code

Now you or a teammates can suggest a code change when commenting on a line of code in a pull request. The suggested change can then, if desired, be committed directly on the pull request.

New Jira banner in Bitbucket

Bitbucket and Jira work better when you use them together. If you use Jira, you can see all of your tasks directly in Bitbucket. That means you can see more, prioritize better, do less tool hopping, and ultimately save time.

We've added a banner to the Bitbucket 'your work' page to show people how this integration can work.

The banner will only be shown to Workspace Admins who don't already have Jira. It will disappear once they add Jira, or when they dismiss it using the dots menu in the top right side of the banner.

Atlassian is changing the term 'products' to 'apps'

In support of Atlassian’s System of Work and our evolution toward a unified Atlassian platform, Atlassian is shifting how we think about and refer to our suite of individual products, now called ‘Atlassian apps’, or ‘apps’ for short.

We’ve started rolling out this naming change (from ‘products’ to ‘apps’) across Atlassian and Bitbucket Cloud experiences. Over the coming months, we’ll continue to roll this out to Atlassian apps, websites, and documentation. You may see both terms used as we work through this change.

This is a naming update only and won’t affect how you use the apps.

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.

Add tags to alerts in Slack for better organization

If you're using the Slack integration with your alert management, you can now add tags to your alerts directly from Slack. This will help you organize, categorize, and filter your alerts based on specific criteria.

• To add tags to a new or an active alert, select the more actions menu (•••), then select Add tags.
• To add tags to a closed alert, select Add tags.

You can add multiple tags at once by separating them with commas.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Data residency moves: Choose where to host your Opsgenie data

Opsgenie data residency gives you control over where your Opsgenie account data is hosted. We support data residency moves (moving data across locations) for all Standard, Premium, and Enterprise plans for Opsgenie.

To request a data residency move in Opsgenie, go to Settings > App settings > Data residency.

Learn more about data residency in Opsgenie

Record and share Loom videos in the details of your focus area

In the About section of your focus area, you can quickly record a Loom video that digs deeper into the details and adds that personal touch. If you already recorded one, you can also include that link.

Loom videos can also be recorded when crafting an update that shares progress with your followers. Links to previously recorded Loom videos can be added there too.

Search using Jira Query Language when adding work to a focus area

If a simple keyword search isn't returning the work items you need to add to a focus area, slide the JQL toggle and enter your Jira Query Language (JQL) query.

Find out more about JQL

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Expand all work items from sub-focus areas

When you are looking for work items that roll up to a focus area, you can drill down into the detailed information on the Work tab of that focus area. The table shows you the work items that were added to that focus area and all the work items in its sub-focus areas. Depending on the number of sub-focus areas and work items, you might need to expand several sections to see them all.

To make this easier, a toggle was added to the table's More actions (•••) menu to always expand the work items. This choice is made per focus area and requires that the Show work from sub-focus areas toggle is also turned on.

Get auto-suggestions when using JQL

When adding work items to a focus area from different sources, using the Jira Query Language (JQL) might be a familiar way to find exactly what you want. After toggling JQL on in the Search field, auto-suggestions will pop up to help you use valid categories, operators, and matching values.

Teams information now visible in Talent alongside positions

See and filter positions by functional teams—powered by your HRIS connector—for clearer workforce insights.

Ensure both Teams and Talent apps use the same HRIS connector (e.g., Workday). Once the HRIS connector is synced from Talent and enabled in the Teams app, teams will appear as a column in the positions table, and you can filter and view team details directly from Talent.