• Atlassian Administration
• Jira platform
• Jira
• Jira Service Management
• Jira Product Discovery
• Confluence
• Customer Service Management
• Rovo
• Loom
• Trello
• Assets
• Bitbucket
• Compass
• Opsgenie
• Atlassian Analytics
• Focus
• Talent
• Jira Align
• Teams
• Projects
• Studio
• Rovo Dev
• Goals

Connect to every Atlassian app with MCP v2

Atlassian Rovo now supports Model Context Protocol (MCP) v2. This update enables you to connect to every Atlassian app through a single, central interface. MCP v2 introduces dozens of new tools across Jira and Confluence while also adding Loom, Goals, Projects, Bitbucket, Focus, Teams and Talent support.

To get started with this change, update from Atlassian Rovo MCP v1 to Atlassian Rovo MCP v2.

Bulk remove multiple members from a group

Organization admins can now save time by removing up to 200 members from a group at once in Atlassian Administration. This update to the Group Members table allows admins to manage large groups more efficiently without the need to remove members individually.

To remove multiple users in bulk

1. Go to admin.atlassian.com.
2. Select your organization if you have more than one.
3. Select Directory, then Groups.
4. Open a group and go to the Members tab.
5. Use the checkboxes to select the members you want to remove.
6. Select Remove from the bulk actions toolbar at the bottom of the screen.
7. Confirm the removal in the Remove members? dialog.

Unified connectivity: Integrated secure tunnel setup

Admins can now set up secure tunnels for Atlassian Rovo and Teamwork Graph connectors directly within the cloud connector setup wizard. This update to Atlassian Administration simplifies the connection between Data Center and cloud apps by removing the need to manually copy credentials or restart your Data Center instance. By integrating tunnel creation into a single flow, you can securely connect your self-managed data to cloud apps with fewer steps.

Connect Jira Data Center to Rovo

Connect Confluence Data Center to Rovo

1. Ensure your Data Center instance has been upgraded to Jira 11.3.11+ or Confluence 10.2.16+.
2. Go to Atlassian Administration → Connected sources.
3. Create a Rovo connector for your existing Data Center instance
4. If your instance needs a tunnel, the wizard auto-detects an existing tunnel or offers to create one inline — no separate setup, no credential copying.
5. Approve the connection in your Data Center instance. No restart required.
6. Start using Cloud-powered features like Rovo and Teamwork Graph.

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.

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.

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

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

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.

Back up and restore Jira Service Management Assets

Assets in Jira Service Management is now included in the backup and restore of your Atlassian Cloud services.

1. Make sure you have the required permissions to use backup and restore features in your JSM site.
2. Go to the backup and restore section in your Atlassian Cloud admin settings.
3. Follow the steps to create a backup or restore your JSM Assets data.

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.

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.

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.

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

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.

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.

Personalize reliability monitoring with System health

We've introduced System health, a dashboard that shows the operational status and incident history of your Atlassian apps. This dashboard is free for all organization admins.

To start using System health:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Insights then System health to view Atlassian app statuses and active incidents.

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

Manage and optimize your Atlassian landscape with Portfolio insights

We’re excited to announce the open beta of Portfolio insights – a feature set within Atlassian Administration that enhances how you discover, view, and manage your Atlassian portfolio.

Here are the main building blocks:

• • Discover and manage:* Get a centralized view of your Atlassian portfolio, with automatic detection of Data Center instances and Cloud sites.

• • Cloud readiness insights:* Assess your Jira and Confluence Data Center instances with the focus on cloud migrations. Get detailed insights into your data and recommendations on how to improve it for a smoother migration.

• • Instance optimization:* Monitor current health and performance of Jira Data Center. Get more information on what is working well and what can still be optimized to keep your instances high-performing.

Learn more about Portfolio insights and future plans

Portfolio insights is available for every admin, with no sign-up required. We're rolling it out from April 7 – if you can't access it yet, give us a few days.

To access Portfolio insights:

1. Go to admin.atlassian.com, and select your organization. If you don't have one already, you can create it for free.
2. Go to Settings > Portfolio insights.

Get started with Portfolio insights

Consistent and accessible charts in Administration

Atlassian Administration now features updated charts powered by Atlassian Analytics. These charts offer improved performance, visual consistency, and enhanced accessibility, making it easier for admins to analyze data and uncover insights.

To get started:

1. Go to Atlassian Administration (admin.atlassian.com).
2. Navigate to one of the following pages: Overview, Security Guide, or Platform Insights to view the updated charts.

See all users and groups across your organization

We’re improving how you find and manage users and groups in your organization when you have multiple sites. This change applies to customers with the original user management experience only.

You’ll find two new pages in Atlassian Administration, under Directory:

• Users: All users across your organization, including managed accounts if you’re an organization admin.

• Groups: All groups across your organization.

We’ll start rolling out this change from June 22, 2026. We’ll email organization admins before your organization gets this change. Read the Community announcement

When you invite users from the new Users page, you can invite them to more than one site at a time by selecting apps across multiple sites as needed. If you need to make someone a site admin, invite them to the site as a user first. Then, go to their profile to assign the site admin role.

How you manage your users and groups stays the same, including if you need to update details or app access. You can still navigate to the site administration area if you prefer. Any site admins will also be able to access the new Users and Groups pages, but they’ll only see users and groups in the sites they manage.

To view the new pages:

• Go to Atlassian Administration. Select your organization if you have more than one.
• Select Directory, then Users to see the organization users list or Groups to see the organization groups list.

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.

Data Security Policies: Unified controls and streamlined management

Admins can now manage organization-wide Data Security Policies in Atlassian Administration with a simplified experience. The new controls make it easier to configure, review, and enforce security policies across all Atlassian cloud products, reducing conflicts and simplifying policy management.

To get started with this change:

1. Go to Atlassian Administration.
2. Select Security, then Data protection, and open the Data security policy page.
3. Choose a control to view or edit its configuration.
4. Create a draft, make changes, and activate the control to enforce it across your organization.

Deploy configuration changes directly from a sandbox to production environment

Admins can now deploy configuration changes directly from a sandbox to another sandbox or to a production environment. This capability for Jira and Jira Service Management helps admins save time and reduce risk by eliminating the need to manually recreate tested changes, such as workflows and screens, in their production environment.

1. Go to Atlassian Administration, then select Apps.
2. Select Sandboxes, then find the Jira sandbox you want to deploy from.
3. Select Actions, then select Create a deployment.
4. Choose your destination and follow the prompts to scan for changes, select dependencies, and run validations before deploying.

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.

Soft delete for Marketplace apps

We are introducing a soft delete feature for Marketplace apps on sites using cloud commerce platform billing and Forge apps. This update changes how you can uninstall, unsubscribe, or stop trials for Marketplace apps, providing more control and clarity during the removal process.

Control AI tool access to Atlassian apps

You can now manage domain access for Rovo MCP server, which gives you control over which AI tools and integrations can connect to Atlassian apps. You can choose to use or block the Atlassian list of supported domains, or allow access for individually selected domains.

To manage which AI tools can connect to your Atlassian apps:

1. Go to Atlassian Administration and select your organization.
2. Select Apps > AI settings > Rovo MCP server.
3. Add or remove domains as needed.

Track your usage with the new platform usage page

Organization admins can now monitor their consumption-based pricing and usage through a dedicated platform usage page in Atlassian Administration. This new experience provides a centralized view of how your organization consumes resources like AI credits and indexed objects across Atlassian apps, helping you manage costs and plan for future needs.

1. Go to Atlassian Administration at admin.atlassian.com.
2. Select your organization if you have more than one.
3. Go to Settings, then Platform usage.
4. Select Usage summary to view your current consumption and usage charts.

Control what content gets synced to Rovo from Microsoft Sharepoint

You can now control how Microsoft SharePoint content is synced into Rovo directly from the Admin Hub. This update lets you decide which files to include (by date) and how often they should be updated — giving you more flexibility and helping you keep data fresh with less manual work.

To limit or schedule Microsoft SharePoint content updates in the Admin Hub:

1. Go to Atlassian Administration
2. Go to Settings, and then Rovo.
3. When adding a new Microsoft SharePoint connector:
   • Click Choose content to include.
4. When updating an existing Microsoft SharePoint connector:
   • Click the “…” actions menu on the existing Microsoft SharePoint row.
   • Select Choose content to include.
5. Select the Limit by date tab.
6. Pick a date range for the files you want included.
7. Click Save.
8. Set up your preferred update schedule and save your changes.

Control access to apps with country-based IP allowlisting

Admins can now create IP allowlist policies that restrict access to Atlassian apps by approved countries, as well as IP addresses. This enhancement helps organizations strengthen security and support compliance and migration needs by limiting access based on country of origin across Jira, Confluence, Atlassian Analytics, Compass, and Rovo.

Discover how to create IP allowlist policies to access your apps.

To control access to apps with country-based IP allowlisting:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Device security > IP allowlist.
3. Select Create IP allowlist.
4. Enter a name and select sites or resources for the policy.
5. Select Location as the coverage type and choose from the list of approved countries.
6. Save the policy to activate it.

Event exclusion for third-party app activity logs in audit log settings

We are introducing a new event exclusion toggle for third-party app activity logs in your audit log settings. This feature gives organization admins more granular control over which events are stored in the audit log, helping reduce unnecessary data and ensuring only relevant logs are collected.

Release Date: November 3, 2025 Action Required By: December 1, 2025

If you want to continue receiving third-party app Confluence and Jira API request logs, turn the toggle on in your audit log settings before December 1, 2025. If no action is taken, these logs will be disabled for your organization on that date. You can change this setting at any time.

To manage event exclusion:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Insights > Audit log.
3. Select Settings in the top right corner.
4. Select the Event Exclusion tab.
5. For each event type, use the Action toggle to start or stop storing events.
6. When the warning message appears, confirm your choice.

It may take a few minutes for new activities to appear in the audit log.

Connect Marketplace apps to multiple Atlassian apps

Some Marketplace apps can now connect to multiple Atlassian apps. If a Marketplace app supports this, you can install it once and choose which Atlassian apps—like Jira, Confluence, and Compass—you want to connect it to. You can update these connections at any time in Atlassian Administration.

If your app is compatible with multiple Atlassian apps, you can manage where it is connected in Atlassian Administration.

To manage connections for an app:

1. Go to admin.atlassian.com
2. Select the relevant site.
3. Select Apps in the global navigation.
4. In the Sites section of the lefthand navigation, select the site you’re administering apps for.
5. In the lefthand navigation, select Connected apps. The Connected apps page displays all apps currently installed in your instance.
6. Select View App Details for the app.
7. In the Connections tab, under App connections, you can see all available connections for this app. The Atlassian apps that are connected to are marked with a “Connected” status, and those that have not yet been connected are marked with a “Not connected” status. From this screen, you can use the Connect or Disconnect buttons to add or remove connections with Atlassian apps.

IP allowlisting for Rovo experiences

Admins can now apply IP allowlisting controls to Rovo experiences at the organization level in Admin hub. This helps ensure that only users from approved IP addresses can access Rovo Search, Chat, Bookmarks, and more, improving security for your organization.

To learn more, see Specify IP addresses for app access.

1. Go to Atlassian administration (admin.atlassian.com) and select your organization.
2. Select Security > Device Security > IP allowlisting
3. Create allowlist or Edit an existing allowlist
4. Choose Rovo as the app when creating or editing an IP allowlist.
5. You must have at least one of the following plans to see the option for Rovo
   • Premium plan for Jira, Jira Service Management, Confluence, and Compass.
   • Enterprise plan for Atlassian Analytics.

Access policies: Block mobile browser access

Atlassian Guard now allows organization admins to block access to Atlassian apps from mobile browsers. This new condition-based policy helps you enhance security by ensuring users only access organization content through approved methods, such as Atlassian mobile apps or desktop browsers.

To get started with this change:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > User security > Access policies.
3. Select Create policy.
4. Enter a name and description for the access policy, then select Create.
5. Set the access control to Block, then select Turn on policy.

Assets is now a standalone platform app

To ensure we give our customers a seamless and secure experience, we're moving Assets from Jira Service Management as its own platform app in Atlassian Administration. Here, you can assign specific roles to people as well as manage billing and data residency. Existing permissions and access will be automatically migrated to minimize any disruptions.

Find all users and managed accounts in one place

We’re moving all your organization’s managed accounts into your Users list in Administration, and adding extra information to the user profile of your managed accounts. This addresses the confusion when some accounts appear in both your organization’s Users list and your Managed accounts list, accompanied by different profiles. With these changes, you only have to use the Users list to manage everyone, with filters to help you narrow your results. What are managed accounts?

With this update, the Total users count in your Users list may increase, because your Users list now also contains all managed accounts your organization owns, even if they aren't in your directory. Previously, the count only reflected users in your directory. To get the total users in your directory only, export your users list.

There is no change to the Active users count. It continues to count the number of users who are active or invited in your directory.

This change applies to organizations with the centralized user management experience.

To find your organization’s managed accounts:

• Go to Atlassian Administration. Select your organization if you have more than one.
• Select Directory > Users.
• Filter for Managed accounts using the Account type filter.

A faster way to automatically revoke inactive API keys and tokens (Enterprise only)

Administrators can now add actions in automation rules to automatically revoke inactive API keys and API tokens. You can set the inactivity period for each action, helping you keep your organization’s access secure. (Enterprise only)

To add these new actions to your admin automation rules:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Go to the automation section in your Organization settings.
3. Start creating or editing an automation rule.
4. In the Add an action step, select either Revoke inactive API keys or Revoke inactive API tokens.
5. Set the inactivity period as needed.
6. Save your rule. For best results, use these actions with a Scheduled trigger or select a preconfigured rule from the automation templates library.

Migration intent dropdown for cloud-to-cloud migrations

A new migration intent dropdown has been added to the cloud-to-cloud migration experience in Atlassian Administration. Admins can now specify whether a migration is a test or production migration. This intent is used by Atlassian’s Support and on-call teams to correctly assess incident severity and respond faster when production migrations fail, reducing manual back-and-forth.

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Start a new cloud-to-cloud migration.
3. In the Migration intent dropdown, select whether this migration is a Test or Production migration.
4. Complete the rest of the migration setup as usual.

Invite drawer: Improved group selection

Organization admins can now use an updated group selection experience when inviting users to Atlassian apps. This improvement makes it easier to find and select the correct groups, especially for organizations with many groups or multiple directories, ensuring users are assigned the right access from the start.

To get started with this change

1. Go to Atlassian Administration at admin.atlassian.com.
2. Select Directory, then Users.
3. Select Invite users.
4. In the Add to groups field, search for and select the groups you want to add users to.

Independent customer access settings for Customer Service Management

Admins can now manage customer access settings for Customer Service Management separately from Jira Service Management. This change allows you to enable public signup and anonymous access for your Customer Service Management help center while keeping your Jira Service Management projects restricted to internal or specific external customers. By decoupling these settings, you have more flexibility to tailor the signup experience and help center visibility to the specific needs of each app.

Manage customer access to your channels

To get started with this change:

1. Go to Atlassian Administration at admin.atlassian.com.
2. Select your organization, then navigate to Products.
3. Select Jira apps from the Jira admin settings in the top navigation Settings.
4. Navigate to Customer access within Customer Service Management and Jira Service Management to configure signup and portal access settings independently.

Teams: Custom fields for team profiles

Organization admins can now define and manage custom fields for team profiles in Atlassian Administration. This update allows organizations to capture specific metadata—such as cost centers, locations, or divisions—making it easier to organize, find, and report on teams across the organization. These fields are also searchable and filterable within the teams directory.

To get started with this change:

1. Go to Teams Settings from Teams app.
2. Select Create field and choose a field type, such as Text, Number, Select, or User.
3. Enter a name and description for the field, then select Save.
4. Navigate to any team profile to view or edit the new custom field values.

Connect Marketplace apps to multiple Atlassian apps

Some Marketplace apps can now connect to multiple Atlassian apps. If a Marketplace app supports this, you can install it once and choose which Atlassian apps—like Jira, Confluence, and Compass—you want to connect it to on installation. You can update these connections at any time in Atlassian Administration.

During installation, you can choose which Atlassian apps to connect to, and you can update these connections later in the Atlassian Administration Connected apps screen.

For Marketplace apps, you can check an app’s compatibility with different Atlassian apps at the top of its Marketplace listing.

To install a Marketplace app that is compatible with multiple Atlassian apps:

1. Go to marketplace.atlassian.com.
2. On your chosen app, select the Get it now button for free apps or the Try it free button for paid apps.
3. On the pop-up screen, select the site where you want to install the app, choose the edition, if multiple editions are available, and select which Atlassian apps to connect the app to.
4. Select Review.
5. Review the details for the app and select Start free trial.

Confluence migration: Migrate Confluence from Data Center to Cloud in Atlassian Administration

Organization admins can now migrate Confluence Data Center to Cloud using the migration center in Atlassian Administration. This adds Confluence support alongside the existing Jira migration capability, providing a self-serve experience to plan, run, and monitor Confluence migrations.

1. Go to admin.atlassian.com and select your organization.
2. Go to Data management, then Delta migration.
3. Connect your Confluence Data Center source and create a migration plan.

Improved tables: Enhanced accessibility and features

Atlassian Administration tables now support column resizing, reordering, and pinning. These updates make it easier for admins to manage users, groups, teams, and service accounts across 15 table experiences in Atlassian Administration.

To get started with this change:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Column controls are available across several table experiences in Atlassian Administration, including:
   • Directory > Groups (list and group detail views)
   • Directory > Teams (list and team detail views)
   • Directory > Service accounts (detail views)
   • User profiles (App access and Groups tabs)
   • Apps > Atlassian apps
   • Rovo > Rovo access
3. To try the new controls, open any of these pages and hover over a column header to resize, or select the column menu (⋯) to reorder or pin columns.

Guided migration from commercial cloud to Government Cloud

Eligible administrators can now use Atlassian Administration to copy data from existing Jira and Confluence sites in commercial cloud to Government Cloud with a guided migration flow. This first release supports full data copy only and provides step-by-step validation to reduce manual effort for government customers.

To get started with this change:

1. Log in to Atlassian Administration for Government Cloud.
2. Select Data transfer under Data management.
3. Choose Create transfer plan and select In Atlassian cloud to begin the migration process.

Manage app access to Rovo with blocklists

Organization admins can choose which apps shouldn’t have access to Rovo features, using the new Rovo access page in Atlassian Administration. This update replaces the allowlist approach in the AI-enabled apps page with a blocklist, making it easier to see and manage where Rovo features are disabled across your organization.

How to manage Rovo access

To get started with this change:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Rovo, then Rovo access.
3. In the Rovo access page, select Add app, then choose which apps to block from accessing Rovo features.

Use data security policies for Jira Product Discovery

Organization admins can now use data security policies to manage and protect content within Jira Product Discovery.

To use data security policies for Jira Product Discovery:

1. Go to Atlassian Administration at admin.atlassian.com.
2. Select Security, Data protection, then Data security policy.
3. Select an existing draft control or create a new one.
4. When adding override, select your Jira Product Discovery spaces.

Full site scan for Jira and Confluence

Full site scan lets organization admins and Guard Detect scan all Jira and Confluence content to find sensitive data and export results for follow‑up. Full site scan is available to Guard Premium customers and can be launched from the Guard admin experience under the Content scan tab in the header.

When you start a content scan, you can select what you’d like to scan. Make sure you’ve set up any custom detections you wish to scan before you start a content scan.

1. In Guard Detect, select Content scan from the header.
2. Select Start new scan.
3. You’re presented with a dialog box, read the information, check the checkbox to confirm you’ve understood it, then select Next.
4. Select the option that suits your needs — either all Jira and Confluence apps, or your selection of specific workspace.
5. Select Start scan. A dialog box will confirm the scan has been created.
6. Select Close.

Your scan will be listed in the scan history.

Application links: Create links in Atlassian Administration

Organization admins can now create application links for Jira Cloud in Atlassian Administration using Cloud Connector. This new creation experience simplifies the setup process by removing the need to manually copy and paste credentials between Atlassian Cloud and Data Center apps.

1. Go to Atlassian Administration.
2. Select Settings, then Application links.
3. Select Create link and follow the prompts to connect your Jira Cloud site to a Data Center instance using Cloud Connector.

Manage Rovo agents from one place

Organization admins can now manage and govern Rovo agents from a central location in Atlassian Administration. This update provides visibility into all agents across your organization and allows you to set default access policies for newly created agents. By centralizing these controls, you can ensure better security and compliance without searching across individual sites.

To get started with this change:

1. Log in to Atlassian Administration at admin.atlassian.com.
2. Select Rovo, then select Agents.
3. Review the Agents tab to see all agents across your organization, filtered by site.
4. Select the Access tab to set a default access policy for newly created agents.
5. Select an individual agent to manage granular app and group permissions on the Agent details page.

Connected apps: End-of-support warnings for Connect apps

Admins and users will now see in-product warnings for apps built on the Connect framework to prepare for its upcoming end-of-support. These notifications in Jira, Confluence, and Atlassian Administration help you identify affected apps and plan your migration to Forge.

1. Go to Atlassian Administration, then select your organization.
2. Select Apps, then Connected apps.
3. Look for warning banners at the top of the page or within specific app details to identify apps requiring action.
4. For end users, look for dismissible banners within app iframes on Jira issues or Confluence pages.

Rovo: Improved navigation for AI controls in Atlassian Administration

Rovo AI settings have been reorganized in Atlassian Administration to help organization admins find and manage features more efficiently. This update groups key Rovo AI capabilities into a single, dedicated section in the sidebar.

To get started with this change:

1. Log in to admin.atlassian.com.
2. Select your organization if you manage more than one.
3. Select the new Rovo section in the sidebar.
4. Access and manage your Rovo access, Atlassian MCP server, Rovo settings, and Insights from the updated navigation.

Connect end-of-support warnings for public apps

Identify which public apps are affected by the upcoming Connect end-of-support milestone with new in-app warnings. These messages provide guidance on migrating to Forge to help you avoid potential service interruptions.

To view the list of impacted apps:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. From the sidebar, select the site and then Connected apps.
3. Look for warning banners at the top of the Connected apps list and within individual app details for any apps built with Connect.

Manage updates to Talent with release tracks and app updates

Talent can now be put on the bundled release track, so you can have more time to prepare and plan for changes to the Talent app. What are release tracks?

To schedule monthly changes for Talent:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Apps > Release management > Release tracks.
3. Look for Talent in the list of supported apps and select the change track option.
4. Choose the bundled release track to schedule monthly updates.

To view upcoming Talent changes:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Apps > App updates.
3. From the App filter, select Talent.

Guest role available for Jira

Collaborate with external partners and contractors by inviting them to Jira as guests. The guest role lets you provide restricted access to specific spaces in Jira without consuming a paid seat, helping your team work with external contributors while you maintain security and control.

How to invite guests to Jira

Mobile Security: Toggle App Trust for Intune MAM policies

Organization admins can now enable App Trust when creating or editing Microsoft Intune mobile app management (MAM) policies in Atlassian Administration. This change allows you to manage IP access requirements alongside your existing mobile security settings, providing more granular control over how managed users access Atlassian apps on mobile devices.

To get started with this change:

1. Log in to admin.atlassian.com.
2. Select your organization, then go to Security and Mobile security.
3. Choose Intune MAM policies, then select an existing policy to edit or select Create policy.
4. In the Select IP access section, select the App Trust checkbox to enable the setting.
5. Select Save or Next to apply your changes.

External sites: Control access to approved sites

Organization admins can now create an “External sites” policy in Atlassian Administration to limit which Atlassian sites users can access from their corporate network. This security feature helps prevent data exfiltration to unauthorized sites by ensuring users only interact with approved Atlassian apps and sites while on your network.

This feature requires a Atlassian Guard Standard or Atlassian Guard Premium subscription.

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Go to Security, then Device Security, then External sites.
3. Create a new policy and add the domains for the external Atlassian sites you want to approve.
4. Configure your corporate proxy to inject the Atl-Tenant-Restriction-Policy header into requests destined for Atlassian.

Personalize reliability monitoring with System health

System Health is now generally available. Org admins can now access a personalized dashboard showing app status, site-level incidents, email alerts, and postmortems – free for all cloud plans.

To get started with this change:

1. Log in at admin.atlassian.com and select your organization.
2. Go to Insights, then select System Health.
3. Optionally enable email alerts via Notification Settings.

Reset your sandbox to a clean state

You can now reset a sandbox to its original, empty state. This allows you to quickly clear all data and configuration from your sandbox without having to delete and recreate it, saving time when starting new testing cycles or configuration changes.

To get started with this change:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Apps, then Sandboxes.
3. In the table, find the sandbox you want to reset.
4. In the Actions column, select more actions (…) then Reset.

Audit logs: Search by authentication type and on behalf of users

Organization admins can now filter audit logs in Atlassian Administration by authentication type and by actions performed on behalf of other users. This update helps admins more effectively monitor security events and troubleshoot access issues across their Atlassian organization.

To filter audit logs:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Go to Security, then Audit log.
3. Use the new Authentication type and On behalf of filters to refine your search results.

Merge teams to organize your organization

Admins can now combine multiple teams into a single team within Atlassian administration. This helps you clean up duplicate teams and ensure your organization remains organized and easy to navigate.

Merge teams

1. Go to Atlassian administration.
2. Select Directory, then Teams.
3. Choose the teams you want to combine and select Merge team.

New layout and detailed pages to manage connectors

Organization admins can now manage connectors in Atlassian Administration using a new table layout and dedicated detail pages. These updates help you monitor sync status and configuration details for your teamwork graph and search data.

To view this change:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. From the left navigation, select Apps, then select Connectors.
3. Select a connector from the list to view its new detail page.

Agent profiles: Apply default settings

Organization admins can now apply default settings to agent profiles in Atlassian Administration. This change helps admins maintain consistency across their service teams and saves time when setting up new agents.

1. Go to Atlassian Administration, then Rovo.
2. Select Agents.
3. Choose an agent to view their Agent Profile.
4. From the dropdown menu at the top, select Add default access.

UI update: Manage Rovo MCP server access from the Permissions tab in Atlassian Administration

We’ve updated the interface for managing Atlassian Rovo MCP server access in Atlassian Administration. This visual refresh includes a new user consent screen to improve transparency when modifying access, while ensuring all your existing controls and permissions remain unchanged.

1. Go to Atlassian Administration, then Rovo.
2. Select Rovo MCP server, then Permissions.
3. Choose the user or group you want to modify.
4. Follow the prompts on the user consent screen to complete the changes.

Bulk remove multiple members from groups

Organization admins can now save time by removing up to 500 members from a group at once in Atlassian Administration. This update to the Group Members table allows admins to manage large groups more efficiently without the need to remove members individually.

To remove multiple users in bulk:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory, then Groups.
3. Open a group and go to the Members tab.
4. Use the checkboxes to select the members you want to remove.
5. Select Remove from the bulk actions toolbar at the bottom of the screen.
6. Confirm the removal in the Remove members? dialog.

User access requests: Machine learning suggestions

Organization admins can now use machine learning suggestions to help prioritize and manage user access requests in Atlassian Administration. By leveraging a core machine learning model, the app identifies and surfaces requests that are highly likely to be approved, allowing admins to focus on high-signal actions and reduce cognitive load when managing large volumes of requests.

1. Go to Atlassian Administration (admin.atlassian.com).
2. Select your organization, then go to Apps, then User access requests.
3. The access requests will be Sort by: Suggested order by default, ranked by their likelihood of approval.

Build automation rules with Rovo

Save time by using Rovo to generate automation rules in Confluence, Jira, and Atlassian Administration. You can now describe the automation you need in plain language, and Rovo will build the rule for you, making it easier to streamline your workflows without needing to manually configure every step.

To view this change in Jira:

1. Open Jira.
2. Navigate to the space where you want to add the automation rule and select Space settings.
3. Select Automation from the sidebar.
4. Select Create rule, then select Create with Rovo.
5. Describe the automation rule you want to create in the text field and follow the prompts to generate your rule.

Improvements to access request management

We've made improvements to how you handle access requests in Atlassian Administration. Request access emails are now more descriptive, making it easier for admins to understand and act on incoming requests. We've also made it easier to stay on top of pending requests directly from the user list.

1. Log in to your Atlassian organization.
2. Select Administration from the app switcher.
3. Go to the Users section to view pending access requests.

Design coherence improvements including clearer labelling and purposeful motion

We’re modernizing the experience across Atlassian apps with UI improvements that make moving between apps, features and pages feel seamless. These updates to labelling, motion and shapes help you and your team get work done in a familiar, predictable way.

These improvements are rolling out progressively across apps from July 2026, beginning with with the apps listed here. Open any of your Atlassian apps, such as Jira or Confluence, to get started.

Automation: New settings panel in the rule builder

We’ve moved several configuration options in the automation rule builder to a dedicated settings panel. This change helps you manage your automation rules more effectively..

To get started with this change:

1. Open an existing automation rule or create a new one.
2. Select the More menu (represented by three dots) in the rule builder.
3. Select Settings to open the new panel and manage your rule configuration.

Agents: Configure in-context settings

Save time and stay in your workflow by configuring enabled agents directly within the agent install dialog in Jira. This update keeps you in the same dialog after installation — no new windows or tab switches needed — so you can configure, start a session, or configure later without leaving the current context.

1. Open your project in Jira and navigate to the agent marketplace or browse agents.
2. Find the agent you want to use (e.g., Claude for Jira, Cursor) and click Install.
3. Once installation completes, the configure screen appears directly within the agent install dialog — no new window opens.
4. Fill in the required configuration details within the dialog.
5. Click Start session to begin using the agent immediately, or click Configure later to return to the browse agents view and configure at a later time.

All new embedded Marketplace experience: a better way to discover and consume apps

Save time and streamline your workflow with an enhanced Marketplace experience in Jira and Confluence. The new information architecture and tile system make it easier to discover apps and find the information you need.

1. Open the Jira or Confluence app.
2. Select Apps in the left-side navigation bar.
3. Choose Explore More apps to explore the new experience.

Plan work items with Rovo

Improve a work item in one click with a new out-of-the-box Rovo agent in Jira. This ready-to-use agent scopes your work item for you. It gathers relevant context, asks a few clarifying questions, and suggests a stronger description you can accept. There's no setup, and no need to pick an agent first: scoping your work is now its own standalone action.

1. Open a work item in Jira.
2. Select Plan work item from the Improve work item dropdown, or from the agent empty state.
3. Answer the agent's clarifying questions as it scopes the work.
4. Review the suggested description and accept it to update your work item.

Third-party agents: Choose a repository

Save time when using third-party agents in Jira by choosing the specific repository you want the agent to use. By selecting a repository before the agent starts its task on a work item, you ensure the agent has the right context and avoid unnecessary planning steps.

1. Open a work item in Jira.
2. Select a third-party agent to perform a task.
3. Select the repository you want the agent to work with from the list or type one in.

Improve sprint planning with AI-powered analysis of sprint insights

Save time and improve sprint planning in Jira with AI-powered analysis of your sprint insights. The Jira Delivery Agent now summarizes your sprint data, identifies potential risks, and recommends next actions to help your team stay on track.

To perform an AI-powered analysis of your sprint:

1. Open your board or backlog in Jira.
2. Select the Insights panel.
3. Find a specific insight, such as Sprint commitment or Work type breakdown.
4. Select Analyze to open the Jira Delivery Agent and view the summary and recommendations.

Review work items that need your immediate attention

The Recommended tab in Jira now surfaces work items that need your immediate attention, such as items you're blocking, items blocking you, or work that's recently unblocked or stuck. These new signals help you stay on top of work that’s impacting your team's momentum.

To view this recommendations:

1. Go to the For you page in Jira.
2. Select the Recommended tab.
3. Review the new cards for work items that are blocking others, blocked by others, recently unblocked, or stuck.
4. Select a card to view the work item details and take action.

New Jira tools in the Atlassian Rovo MCP Server

The Atlassian Rovo MCP Server adds more than 20 new Jira tools. AI agents and MCP clients can now work directly with boards and sprints, attachments, comments, worklogs, change history, users, statuses, dashboards, entity properties, work item watching, and project administration.

1. Connect your MCP client, such as Claude, Cursor, or VS Code, to the Atlassian Rovo MCP Server, then authenticate to your Atlassian site.
2. Confirm the client is using the current Jira v2 tool set.
3. Ask the agent to perform an action in Jira that uses one of the new tools, such as “show the work items on my team’s board” or “attach this file to ABC-123.”

The agent selects the matching tool, such as getJiraBoardIssueData or uploadAttachmentToJiraIssue, and returns the result.

Email option for agentic automations

Agentic automations in the Summary view now include a option to receive updates through email when Confluence is not linked. This ensures that Jira Delivery Agent can still deliver responses using emails instead of Confluence reports.

To view this change:

1. Open Jira and navigate to the Summary view of your space.
2. From the section that displays the agentic automations banner, select Set up next to any automation.
3. This will begin the wizard set up for one of the 3 agentic automations: Delivery health check, Stakeholder status update, Daily standup.
4. You’ll see the Send email step in the workflow where you can configure the email details. Note that you’ll see the email option only if you don’t have Confluence subscription or access.

View triage agent recommendations in the Next best actions section

Save time by viewing and actioning triage agent recommendations directly from the Next best actions section in Jira. When the triage agent is configured as part of a transition in your workflow, it automatically suggests field updates that now appear at the top of the work item view for better visibility.

To view this change:

1. Open a work item in Jira that has transitioned to a status where the triage agent is configured.
2. Locate the Next best actions section at the top of the work item view.
3. Review the suggested field updates, such as changes to the work item type or other standard fields.
4. Select the checkmark icon to accept a recommendation or the dismiss icon to remove it.

Agents: Manage sources, prompts, control and triggers in your spaces

Jira admins can now manage AI-powered agents directly within their space settings. This new page allows you to view which agents are active in your space, understand their workflow triggers, and configure space-level prompts and controls to ensure AI workflows and responses are tailored to your team's specific context.

To get started with this change

1. Open your Jira space.
2. Select Space settings from the sidebar.
3. Select Agents to view the active agents and their configurations.
4. Adjust the context settings to suit your space requirements.

Human-recongnizable names for Assets objects in JQL

We've updated Jira Query Language (JQL) so that Assets objects now display as human-readable names instead of Atlassian Resource Identifier (ARI) values. This makes writing and validating JQL faster and easier.

To view this change:

1. Open your Jira app and navigate to Filters.
2. Enter a JQL query that includes Assets object operands.
3. View the improved results containing the Asset Objects' names.

Fields: Rich text support for field descriptions

Jira admins can now use rich text to create and edit field descriptions in Atlassian Administration. This change allows for better formatting and clearer instructions for users, while also increasing the character limit to 4,000 visible characters (up from 255).

1. In Jira, select the Settings icon in the top navigation.
2. Go to Work items, then Fields.
3. Select Create field or select Edit on an existing field to use the rich text editor for the description.

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

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.

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.

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

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

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.

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.

Jira Plans: Drag and drop field columns

You can now drag and drop field columns in the timeline view to instantly reorder them. You’ll also find a More actions menu in each column header to quickly remove or reorder columns, so you can make adjustments without interrupting your workflow.

To reorder columns in your timeline, select and drag a column header to your desired position. For more options, select the More actions (...) menu in the column header to reorder or remove columns.

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.

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.

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.

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.

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

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.

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.

Manage views directly from the space navigation

Project admins can now add or remove views directly from the space navigation, giving them more flexibility to customize the space to suit their team's need.

To add a view, select the plus icon + in your space navigation and choose which view you want to add.

To remove a view, select the tab options menu (...) next to the tab name, and then select Remove.

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:

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

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 and organize work by Focus area in Jira Plans

You can now view, filter, and group work by Focus area directly in Jira Plans. This integration lets you see which Focus areas are linked to your Jira work items, making it easier to align and organize your planning. The Focus area field is read-only for now and available to select customers.

To see and use Focus areas in your Jira Plans:

1. Open a plan in Jira Plans where Focus is provisioned for your site.
2. Look for the new Focus area field in your plan’s fields.
3. Use the filter or group options to organize work by Focus area.
4. If you don’t see this feature and have both Focus and Jira Plans, reach out to your Atlassian contact or the #focus-area-in-plans Slack channel to request access.

Software projects: More context on completed and open issues when you complete a sprint

We’ve added extra details to help you understand the status of all issues whenever you complete a sprint in a Jira software project. When you select Complete sprint, we’ll tell you which board columns contain completed issues, and which ones contain open issues. This can help you decide if you need to move any issues around on the board before you complete the sprint.

Field configuration schemes: Field limits for optimized performance

To ensure your Jira apps remain fast and reliable, we’re introducing a limit on the number of fields you can add to a field configuration scheme. This change helps maintain site performance by preventing overly complex configurations that can slow down your experience.

If you have an existing support ticket regarding this change, please refer to the latest communication from support for the most up-to-date information applicable to your instance.

To get started with this change:

1. Go to Settings, then Work items.
2. Select Field configuration schemes.
3. View your existing schemes and try to add a new field configuration to a scheme.
4. If a scheme is already at the limit, Jira will prevent you from adding more fields to it.

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

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.

Customize project backgrounds with images and color gradients

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

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. Next to your project's name in the sidebar, select More actions (•••).
2. Select Set project background.
3. Select a theme.

To set a theme in a team-managed project, you can follow the above steps, or:

1. Select More actions (•••) next to the project name.
2. Select Set project background.
3. Select a theme.

Limits for work item types and fields

We’re introducing limits and guardrails for work item types and fields to improve site performance and scalability. You’ll see a warning if a space exceeds 700 fields or 150 work item types. To keep your site running smoothly, you won't be able to add more until the space is back within these limits.

Understand data limits and guardrails

To get started with this change:

1. Open Jira.
2. Select Settings (cog icon) in the top navigation bar.
3. Under Jira admin settings, select Work items.
4. Select Work item type schemes or Field configurations.
5. Look for a warning message on schemes that exceed the recommended limits.
6. Use the Site optimizer to identify and remove unused fields or work item types to bring your space back within the limits.

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.

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.

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

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.

Prompt for Jira users to return to Confluence after inactivity

If someone has access to both Jira and Confluence but has not used Confluence in the last 28 days, they will now see a flag in Jira encouraging them to rejoin their team in Confluence. This flag includes a direct link to Confluence Home and an option to dismiss the message.

To see and interact with this new flag in Jira:

1. Log in to Jira with an account that also has access to Confluence.
2. If you have not been active in Confluence for at least 28 days, look for a flag at the top of your Jira screen.
3. Select "Go to Confluence" to visit Confluence Home, or select the "X" icon to dismiss the flag.

Add comments when flagging work items in Jira

In Jira, you can now add a comment whenever you flag a work item, no matter where you do it. Previously, you could only add a comment from views like the board, backlog, or the command palette in the work item view. This update adds the same comment prompt when you add or remove a flag from the More actions (•••) menu in the work item view, giving your team consistent context about why work is flagged as at risk.

To get started with this change:

1. In Jira, open the work item you want to flag.
2. Add or remove a flag from any supported view (board, backlog, command palette, or work item view).
3. When prompted, add a comment to explain why the work is at risk.
4. Save your changes.

Approvals are coming to Jira

We’ve added native approvals for company-managed projects using Premium editions in Jira, allowing teams to streamline reviews and sign-offs directly within their workflows. Whether you're managing content reviews, code changes, or project deliverables, you can now set up approval steps that ensure proper governance and accountability.

The approvals feature includes:

• Custom approval fields and approver roles
• In-workflow approval steps and email notifications
• Approval tracking and audit history
• Support for single or multi-step approval chains

Create personalised onboarding experiences in Jira

Admins can create personalized welcome experiences with custom content, links, and branding, delivering tailored guidance to new users so they understand company context during their first-time onboarding.

To access and use the new custom onboarding targeting gate in Jira:

1. Sign in to your Jira site.
2. As a site admin, navigate to custom onboarding from Jira admin settings → products
3. Look for the new custom onboarding option to create, manage and get data insights on custom onboarding

Automate Jira work item approval with smart values

We've introduced new smart values to refer to the manager of a Jira work item reporter or assignee. For example, you could use these smart values to automatically set the approver of a Jira work item to the assignee’s or reporter’s manager.

The new smart values include issue.reporter.manager or issue.assignee.manager.

1. Check the manager you want to refer to is set up through User Provisioning.
2. Set up an approver workflow for Jira or Jira Service Management.
3. Open the automation rule builder in Jira or Jira Service Management.
4. Select a trigger for your rule.
5. Add the action Edit Work Item and select More Options.
6. Add the smart value in the Additional Fields section as code.
7. Once the trigger you set up is triggered, the manager of the assignee is added as the approver.

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.

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

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

AI-powered snippets for Confluence links in Jira

To provide you immediate context on your linked Confluence pages, we've replaced the standard link previews with AI-generated summaries in Jira. This means you can access key information from Confluence without switching between apps, saving you time and keeping you focused on your work.

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.

New automation action: Add stakeholders to incident

You can now automatically add stakeholders to incidents using the new Add stakeholders to incident action. This helps streamline communication and ensures the right people are kept informed during incident response.

To give the new automation component a try:

1. Navigate to either project automation (in Jira) or global automation.
2. Create a new rule, or edit an existing rule.
3. Add the new Add stakeholders to incident action to your automation rule.
4. Configure the action to specify which stakeholders to add when the rule is triggered.

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.

Jira: More ways to create and link work

You can now create subtasks and link to existing work within a work item. This applies to company-managed and team-managed projects.

1. Go to your board
2. Select a work item then go to either the Child work items or Subtasks or Linked work items section.
3. From there you can either Add subtask or Add child work item or Add linked work item.

A better way to manage threaded comments in Jira

This update introduces the ability to show and hide threaded comments in Jira. This makes it easier to focus on the most relevant conversations, and reduces visual clutter when working with long comment threads.

To try out the new threaded comment show/hide feature:

1. Open any work item in Jira that contains threaded comments.
2. Select Hide replies to collapse replies within that thread. Select Show more replies to expand them again.

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.

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.

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.

We’re merging List and All work into one powerful view for all teams

Now available for Premium and Enterprise customers

Jira now combines the List and All work views into one powerful, unified view for managing work items. It's simply called List. Learn more about the change in our Community announcement.

To use the new merged experience:

1. Open your project in Jira.
2. Go to the main navigation and select the “List” tab (previously “List” or “All work”).
3. Explore the combined features, including hierarchy, grouping, inline editing, and more — all in one place.

Rovo Dev in Jira: Build and iterate on code directly in Jira

Pair up with Rovo Dev to transform your Jira work items into working code.

Start coding instantly in a secure, cloud-based session in a dedicated, sandbox environment. Rovo Dev in Jira uses your work item and your team’s knowledge from Jira, Confluence, your codebase, and more to generate code. When you’re happy with the result, create a pull request directly from the sandbox to merge your changes. Find out more about Rovo Dev in Jira

You can also use Rovo Dev actions in automations to automatically generate code for repetitive tasks at scale, so your team can focus on more valuable work. Find out more about Rovo Dev in automations

To use Rovo Dev in Jira:

1. Open your work item and select Generate code in the Rovo Dev section.
2. Select a repository where you want to generate the code.
3. Enter a prompt to provide more context or add a saved prompt.
4. Select the settings icon to define code and environment settings for your Rovo Dev sessions.
5. Select Generate code.

To use Rovo Dev in automations:

1. In your Jira space, select More actions (…) next to your space name, then select Space settings.
2. In the sidebar, select Automation, then select Create rule.
3. Add a trigger, component, and the Generate code automation action.
4. Select a connected repository and configure the branch and pull request options.
5. Enter a prompt to provide more context.
6. Select Next and then Turn on rule.

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.

A simpler left sidebar for new Jira users

We're simplifying the left sidebar for people who are new to Jira. This update reduces the number of items shown in the sidebar, making it easier to get started and find what you need.

To see the simplified sidebar:

1. Sign in to Jira as a new customer.
2. Look at the left side of your screen to view the updated sidebar.
3. Explore the available options to start your work.

A full-height sidebar for better navigation

The sidebar now spans the full height of your Atlassian app, making the navigation more seamless, and improving the overall discoverability and accessibility.

1. Open the Atlassian app.
2. Observe the left sidebar, which now extends from the top to the bottom of your window.

Field schemes: A new way to manage fields

Jira admins can now use field schemes to manage which fields are available and required for different work types. This new experience replaces the legacy field configurations and field configuration schemes, providing a more intuitive way to ensure projects only include relevant fields.

To use field schemes:

1. Go to Jira settings, then Work items.
2. Select Field schemes from the sidebar.
3. Choose an existing scheme to edit or select Create field scheme to start a new one.
4. Use the Advanced settings sidebar to specify which work types a field is available or required on.

A more accessible way to create work items on the plan timeline

The work item creation experience on the plan timeline is getting a new design. Instead of using a nested dropdown menu, you will now see a popup with fields. This update is designed to address accessibility concerns and make it easier for everyone to create work items. A new Create button has also been added to group headers, allowing you to create work items directly within a group.

To use the new work item creation popup on the plan timeline:

1. Go to your plan timeline in Jira.
2. Select the option to create a new work item.
3. Interact with the new popup window to fill in the required fields and complete work item creation.
4. A "Create another" checkbox has been added to the popup, enabling the opening of the inline work creation feature, once the work item has been created

Bulk select up to 1000 work items in the work item navigator

We’ve made it easier to manage more work at once in Jira with the new bulk operations experience. Now, when you select work in the List view or the All work tab, you can select up to 1,000 work items that match your filters with a single click from the bulk operations toolbar, even if they aren’t all loaded on your screen. Previously, you could only select 50 items at a time.

To bulk select multiple work items:

1. Apply your desired filters in the List view or All work tab in your Jira space to find work you’d like to bulk change.
2. Select a work item, by either clicking the top left checkbox or the “Select all” button in the toolbar.
3. The first 1,000 issues or the total work items matching your filters will be selected automatically (whichever is higher).
4. You can now perform bulk actions, like edit, delete, or move, on all selected items at once.

Jira ‘projects’ will soon be renamed ‘spaces’

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.

As part of these efforts, the term project will soon be replaced with space across all Jira Cloud products, including Jira Service Management and Jira Product Discovery.

• Read more about these changes on the Atlassian Community

This change builds on previous terminology updates, like the transition to 'work' in Jira.

Generate and refine work items from chat

You can now open a full-screen canvas from Rovo Chat in Jira to describe your goals, add context, and have Rovo suggest a breakdown of work items. Review and refine these items before adding them to your Jira space, making project planning faster and more approachable for all teams.

To get started with this change:

1. Open Rovo Chat in Jira.
2. Ask Rovo to create work items
3. Select Preview in Rovo Chat’s response to open the canvas.
4. Review and edit the suggested work items in the canvas.
5. Add the finalized work items to your Jira space.

Connect work items directly to projects

Jira and the Projects app are now natively integrated. A built-in Project field is now available by default on software and business Jira spaces, making it easier to connect work items to projects and track them across your organization.

1. Go to a software or business space in Jira.
2. Open an existing work item or create a new one.
3. Select the Project field.
4. Select an existing project from the list, or create a new one from the picker.
5. To view linked work items, go to the project in the Projects app and check the sidebar.

Unifying Confluence and Loom resources into the Attachments section

Jira now brings Confluence pages and Loom videos into one unified Attachments section, making it easier to manage all your resources in one place. This streamlined experience reduces clutter and helps teams collaborate more efficiently by providing quick access to important documents and videos.

To use the new Attachments section:

1. Open a Jira work item.
2. Go to Attachments to view files, Confluence pages, and Loom videos in one place.
3. Select + Add to add attachments.
4. Preview, add, or unlink Confluence pages and Loom videos directly from Attachments.

Export work item details to Excel directly from the work item view

You can now export work item details directly from the work item view in Jira to Excel.

To export a work item's detail to Excel:

1. Open the desired work item in Jira.
2. Select on the More actions menu.
3. Select the Export option in the work item view.
4. Choose Excel to download the work item details.

Find and add responders in the incident search bar

You can now find and add responders in the incident search bar. The incident sidebar introduces advanced search and filtering options, along with an intuitive interface to help you quickly find and add the right responders.

To find and add responders in the incident sidebar:

1. Open an incident where you want to add responders.
2. Go to the sidebar and select Add responder.
3. Use the search bar to find people, teams, or services by name or filter options.
4. Select the responder you want to add from the improved results list.

See relevant work items in the All work tab

You can now see work items that match your most recently used filters when you visit the All work tab for a Jira project (soon to be 'space').

To see these work items in the All work tab:

1. In your Jira project, select the All work tab
2. Apply filters on work items that are relevant to you.

Assign work to agents in Jira

You can assign work to agents, @mention them in comments, and trigger them in your Jira workflow transitions - so they help draft, summarize, and get work done where it’s tracked.

Note that this is an Open Beta release, and the feature won’t yet be available for Jira Product Discovery, Jira Service Management or Jira Service Desk.

Adding an agent

To add an agent:

• Go to the app switcher in the left top navigation.
• Select Studio, then Agents

From there, you can browse and install an existing agent, or create a new agent. Once added, you need to enable the agent to collaborate with you. You'll only need to do this once per agent.

To enable the agent for collaboration:

• Select the agent you’ve just added.
• In the left-hand navigation, scroll down to the Configuration section.
• Select Surfaces, then turn on the toggle for Work item.

Note that GitHub Copilot coding agent, the first of many partner agents, is also coming soon.

Assigning work to an agent

To assign work via the assignee field:

• Open the relevant work item.
• In the assignee field, select the AI agent you want to work with.
• The agent will use the information in the work item e.g. description, and begin working on the assigned task. You’ll see agent activity and updates within the work item – they’re only visible to you (until you choose to share the final output).

Agent Collaboration

You can also trigger an agent to collaborate with you on work. There are three ways to do this:

1. @Mention in a comment

• Open the relevant work item.
• Leave a comment @mentioning the agent that you’d like to work with.
• The agent will use the comment and information in the work item e.g. description, and begin working on the assigned task. 

2. From a column on a board

In team-managed software spaces:

• Go to board view.
• Select More actions (…) in the top right of your chosen column.
• Select Add agents. Once you’ve added an agent, they'll automatically start working on anything that you move into that column.

The agent won’t work on tasks someone else in your team moves into that column.

3. From the workflow editor

Make sure the following is set up first:

• Your space admin has workflow permissions.
• Rovo is enabled along with Rovo permissions,
• Agents have been turned on in Studio.

Team-managed spaces

1. On space sidebar, go to your space's More actions (…) and select Space settings.
2. Expand Work types and navigate to the work type screen (Task , Epic , Bug , etc)
3. On the right hand corner, select Edit workflow.
4. On the workflow editor, select desired transition to add agent to and select Add rule.
5. From the add rule screen, select Trigger agent action.
6. Add agent from the dropdown and an optional custom prompt, then select Add.
7. Finally, select Update workflow and Save once you’re happy with your changes.

Company-managed spaces

• On space sidebar, go to your space's More actions (…) and select Space settings.
• In Space settings, select Workflows.
• Find the workflow you want to edit and select Edit workflow.
• On the workflow editor, select desired transition to add agent to and select Add rule.
• From the add rule screen, select Trigger agent action.
• Add agent from the dropdown and an optional custom prompt, then select Add.
• Finally, select Update workflow and Save once you’re happy with your changes.

Tracking an agent’s work

If you choose to assign work to an agent, their work will only be visible to you. The agent will work with you so you can refine the output, expand or decrease the scope and check everything. Once you’re happy, you can choose to share the agent’s work with teammates – as a comment or an attachment in the work item itself.

Improved commit message for Git commands in software projects

We've updated the Git commit message to include the work item summary, making it easier to create commits without manually adding work item details.

To use the updated commit message:

1. Go to your Jira software project.
2. Open a work item.
3. In the development field, select Create commit.
4. Select Copy to copy the updated Git command, which now includes the work item summary.

Create and configure formulas with a new custom field type

We're introducing a new formula custom field type for team-managed spaces. Space admins can create and configure this field for any work types. This formula will automatically calculate its output in real time on each work item. And if you have Rovo enabled, you can use it to write formulas using natural language or get help correcting any errors in your formula syntax.

In the coming months, we'll add more capabilities to this field, including support for date and time, text outputs, functions and conditions as well as compatibility with company-managed spaces.

New reminder digests for comment mentions

Jira will now send you reminder digests for comment mentions you haven’t responded to, helping you stay on top of important conversations and ensuring nothing slips through the cracks.

Users can turn this off by following the link on the email, or by going to Personal settings, then Digest notifications.

On-call feature is leaving soon

We’re deprecating the legacy On-call feature, which will be removed on January 12, 2026. You can move to Jira Service Management to manage your on-call schedules.

Read more about managing on-call in Jira Service Management

Modify work types from your board

Admins can add and edit work types directly from their board. This feature is available for team-managed projects.

To add work types in your board:

1. Select Add work type in the work type dropdown.
2. Fill in any required fields in the form and select Add.

To edit work types in your board:

1. Select Edit work type in the work type dropdown.
2. Fill in any required fields in the form and select Edit.

Classification rules and new classification settings

Organization admins can now configure classification rules to automatically apply data classification levels to content in Jira and Confluence based on detected sensitive data. Using detections from Guard Detect — including custom detections — admins assign classification levels to detections and apply them across their organization, to both new and existing content objects. New settings give admins control over whether whether users can update content object classifications, and whether users can update content object classifications set by rules.

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security, then select Data protection, and then select Data classification.
3. Select the Classification rules tab, then create rules that assign classification levels to detections.
4. Select the Settings tab to configure whether users can update classification levels, and whether users can update classification levels set by rules.

Making it easier to find and add fields to the All work view

We’ve updated the All work view so fields now follow the configuration of the space you’re in. The column selector, visible columns, and CSV exports now hide fields that aren’t part of your current Jira space, reducing noise and keeping you focused on the work that’s actually relevant to you.

To view this change:

1. Open a space in Jira.
2. Select the All work tab.
3. Select Configure columns (three vertical columns icon).
4. Only columns that are associated with your space will now be appear in the list.

A better way to improve descriptions with Google Docs links

You can now use Google Docs links when improving work item descriptions. This update makes it easier to bring in content from your favorite document tool to help you write better work item descriptions.

To use Google Docs links in the description improver:

1. Open a work item where you want to improve the description.
2. Paste a Google Docs link into the description field.
3. Select Improve description.
4. Follow the prompts to generate an improved description using your linked Google Doc.

This functionality is also available while creating a new work item.

A unified and more powerful timeline for software spaces in Jira

We’re upgrading the Jira timeline to help you plan and track work with more clarity. This update brings a consistent experience, making it easier to manage everything from high-level epics to individual subtasks in one view.

You can now view and manage all work items, including subtasks, directly on your timeline. This update also introduces inline editing for key fields and customizable bar colors to help you organize your work visually.

To customize your timeline view:

1. Go to your Jira software space and select Timeline in the space navigation.
2. Select View settings at the top right of the timeline view.
3. Select the Show inline hierarchy toggle to choose how you want to see your filtered work items.
   1. When Show inline hierarchy is on:
      1. Work items are shown in a two-level hierarchy, with child work items displayed under their parent.
      2. Subtasks and work items without an epic-level parent are hidden.
   2. When Show inline hierarchy is off, filtered work items are shown in a flat list instead.
4. Use the Start hierarchy from dropdown to select your preferred top-level work item. If your space only has epic-level work items and below, this control isn't shown.
5. Select your preferred Bar color to display items in different colors based on their status or epic-level parent.
6. Select checkboxes to update multiple work item fields at once using the bulk edit toolbar.

To update work items directly:

1. Go to your Jira software space and select Timeline in the space navigation.
2. Select the Assignee, Status, or Summary field on any work item in the timeline view.
3. Enter your changes to update the information instantly without leaving the view.

Jira Plans - Easier setup when creating new plans

We've redesigned the setup experience when you create a new plan. This guided flow makes it easier for you to choose work sources, teams, and field columns so your plan is aligned with how your teams work from the start.

To create a new plan:

1. Select the plus icon + next to Plans in your navigation.
2. Follow the steps and add relevant details to complete your plan set up.

Merge multiple work items

Save time and reduce clutter by merging duplicate or redundant work items into a single, primary work item in Jira. This new bulk action is available for work items within Jira Software and Jira Business projects. To use this feature, you must have permission to edit work items, perform bulk actions, and archive work items.

To get started with this change:

1. Go to your Jira backlog or list view.
2. Select between 2 and 11 work items of the same type.
3. Select Merge from the bulk actions menu.
4. Choose the primary work item to merge the others into, select which work item’s description and fields you want to retain, and choose whether to consolidate linked work items, child work items, comments, and attachments from all selected work items.
5. Click Merge.

Bulk operations on timelines in business spaces

Timelines in business spaces now support bulk operations, allowing you to select multiple work items and apply actions to all selected work items at once. This update brings the familiar bulk actions experience from list and backlog views to business timelines, making it easier to manage work at scale.

To get started with this change:

1. Open the timeline view in your business space.
2. Select multiple work items using the checkboxes next to each item.
3. Use the toolbar that appears to apply bulk actions to your selected items.

Rovo Search in Jira for eligible users

Rovo Search is now enabled in Jira for customers with the appropriate Rovo entitlement. This update allows eligible Jira users to access Rovo Search features, improving search capabilities and productivity within the app.

1. Sign in to Jira with an account that has the Rovo entitlement.
2. Use the search bar to access Rovo Search features.

Import data into existing spaces with field mapping controls

You can now import data into an existing space using CSV. The field mapping screen only shows fields available in the selected space, and restricts the creation of new custom fields. Work items are appended to already existing work in your space.

To explore this change:

1. From the navigation bar, select Spaces > Create a new space.
2. From the sidebar, go to More > Import data.
3. Select CSV from the list of apps.
4. Upload the CSV file.
5. Select the existing space you want to import data into from the dropdown menu.
6. Map your fields using only the available fields in the selected space.
7. Review the summary of work items to be created or updated before confirming the import.

Updated audit log experience for Jira admins

Jira admins can now use an improved audit log to track and troubleshoot changes. This update provides a more consistent experience for managing important events, such as permission changes and configuration updates, helping you maintain better visibility and security.

1. In Jira, select Settings, then System.
2. From the sidebar, select Audit log.

Pause automation rules until a webhook is received

The Delay until component now supports a Webhook received event. This lets you pause an automation rule until a matching webhook call arrives, better coordinating work across third-party apps before the automation continues.

Discover more about using the Delay until automation component

To use this event in your automation rules:

1. Navigate to Automation in your Jira or Confluence space.
2. Create or edit an automation rule.
3. Add the new Webhook received event to the Delay until component.
4. Configure and save your automation rule.

Forge custom fields in the issue navigator

Forge custom fields now appear as first-class columns in the issue navigator in Jira Software. This allows you to search, sort, and export Forge custom fields just like native fields, making it easier to manage your work and migrate from server to cloud.

To get started with this change:

1. Go to your Space, then select the All work tab to open the issue navigator.
2. Select Columns to add your Forge custom fields to the view.
3. Search, sort, or export your work items using these fields as you would with any native field.

Keep track on your due and overdue work items in Slack

When you’re assigned a work item with a due date, you’ll receive daily notifications in Slack to help you manage and track your work.

You’ll get these notifications by default when digest notifications via email or the Jira web app are enabled for due and overdue work items in Jira, and You’re the assignee is turned on in the Jira app in Slack.

To stop receiving these notifications, select Turn off from the Jira app in Slack.

Introducing AI-generated summaries for Jira work items

Jira now offers an AI-generated summary card for work items. This feature helps users quickly understand complex work items by providing a concise overview - including information about its status, key contributors, and next steps - directly in the work item view.

1. Open any Jira work item.
2. Select the new Work Item Summary button at the top of the work item, next to Quick Add.
3. View your work item's AI-generated summary.

Find and join spaces faster

When you're invited to a space, you'll receive an in-app notification to help you get started faster.

To find the in-app notification, select Notification to find the invitation to join the space.

Activate apps faster from the template picker

App admins of Atlassian organizations that have only Jira apps can now activate Jira Service Management and Jira Product Discovery directly from the template picker. This simplifies the setup by combining app activation and project creation into a single step, helping you start using new features faster.

To view this change:

1. Open the Jira template picker.
2. Select a Jira Service Management or Jira Product Discovery template.
3. Review the template preview and app overview on the new setup page.
4. Select the checkbox to accept the product terms.
5. Select Try this template to activate the app and create your project.

Timeline: Save and share custom views

Plan work more effectively in Jira business projects by saving custom timeline views. Project admins can save timeline configurations at the project level so teams can quickly return to the same planning context, while individual users can still personalize their own view and reset back to the saved version when needed.

To get started with this change

1. Go to your business project and select Timeline from the project navigation.
2. Adjust the timeline to the planning context you need, such as applying filters, changing display options, or updating other supported timeline settings.
3. If you're a project admin, select + in the project navigation bar to create a new timeline view.
4. After configuring your timeline view settings, select the save icon and choose Save timeline to persist your changes, or Reset to last saved to return to the last saved configuration.
5. Use the view switcher to move between saved timeline views, or share the saved view link so teammates can open the same project-level timeline setup.
6. If you make personal changes, select the reset icon to return to the last admin-saved configuration.

Loom screenshots: Rich previews in Confluence and Jira

Loom screenshot links pasted into Confluence or Jira now render as rich Smart Link previews instead of plain text URLs. This improvement provides immediate visual context and brings screenshot links to parity with Loom video links.

1. Copy a link to a Loom screenshot.
2. Paste the link into a Confluence page or Jira work item.
3. Select the link to switch between Inline, Card, and Embed views.

A quicker way to unlink work items

You can now unlink work items directly from the work item view, without needing to select the work item relationship dropdown.

To unlink a work item from the work item view:

1. Select and open a work item in Jira that has linked work items.
2. Navigate to the Linked work section.
3. Hover over, or select, the row for the work item you want to unlink, and select the X (cross) icon.

Jira Plans - Improved onboarding for new users

We’ve made it easier for you to get started with Plans. As you onboard to Plans, you’ll now see an introductory video and clearer instructions, making it simple to set up and configure essential settings. These improvements help your team understand how to plan, track, and report on work across multiple spaces more effectively.

Whiteboards smart sections: update multiple Jira fields at once

Confluence whiteboards now let you update multiple Jira fields in a single smart section. This makes it easier to manage and organize Jira work items directly from your whiteboard, saving time and reducing manual effort.

To get started with this change:

1. Open a premium-enabled Confluence whiteboard.
2. Create a section on your whiteboard.
3. Select the section.
4. From the toolbar, choose Jira integrations, then select Create action (or click the Create action label).
5. In the side drawer, configure the smart section and select the Jira fields you want to update.
6. Save your changes.

The number of search results for projects, web pages and goals is now visible across Atlassian apps

When using the search feature in Atlassian apps, such as Jira and Confluence, you can now view the specific number of results for projects, goals, and web pages. This update brings consistency and clarity to your search experience, helping you to easily categorize your search results.

To get started:

1. Locate the search bar in Confluence, Jira, or any other Atlassian app that displays search results in the right panel.
2. Enter a question, name or keyword into the search bar.
3. View the right panel to see the number of search results for projects, goals, and web pages respectively.

Explore using Rovo Search in Atlassian apps

Bring work in faster when you create a new space

When you create a new space, the option to import data is more visible in the sidebar. This makes it easier for you to bring work from other tools right from the start.

All users can import data from other tools such as Monday, ClickUp, Jira (software space), and Jira (business space).

To import data during space creation:

1. Select Space, then Create space in the navigation.
2. Select Import data to see the expanded list of tools you can import your data from.

See work relevant to you in your weekly recap email

Your weekly recap email now displays more relevant recommendations and highlights, including mentions from work item descriptions. This helps you stay informed on important updates in your space.

Seamless Loom recording integration

This update introduces further integration between Jira and Loom. Users can now record using the Loom recorder right from their Jira work items, and Rovo will take care of updating the work item description based on the context shared in the video.

Incidents in Jira feature is leaving soon

We’re deprecating the Incidents in Jira feature (currently in early access), which will be removed on July 10, 2026. You can continue viewing and managing your incidents in Jira Service Management, as before.

Entity limits and reporting for admins

Jira Cloud now includes limits for field options, work item security levels, grants per permission, versions, workflows, statuses, components, and priorities. Admins can use new reporting and streamlining tools to monitor and optimize configuration, ensuring reliable app performance at scale.

To get started with this change:

1. Go to Work Items > System.
2. Select a configuration page, such as Custom fields , Work item types , or Permission schemes.
3. Review entity usage and follow prompts to optimize or clean up as needed.

Space Insights: Customizable dashboards

Visualize your team's progress more effectively with customizable dashboards in Jira. The Reports tab now defaults to Space Insights, an interactive dashboard where you can create and resize charts, lists, and activity streams scoped to your specific space. This change helps teams gain immediate insights into their work while keeping existing reports easily accessible.

To get started with this change:

1. Open any Jira Software or Jira Business space.
2. Select the Reports tab from the space navigation.
3. If you are a space admin, select Edit to add, remove, or resize widgets.
4. To find existing reports like burndown or velocity charts, select the more reports button at the top left of the view.

Bug tracking templates: Improved views and new project setup

Jira Cloud offers an improved bug tracking experience with updates to the company-managed project bug tracking template and a new team-managed project bug tracking template. These changes provide clearer, more useful default views, making it easier to set up and manage bug tracking projects.

To get started with this change:

1. Select Create project in Jira Cloud.
2. Choose the Software development category.
3. Find and select the Bug tracking template.
4. Select Use template to create your project.

Create a work item with a filter applied

When you create a work item in the List tab (previously List view or All work view), any filters you've applied in basic search will be automatically applied to the new work item. This means your created work item will stay visible in the list, making it easier to find and edit without adjusting your filters.

Discover more about the merge with List view and All work view.

To create a work item with a filter applied:

1. Go to the List tab in your space.
2. Select one or more filters in basic search and create a work item. The new work item will appeared in your list with the selected filter applied.

Security feature is moving to Development in Jira

The Security in Jira feature will now have a new home within Development in Jira.

Starting July 12, 2026, you’ll no longer have separate Security page in your software space in Jira, and Development will be the only place to access the security features. You can start using Development today, where all security features, including your existing security container connections and data, are already available. There you’ll also find data from other integrated apps, key metrics, work suggestions, and more.

Find out more about Development in Jira

1. Open your software space in Jira.
2. Locate the Development tab within the main navigation to access your deployments, security, code and repository information.

Native Teams support in Jira automation

Admins can now use Atlassian Teams natively within Jira automation rules. This update allows you to select teams directly in the Assign work item action and the User condition, removing the need for manual JSON workarounds or team ID lookups.

Jira automation actions

To get started with this change:

1. Open your Jira project and go to Automation.
2. Create a new rule or edit an existing one.
3. Add the Assign work item action or the User condition.
4. Use the native team picker to select the appropriate team.
5. Save and turn on your rule.

List view: Group work items by date

Organize your work more effectively in Jira by grouping work items by date and date-time fields in the list view. This update allows you to see your schedule at a glance and manage your team's priorities with better clarity by organizing work based on deadlines and timelines.

To get started with this change:

1. Open your project and select the List view.
2. Select the Group by menu from the toolbar.
3. Select a date field, such as Due date, from the list.

Streamline and manage custom fields options in your site

You can now scan for custom field options that aren't used in any work items or workflows by using tools that optimize your site. These tools let you bulk-disable them in one action, so you can keep each field under the 20,000 option limit. This ensures performance in your space stays predictable as your site grows.

Read more about optimizing and reducing unused field options

To streamline and manage custom fields in your site:

1. From the top navigation, go to Settings, then Work items.
2. Under Fields, select Fields to find the custom field you want to review.
3. Select Actions (...) next to the field name, then Optimize.

Streamline work item security levels in your site

To help you optimze your work item security levels, we've introduced tools that allow you to find and bulk-remove levels that aren't used in any work items. This ensures you stay within the limit of 50 levels per scheme and keeps your site fast and reliable.

Discover more about optimizing work item security levels in your space

To manage work item security levels in your site:

1. From the top navigation, go to Settings, then Work items.
2. Select Work item security schemes to open the scheme you want to manage.
3. Select Optimize to identify and removed unused security levels.

Full site scan for Jira and Confluence

Full site scan lets organization admins and Guard Detect scan all Jira and Confluence content to find sensitive data and export results for follow‑up. Full site scan is available to Guard Premium customers and can be launched from the Guard admin experience under the Content scan tab in the header.

When you start a content scan, you can select what you’d like to scan. Make sure you’ve set up any custom detections you wish to scan before you start a content scan.

1. In Guard Detect, select Content scan from the header.
2. Select Start new scan.
3. You’re presented with a dialog box, read the information, check the checkbox to confirm you’ve understood it, then select Next.
4. Select the option that suits your needs — either all Jira and Confluence apps, or your selection of specific workspace.
5. Select Start scan. A dialog box will confirm the scan has been created.
6. Select Close.

Your scan will be listed in the scan history.

Transcribe speech to text in Rovo Chat

Save time and capture every detail by using Rovo to transcribe speech to text in Atlassian apps. This feature allows you to quickly convert spoken words into written content, making it easier to interact with Rovo Chat and create content on the go.

To get started with this change:

1. Open an Atlassian app, such as Confluence or Jira.
2. Open Rovo Chat or select Create with Rovo where you would need to type a prompt.
3. Select Start dictation (the microphone icon).
4. Speak your prompt and select Finish dictation.
5. Select Submit to enter your prompt.

Retain unsaved description when pressing Escape

When editing a description, pressing the Escape key will now preserve your unsaved changes as a draft instead of discarding them. This update helps prevent accidental data loss and makes it easier to continue editing where you left off.

1. Open any work item in Jira Cloud and start editing the description field.
2. Type your changes, then press the Escape key.
3. Re-enter edit mode to see your unsaved changes retained as a draft.

Redesigned email notifications

Jira email notifications now feature a refreshed design with standardized components and styles and redesigned header and footer. This update improves the branding and consistency of the emails you receive from Jira, making it easier to stay across your team's work and identify important updates at a glance.

Preview work items with resizable panels

Jira is replacing the detail view in the List view and Global Search with a resizable preview panel. This change allows you to view and interact with work items in a side panel without losing your place in the list. You can also preview Confluence pages, projects, and goals without opening new browser tabs, helping you move quickly between work items and reduce tab overload.

To get started with this change:

1. Go to the All work tab or use Global Search in Jira.
2. Select a work item from the list to open it in the side panel.
3. Drag the edge of the panel to resize it, or select the option to open the work item in full-screen.

Deployments feature is moving to Development in Jira

he Deployments in Jira feature will now have a new home within Development in Jira.

Starting July 12, 2026, you’ll no longer have separate Deployments page in your software space in Jira, and Development will be the only place to access the deployment features. You can start using Development today, where all deployment features, including your existing app connections and data, are already available. There you’ll also find data from other integrated apps, key metrics, work suggestions, and more.

Find out more about Development in Jira

1. Open your software space in Jira.
2. Locate the Development tab within the main navigation to access your deployments, security, code and repository information.

Code feature is moving to Development in Jira

The Code in Jira feature will now have a new home within Development in Jira.

Starting July 12, 2026, you’ll no longer have separate Code page in your software space in Jira, and Development will be the only place to access the code features. You can start using Development today, where all code features, including your existing app connections and data, are already available. There you’ll also find data from other integrated apps, key metrics, work suggestions, and more.

Find out more about Development in Jira

1. Open your software space in Jira.
2. Locate the Development tab within the main navigation to access your deployments, security, code and repository information.

New Jira beta features page

Jira admins can now manage experimental features from a new Jira Beta Features page in Jira Admin Settings. This update centralizes feature management by moving control from individual user settings to a dedicated admin interface in Jira Cloud, ensuring consistent experiences across your site.

To get started with this change:

1. Go to Settings.
2. Select System.
3. Select Beta Features to view and manage available beta features.

Create work items faster with a modernized experience

We’re updating the way you create work in Jira to make it faster and simpler. When you select the Create button, you’ll see a compact create window with essential fields so you can capture ideas quickly and stay in your flow. We're introducing this experience gradually, so it may not be available in your site right away. As we learn from feedback and usage, we may continue to refine the experience.

To get started with this change:

To create a work item with the modernized experience:

1. Select the Create button from any screen in Jira.
2. Enter the key details for your work item in the compact create window. The compact create window shows the summary, description, any required fields, and up to three optional fields from your existing configuration. For team-managed projects, these are the highest-ranked optional fields. For company-managed projects, they’re the first optional fields shown on the create screen.
3. Select Create to finish, or select the expand icon if you need to add more details in the full layout.

For projects with more complex needs, like extra required fields, tabs, or customized screens, you'll automatically see the full-form layout.

Connected apps: End-of-support warnings for Connect apps

Admins and users will now see in-product warnings for apps built on the Connect framework to prepare for its upcoming end-of-support. These notifications in Jira, Confluence, and Atlassian Administration help you identify affected apps and plan your migration to Forge.

1. Go to Atlassian Administration, then select your organization.
2. Select Apps, then Connected apps.
3. Look for warning banners at the top of the page or within specific app details to identify apps requiring action.
4. For end users, look for dismissible banners within app iframes on Jira issues or Confluence pages.

Web links: AI-powered Atlassian and third-party content suggestions

Gather context in Jira with AI-powered content suggestions from across your connected apps. When you add a web link to a work item, Jira now suggests relevant Confluence pages, whiteboards, and Loom videos, alongside files from third-party apps like Google Drive, Microsoft OneDrive, and Figma.

To get started with this change:

1. Open a work item in Jira.
2. Select the plus icon (+), then select Add web link.
3. In the Web links section, select View suggestions.
4. To add a suggested link to your work item, select the checkmark icon.

Create Jira Spaces with Rovo

Save time and reduce setup effort by using Rovo to configure your new Jira spaces. By providing a simple prompt, Rovo suggests the best space name, key, work types, and statuses based on your team's specific needs and existing context.

We're currently experimenting with this feature, so it may not be available to everyone yet.

1. Hover over Spaces in the side navigation, then select Create space
2. Under space templates, select Create with Rovo > Get started with a prompt.
3. Enter a prompt describing your team's work, and optionally include links to Confluence pages, Loom videos, or third-party apps for more context.
4. Review the suggested space configuration, including the space name, key, and workflow.
5. Select Create space to finish the setup.

Space invites for linked teams

In Jira, you can automatically send space invites to team members when their team is linked to a Jira space. New team members also receive invitations to any linked projects. This ensures everyone has the access they need to collaborate effectively from day one

To get started with this change:

1. Navigate to your Jira space.
2. From the top navigation, select Link contributing teams.
3. Once the team is linked, project invites will be sent to all team members to grant them access.
4. Alternatively, go to the Teams page in Atlassian Home to invite new users or add spaces to existing teams.

Formula fields: Enabled on company-managed spaces and text, date, and duration supported as output types

Jira formula fields are now available in company-managed spaces.

Jira formula fields support text, date, and duration outputs, enabling complex calculations across your work. You can search and sort by formula field values using Jira Query Language (JQL) to organize and prioritize your work items. These features are available in both company-managed and team-managed spaces.

Create a formula field

In a company-managed space, create a formula field via your admin settings:

1. Start in your Jira company-managed space.
2. Select Settings from the global navigation, then select Work items.
3. Select Fields from the side navigation.
4. Select Create new field.
5. In the Field type dropdown, select Formula.
6. Enter a field name and description.
7. In the Spaces dropdown, select All spaces to make the field available everywhere, or select a single space to restrict it. You can’t select more than one individual space.
8. Select a Formula output: either number, text, date, duration, currency, or percentage.
9. Enter a formula. If Rovo is enabled, you can select Generate formula to create a formula using natural language. View the list of supported fields and functions for formulas
10. Select Format to choose how to display the formula’s output (for example, you could show a duration as days or hours, or a number as a currency with decimals).
11. Select Create to finish.

In a team-managed space, create a formula field via your space settings:

1. Next to your space’s name in the sidebar, select More actions (•••), then Space settings.
2. Select Fields in the sidebar.
3. Select Add field, then select Create new field.
4. In the Field type dropdown, select Formula.
5. Enter a field name and description.
6. Select a Formula output: either number, text, date, duration, currency, or percentage.
7. Enter a formula. If Rovo is enabled, you can select Generate formula to create a formula using natural language. View the list of supported fields and functions for formulas
8. Select Format to choose how to display the formula’s output (for example, you could show a duration as days or hours, or a number as a currency with decimals).
9. Select Create to finish.

Guest role available for Jira

Collaborate with external partners and contractors by inviting them to Jira as guests. The guest role lets you provide restricted access to specific spaces in Jira without consuming a paid seat, helping your team work with external contributors while you maintain security and control.

How to invite guests to Jira

Plans: Connect and view Atlas projects

You can now view Atlas projects associated with work items directly within your plans in Jira. This integration allows you to see which Atlas projects are linked to your work items, helping you align your team's work with broader strategic initiatives without leaving your plan.

To get started with this change:

1. Open a plan in Jira.
2. Select Fields, then Add a field.
3. Search for and select Project to add it to your plan.
4. Select an Atlas project lozenge in the field to open the project details in a new tab.

Field optimization tools for field schemes

Jira Cloud admins can now access streamlining tools from the field schemes experience in Jira admin settings. These tools optimize field schemes by removing unused fields, creating project-specific schemes, splitting schemes, and provide functionality to download optimization details.

To get started with this change:

1. From the top navigation, go to Settings, then Work items.
2. Select Field schemes.
3. Select the field scheme you want to manage.
4. Under Actions, select Optimize to use the streamlining tools.

Group work items in the timeline view

Organize work more effectively by grouping work items on your timeline. You can now group your work by fields like assignee, status, or labels to see who’s working on what and better manage your team’s capacity. This helps you visualize workload at a glance and ensures work is distributed fairly across the team.

To group work items:

1. Go to your Jira space and select Timeline from the navigation.
2. Select the Group by menu at the top of the timeline.
3. Choose the field you want to reorganize your work items by.

Turn tables and lists into charts and diagrams with Remix

Understand complex information faster by transforming text, tables, and lists in Jira work item descriptions into instant charts and diagrams. Remix is an AI-powered feature that lets you generate personal visualizations without changing the original content — so you can explore data your way.

1. Open a Jira work item and select the description to enter edit mode.
2. Hover over a table, list, or text block to reveal the element toolbar.
3. Select Remix from the element toolbar or the Rovo menu.
4. Choose a visualization type, such as a chart or diagram, to generate a preview.
5. Select Insert to add the visualization to the description, or Copy to clipboard to use it elsewhere.

Start and complete sprints automatically in Jira

Save time and keep your team on track by scheduling sprints to start and complete automatically in Jira.

To get started with this change:

1. Go to your scrum board and select the Backlog.
2. Find the sprint you want to automate and select More actions (...), then select Edit sprint.
3. Select Automatically start and complete sprint.
4. Set your preferred Start date and End date.
5. Choose whether open work items should move to the backlog, a new sprint, or to an existing sprint on completion.
6. Select Save.

Draft release notes with Rovo

Save time by using Rovo to draft release notes in Jira. Summarize key changes in your release with AI and communicate value to your customers and stakeholders more efficiently.

To get started with this change:

1. Go to your software space and select the Releases tab in the navigation.
2. Select the version you want to generate release notes for.
3. Select Release notes.
4. Select the toggle next to Create with Rovo.
5. Select Create with Rovo to open Rovo Chat and review your draft.

Summary view: Recommended automations

Jira users can now discover and set up automations more easily with a new gadget in the Summary view. This feature recommends three automations tailored to your project, helping you save time and explore how Atlassian Rovo and agents can streamline your team's work.

To get started with this change

1. Go to the Summary view of any Jira or Jira Business project.
2. Locate the new automations gadget.
3. Select Try to open Rovo Chat with a pre-filled prompt for that specific automation.
4. Select Set up to open a wizard that guides you through the configuration steps.

Jira: Use your current view as context for Rovo Chat

Save time and get more relevant answers by using your current Jira view or selected work items as context for Rovo Chat. Instead of manually copying work item keys, Jira now automatically passes your active view, filter, or selected work items into Rovo Chat to help you summarize work, create insights, or take actions tailored to your current workflow.

1. Open a supported Jira view, such as your All work, Backlog, or List view.
2. Select one or more work items to make them the active context for Rovo Chat.
3. If no items are selected, Rovo Chat will automatically use your current view or filter as context.
4. Open Rovo Chat to see the context indicator and enter your prompt.
5. To remove the context, select the X on the context indicator in the chat interface.

Forge UI modifications: support for work item modal views

Forge apps that use UI modifications now work consistently when you open a work item (referred to as an issue in the API) in a modal through Forge apps in Jira Cloud and Jira Service Management (agent view). Previously, these modifications were not applied to modals triggered by apps. This change ensures that your UI modifications — such as hiding fields, setting values, or making fields read-only — apply correctly regardless of how you open the work item.

To get started with this change:

1. Navigate to your Forge app's global page in Jira.
2. Select a work item to open it in a modal view.
3. Observe that your Forge app's UI modifications now apply to the work item modal.

Forge custom fields of Object type now supported in bulk edit

This update enhances the Jira Issue bulk-edit experience for Object type Forge Custom Fields. it replaces the existing TextField input field with a forge-app-defined custom edit experience for Object Forge Custom Field. Note: The Forge app developer has to enable the custom edit experience for bulk edit by adding "issue-bulk-edit" in the manifest. We will fallback to default TextField experience if the Forge app developer doesn’t enable it.

1. Select the work items you want to update from the List view, Backlog or Global Issue Navigator
2. A bulk action toolbar opens once you have selected the issues. Select "Edit Fields" to open the "Bulk Edit" side panel
3. Follow the prompts to select the Object type Forge custom fields you want to edit and enter the new values.
4. Review and confirm your changes to complete the bulk operation.

View work items with parent work items from other spaces in the List view hierarchy

This update restores the ability to view work items with parent work items from other spaces when Show hierarchy is enabled in the List view in Jira.

1. Open the List view in any Jira space.
2. Select More actions (···) and toggle on Show hierarchy.

Work items having parent work items in another spaces should now be visible in the List view.

Code blocks: Enhanced formatting and language detection

Code blocks in Jira and Confluence now include several improvements that make technical content easier to write, format, and read. New code blocks can detect supported languages automatically, the language picker now surfaces recently used languages, the floating toolbar includes controls for formatting code and line numbers, wrap setting is now persistent and clicking the code block border selects the whole block for easier editing.

Use these improvements while editing code blocks in Jira or Confluence:

Detect a language automatically

1. Insert a new code block with no selected language.
2. Type or paste enough code for the editor to detect the language.

Use recently selected languages

1. Open the language picker in a code block.
2. Select a language manually.
3. Your recent selections appear in the Recently used section the next time you open the language picker.

Format code

1. Select a JSON, JavaScript, JSX, or SQL code block that has content.
2. Select Format code from the floating toolbar.

Wrap lines

1. Select a code block.
2. Select the Wrap lines button to wrap or unwrap lines. Changes made while editing are saved with the page.

Show or hide line numbers

1. Select a code block.
2. Select the Line numbers button to show or hide line numbers. Changes made while editing are saved with the page.

Select the whole code block

1. Click the code block border to select the whole block.

Create agents directly from Jira work items

You can now create and configure agents without leaving your current work item. Select Create an agent from the Assignee or Agents field, and an agent plan will be drafted based on the work item context — ready for you to review, refine, and activate in seconds.

1. Open a work item in Jira.
2. In the Assignee or Agents field, select Create an agent.
3. An agent plan is drafted based on the work item context.
4. Review the suggested name and instructions, then edit if needed.
5. Select Create to activate the agent on your work item.

CSV import: Map statuses and import into existing spaces

Save time when moving data into Jira Cloud by importing CSV files directly into your existing spaces. This update to the CSV importer allows you to add new work items to a space and map status values from your file to existing Jira statuses, ensuring your data aligns with your current workflows.

You need to be a system or organization admin to do this.

1. In Jira, go to Settings, then System.
2. Select External system import, then CSV.
3. Select an existing space from the dropdown menu as your import destination.
4. Follow the prompts to map your CSV fields and work types and status values to the existing space configuration.

Contextual suggestions for Atlassian apps and operations

Jira now features a redesigned experience for cross-app recommendations and operations. Instead of large banners, you'll see subtle, contextual suggestions within relevant parts of your page to help you discover other Atlassian apps and helpful widgets without interrupting your work.

1. Navigate to any relevant page in Jira where you typically manage work or view project details.
2. Look for contextual suggestions or small widgets that appear near related content.
3. Select a suggestion to explore how other Atlassian apps or operations can support your current task.

Triage work items with the Jira Triage Agent

Save time and reduce manual effort by using the Jira Triage Agent to automatically review and route incoming work. The Jira Triage Agent uses AI and your Teamwork Graph to analyze the context of new work items and suggest updates for fields like priority, labels, and assignee. It also identifies duplicate or similar work items within your space, helping your team stay organized and focused on the right tasks.

1. Go to your Jira board and select the agent picker from the status column header.
2. Select the Jira Triage Agent to attach it to the workflow status.
3. Alternatively, open any work item and select Assign agent from the Agents section to run the Triage Agent on that specific work item.
4. Review the suggested updates and relationships directly on the work item.

Company-managed spaces: Create spaces with a one-step wizard

Admins can now create company-managed spaces in Jira using a simplified one-step wizard. This update streamlines the space creation process, allowing you to set up and configure your spaces more efficiently.

1. In Jira, go to Spaces, then select Create space.
2. Choose a space template and select Use template.
3. Select Company-managed as the space type.
4. Enter your space details in the one-step wizard and select Create space.

Mobile app policy: Restrict notifications

Organization admins can now control how push notifications appear in Atlassian mobile apps to help prevent data leaks. This new restriction in the mobile app policy allows admins to either hide sensitive notification content or block push notifications entirely for Jira, Confluence, and Rovo mobile apps.

1. Go to admin.atlassian.com.
2. Select your organization, then go to Security and Mobile app policy.
3. Create a new policy or select an existing one.
4. Select Restrict notifications and choose your preferred setting.

Assign multiple agents to workflow transitions

Manage your workflow automation directly from your board by assigning multiple agents to specific column transitions. You can customize each agent’s behavior with optional prompts without ever opening the workflow editor. This gives you more granular control over how work moves through your board, saving you time and increasing your team's automation flexibility.

To get started with this change:

1. Go to your board and select the Add agent icon in the column header.
2. In the Add agent modal, select an agent from the dropdown and choose one or more transitions to assign them to. To update an existing configuration, select an agent avatar or an agent from the overflow list in the column header.
3. Enter an optional custom prompt to configure the agent's behavior for those transitions.

Ability to add agent to workflow transition on Company-managed boards

Save time and streamline your processes by adding agents directly to your workflow from your board in Jira. This update allows you to integrate automation and AI capabilities into your team's work without leaving your current view, making it easier to manage how work moves from start to finish.

To get started with this change

1. Navigate to your board in Jira.
2. Hover the board column and see Add agent icon button, provided if the user has the required permission.
3. Click on the button and wait for the modal to appear.
4. Select the agent and provide the prompt value.

Site Optimizer: Support for new field schemes

Jira Cloud admins can now use Site Optimizer to analyze the new field scheme model. This update allows you to identify and manage both legacy field configurations and the new field schemes within your site, helping you streamline your site configuration and prepare for future migrations.

1. Go to Settings in Jira and select System.
2. Go to Site Optimizer → All reports.
3. Select Custom fields and goto Review and optimize to view the analysis of your site schemes.
4. Review the list of schemes, which now includes both legacy field configurations and the new field schemes.
5. Select the Optimize button next to a scheme to view detailed analysis and recommended actions.

Jira recommend agents empty state

Save time by discovering and assigning Rovo agents to your work items more easily. Jira now displays an empty state in the agent section when no agents are assigned, making it clear that you can use agents to help progress your work.

To get started with this change

1. Open a work item in Jira.
2. Locate the Agents section in the work item details.
3. If no agents are assigned, you'll see the new empty state.
4. Select the agent picker to browse and assign a Rovo agent to your work item.

Find the right agent for your work with agent recommendations

Save time and reduce guesswork with agent recommendations in Jira. We’ve updated the agent picker and browse experience to surface the most relevant agents based on your current task, workflow, and recent activity. These improvements, powered by a new recommendation API, help you quickly identify which agents can best assist with your work items.

To find and use the recommended agent:

1. Open a work item in Jira.
2. Select Agents at the top of your work item.
3. Review the Recommended agent at the top of the list.
4. Select an agent from the Favorites, Coding agents, or Company verified categories to assign them to your task.

Transition improvements in workflow editor

Manage your workflows more efficiently with new transition options and a clearer layout in the workflow editor. These updates help Jira admins save time when creating statuses and provide better visibility into how work moves through a project.

To get started with this change:

1. Go to Space settings, then Workflows.
2. Select Edit on the workflow you want to update.
3. Select Add status to see the new Allow transitions from any status checkbox.
4. Select any status on the diagram to view the separated Incoming and Outgoing sections in the status panel.

Work with agents from your Jira For you page

Save time and streamline your workflow by delegating tasks to agents directly from the For you page in Jira. You can now invoke agents on work items in your Recommended and Assigned to me tabs without leaving your current view. Additionally, a new Agents need your input section surfaces sessions that require your input or are ready for review, helping you stay on top of delegated work.

1. Go to the For you page in Jira.
2. Hover over a work item in the Recommended or Assigned to me tab.
3. Select Work with agent to open the agent picker and choose an agent to start a session.
4. Check the Agents need your input section in the Recommended tab to review sessions that are paused, waiting for input, or finished.

Boards: Assign agents to columns

Save time by assigning agents to workflow columns directly from your board in Jira. This update allows you to manage agent assignments more quickly in team-managed spaces without leaving your current view. You can also hover over an agent’s avatar to see their details at a glance.

• Go to your board in a team-managed board in Jira.
• Hover over a column header to reveal the Add agent icon.
• Select the Add agent icon to open the agent picker.
• Select an agent to assign them to all transitions in that column, or remove an existing agent.
• Hover over any assigned agent's avatar to view their profile details.

Configure your filter panel with more fields and saved filters

You can now customize your filter panel in Jira to better suit your team's workflow. We’ve added support for more fields in basic mode, including date, select, and people fields. We've integrated your saved filters directly into the filter panel. These changes help you find the work you need faster by keeping your most important filters organized and accessible.

To get started with this change

1. Go to your Board or Backlog (software team-managed projects only), or the List view.
2. Select Filter to open the filter panel.
3. Select + Add field to add new fields or use the drag handle to reorder them.
4. Select the Saved filters dropdown within the panel to save your selections or switch between your saved filters.

Automation: Use partner coding agent action

Save time and streamline your development workflow by using Jira automation to trigger actions in third-party coding agents. You can now use the partner coding agent action to automate code reviews, documentation updates, or work item analysis directly from Jira.

1. Go to your Jira space and select Space settings, then Automation.
2. Select Create flow and choose a trigger for your automation.
3. Select New action, then search for and select partner coding agent-*
4. Configure the action by providing additional instructions through a custom prompt or, change the connection user who will be used for invoking the coding agent.
5. Select Save, set the flow name and activate your flow.

*-Support for Github Copilot agent is in Open Beta

Board experience: Harmonized view for team-managed projects

Jira now provides a more consistent board experience for team-managed projects. This update aligns the visual layout and functionality of boards in team-managed projects with those in company-managed projects, making it easier for teams to switch between different project types without losing familiarity. This change helps your team stay focused on work by providing a unified way to track and manage work items across Jira.

To get started with this change

1. Open your team-managed project in Jira.
2. Select Board from the project sidebar.
3. Interact with your work items using the updated board layout and navigation.

Link existing statuses to team-managed spaces board view

Jira admins and project admins can now link existing workflow statuses to team-managed spaces from within the board view. This change helps organizations standardize workflows and improve reporting across Jira by reusing established statuses instead of creating new ones.

To get started with this change

1. Go to your team-managed space board.
2. Either create a new column from the board, or from the “Configure Columns” option in the board “More actions” menu.
3. Type the name of an existing status to search for and select an existing status.
4. Click “Create” or “Proceed”.
5. New statuses can still be created by entering a unique status name and choosing “Create Status”.

Work item view: Add existing statuses in team-managed spaces

In Jira team-managed spaces, you can now search for and select an existing status when adding a status from the Status field in the work item. If the status you need does not exist, you can create a new one.

1. Open a work item in a team-managed Jira space.
2. In the Status field, select Add status.
3. Search for and select an existing status.
4. If you need a new status, enter its name and select Create status.

Access management: New global page

Jira admins can now manage user access and roles more efficiently with a new global access management page. This update provides a central location to view and control how users join and interact with Jira, helping you maintain security and streamline onboarding.

1. Go to Jira settings, then System.
2. Select Access management from the sidebar.
3. Review and update your global access settings as needed

Timeline: Sort work items by assignee, status, and dates

Organize your project timeline in Jira by sorting work items based on the assignee, status, or key dates. This update helps you quickly find specific work and better understand your team's schedule and progress.

To get started with this change

1. Open your project in Jira and select Timeline from the left navigation.
2. Select the Sort menu at the top of the timeline.
3. Choose to sort your work items by Assignee, Status, Start date, or Due date.

Plans: Focus Area hierarchy in timeline swimlanes

When you group your timeline by Focus Area in Jira, swimlanes now display your Focus Area hierarchy. This update allows you to see the highest-level Focus Area by default and expand it to drill down into work connected to child Focus Areas, matching how they are structured in Focus. This change helps you better visualize and manage work across different levels of your organization within the Jira app.

To get started with this change

1. Open your plan in Jira and go to the Timeline view.
2. Select the Group by menu and choose Focus Area.
3. Locate the Focus Area swimlanes to see the highest-level Focus Area.
4. Select the arrow next to a Focus Area to expand and view its child Focus Areas and connected work.

Individual capacity planning: Plan work for your team

Plan work more effectively by managing the capacity of individual team members in Jira. This new experience allows you to see each person's availability and workload in one place, helping you balance tasks and prevent burnout across your team.

1. Go to your space in Jira.
2. Select the Add tab icon (+) in the horizontal navigation.
3. Select the Capacity tab to add it to your navigation.
4. Select Capacity to interact with the capacity planner.

Fix failed builds from the development panel

Software projects in Jira now include a button in the development panel that allows you to fix failed builds using agents. This update helps you quickly address build issues directly from the work item, saving time and streamlining your development workflow.

1. Open a Jira work item that has a failed build associated with it.
2. Locate the development panel in the work item.
3. Select the button to fix the build using an agent.

Emoji picker: Refreshed UI and new Atlassian emojis

We've updated the emoji picker across Atlassian apps, including Jira, Confluence, and Jira Service Management, to provide a more modern experience. This refresh includes a new set of Atlassian emojis, making it easier for you to express yourself and collaborate with your team.

1. Open any content where you can use emojis, such as a Jira work item or Confluence page.
2. Select the emoji icon in the editor toolbar or type a colon (:) to open the emoji picker.
3. Explore the refreshed interface and select from the new set of Atlassian emojis.

View work item hierarchy in the timeline

Jira users can now view and navigate work item hierarchy directly from the timeline when filters are applied. This change introduces a hierarchy flyout that helps you understand the relationship between parent and child work items without losing your place in the timeline.

To view the work item hierarchy:

1. Go to the Timeline view in your Jira space.
2. Apply a filter to your work items.
3. Select Show hierarchy on an work item row.

Workflow rules: View all rules in a single dialog

Jira Cloud admins can now view and manage all workflow rules for a transition in a single, tabbed dialog. This update provides a larger surface to inspect rule categories while maintaining the context of your workflow diagram.

To get started with this change

1. Open the workflow editor for your project.
2. Select a transition in the workflow diagram to open the transition details side panel.
3. Select View all in the rules section of the side panel.
4. Use the tabs in the dialog to switch between different rule categories.

Filter by agent and agent state using the refined filter panel

Jira users can now filter work based on assigned agents and their current states. This update to the filter panel helps you manage work items more effectively as you incorporate agentic workflows into your experience.

To get started with this change:

1. Open a Board or List view in your space.
2. Select Filter.
3. Create a new filter using the fields Agent or Agent state.
4. Choose the agent or agent state you want to filter by.
5. Select Apply.

Automation: Integrate with Cursor

Save time and streamline your development workflows by integrating Cursor with automation in Jira. This new action allows you to trigger Cursor tasks directly from your automation rules, helping your team stay focused and productive.

To get started with this change

1. Go to your Jira space and select Space settings, then Automation.
2. Select Create flow and select a trigger for your automation.
3. Select New action, then search for and select Use Cursor in Coding agents action from the list of available actions.
4. Configure the action by providing additional instructions through a custom prompt or change the connection user (who will be used for invoking the coding agent).
5. Select Save, set the flow name, and activate your flow.

List: Expand and collapse all work items

Save time in Jira by expanding or collapsing all top level work items in the list view with a single click. This update allows you to quickly view or hide child work items across your entire list. Furthermore, when grouping is applied, this feature allows you to quickly expand or collapse all groups.

To expand work items in list view:

1. Go to your Space, then select the List/All work tab.
2. Select the Expand parent work items toggle to expand all root-level work items.
3. Select the toggle again to collapse the hierarchy and return to a high-level view.

View and manage all your agent work in one place

Save time and stay organized with My agent sessions, a new view on the For you page in Jira that lets you monitor and manage all your agent work from a single place. See which sessions need your input and take action immediately without having to search through individual work items.

To get started with this change:

1. Open Jira.
2. Select For you from the navigation menu.
3. From the My agent sessions view, select any session to take action.

Autocomplete for teams in JQL

Find and select Atlassian teams more easily when using the membersOf() function in Jira Query Language (JQL). An autocomplete dropdown now lists your site's teams as you type, so you no longer need to manually find and enter team IDs. Filter work items by team name to ensure your boards and reports stay accurate.

To get started with this change:

1. Open your Jira app and go to your space.

2. Select the List tab, then select Filter.

3. Select the JQL tab to start writing your query.

4. Type the membersOf() function and start typing a team name inside the parentheses.

5. Select your team from the autocomplete list that appears.

Smart field suggestions now available in the new Jira issue creation experience

Speed up your workflow and reduce manual data entry with intelligent field suggestions in Jira's modernized work item creation dialog. By analyzing your project's historical patterns and similar issues, Jira now surfaces the most relevant values for both standard and custom fields, helping you capture work faster and with greater accuracy.

To get started with this change

Smart field suggestions are available for Jira Cloud Standard and Premium plans.

1. To see these suggestions in the new issue creation experience, ensure that Atlassian Intelligence is enabled for your organization.
2. Admins can manage this setting by navigating to Organization settings > Atlassian Intelligence.
3. Once enabled, suggestions will appear automatically as you create issues in projects with sufficient historical data.

Blocks: Transform, sync, and save content across apps

Blocks bring faster editing, reusable patterns, and always-in-sync content across apps. This new feature set allows you to create content once and reuse it across Jira and Confluence with live-syncing, ensuring your information is always up to date. You can also quickly transform content types using the new block menu and save polished sections as templates for future use.

1. Open any editor and select the drag handle (⋮⋮) to access new block-level options.
2. Select Change format to convert a block into a different type, such as a paragraph into a panel.
3. Select Create sync block from the menu to turn content into a synced block, then insert it elsewhere using the /sync block command.
4. Select one or more blocks and select Save block template to create a reusable template you can insert via the slash command or insert menu.

Customize your epic work type during project creation

You can now rename and customize the icon for the epic work type directly within the project creation wizard in Jira. This update allows you to align your project structure with your team's specific terminology and mental models from the very beginning, ensuring a more intuitive setup experience.

To get started with this change

1. Select Create project in Jira.
2. Choose a template, such as Kanban or Scrum.
3. In the project creation wizard, locate the Work types section.
4. Select the Epic work type to rename it or choose a new icon.
5. Complete the project creation process to see your customized work type in your new project.

Hand off work items to AI coding agents from Jira

Hand off any work item to Cursor, Claude Code, GitHub Copilot, or other agentic tools, with full context, in one click.

You can now launch your preferred AI coding agent directly from a Jira work item. Jira automatically assembles the relevant context, including the summary and description, into a ready-to-go prompt, so your agent can start working immediately without manual copy-paste.

Supported tools: Desktop apps: Cursor, GitHub Copilot, OpenAI Codex, VS Code. Terminal and CLI tools: Claude Code, Rovo Dev CLI.

1. Open any work item in Jira and find the code icon in the work item header.
2. Select your coding agent from the dropdown.
3. For desktop apps, the tool opens with a pre-filled prompt containing your work item context. For terminal-based agents, copy the ready-made command in one click and paste it into your terminal.

Plans: Formula fields now recalculate in scenarios

Formula fields in Jira Plans now recalculate based on scenario values, allowing you to see up-to-date derived values while exploring changes in your timeline. Previously, formula fields only reflected data from the committed Jira issue, which could lead to inconsistent information when testing "what if" scenarios. This update ensures that when you modify a referenced field in a scenario, the dependent formula field updates immediately to help you make more accurate planning decisions.

To get started with this change

1. Open a plan in Jira and ensure you have both a formula field and its referenced fields added as columns in the timeline or backlog view.
2. Select a scenario to begin testing changes.
3. Modify the value of a field that your formula depends on, such as a date or number field.
4. Observe the formula field column to see the value recalculate based on your scenario-only change.

Workflow editor: Replace statuses

Save time when editing your workflows in Jira by replacing an existing status with another one in a single action. This update allows you to swap statuses without manually editing transitions, helping you maintain your workflow structure while making necessary adjustments.

1. Edit a Jira workflow.
2. Select the status you want to replace.
3. Select the replace option in the status details panel.
4. Select an existing status or create a new one to take its place.
5. Update your workflow and select which status work items in the removed status should be moved to (this will default to the replacement status).

Workflow editor: Old version removal

We’ve removed access to the old workflow editor in Jira. This change ensures all users have a consistent experience using the updated workflow editor to manage how work moves through its lifecycle.

1. Go to Jira settings, then Work items.
2. Select Workflows.
3. Select More actions (•••), then Edit on any workflow to open the current workflow editor.

Improved onboarding for new Jira users

New users joining Jira will now land directly on the For you page instead of landing on an empty page or a generic directory. This change helps new team members quickly find relevant work and get started with their tasks in Jira without needing to navigate through multiple menus.

To view this change:

1. Log in to Jira as a new user.
2. View your personalized For you page.
3. Select a task or project from the page to begin working.

Manage delivery risks with Jira Delivery Agent

Jira now includes the Jira Delivery Agent, a Rovo Agent designed to help you manage your work more effectively. This agent reads Jira work, identifies delivery risks early, and turns issue activity into clear, actionable updates. By using the Jira Delivery Agent, you can make more informed decisions and keep your team on track.

To use the Jira Delivery Agent:

1. Open Rovo Chat in your Jira space.
2. Select the Rovo dropdown menu.
3. Search and select the Jira Delivery Agent to begin the analysis of your work.

Plans: Additional custom fields on the timeline

Save time and improve visibility by adding more fields to your timeline in Jira. You can now include Updated, Created, Read-only text and Paragraph fields directly on the Plan to keep your team informed without switching views.

To get started with this change

1. Open a plan in Jira.
2. Go to Plan settings, then Timeline.
3. Select Add field.
4. Choose the read-only text or paragraph field you want to add.
5. Select Add to see the field on your plan.
6. Go to the Timeline and select Add Fields to show Read-only text, Updated and Created fields.
7. Paragraph fields are visible from the Work Item Description modal accessed by clicking on the Work Item summary.

View and manage Studio flows in Product Automation

Manage your automation flows more effectively with the new ability to view Studio flows directly within Product Automation. This update provides a centralized view of your flows, making it easier to track and organize automated processes across your Atlassian apps.

1. Open your Atlassian app and navigate to Product Automation.
2. Select the Studio flows tab from the automation list.
3. Review the list of available flows..

Break down work items with Rovo in list view

Save time by using Rovo to break down parent work items into smaller tasks directly from the list view in Jira. This new feature in Jira and Jira business projects allows you to quickly generate child issues using AI-powered suggestions, helping your team stay organized and move faster.

To get started with this change

1. Open a Jira or Jira business project and select the List view.
2. Select the + icon or the inline child creation area under a parent work item.
3. Select the Break down with Rovo call-to-action.
4. Review the suggested tasks in the Rovo chat sidebar and select Create work items to add them to your project.

Duplicate work is detected while creating new work items in the global navigation

Jira Cloud now helps you avoid creating duplicate work items by flagging potential duplicates during the creation process. When you create new work items using the global navigation, Jira identifies similar work and alerts you, saving time and keeping your spaces organized.

1. Select Create from the top navigation bar in Jira.
2. Start entering details for your new work item.
3. Look for a list of potential duplicates that appears as you type.
4. Review the suggested work items to see if the work already exists before completing your new work item.

Switch to a work item dialog from the preview panel

Get a larger view of your work items without leaving your list. You can now open a work item in a dialog directly from the preview panel in List view and global search. From this dialog, you can navigate between work items using arrow buttons or keyboard shortcuts.

1. Open a list view or perform a global search in Jira.
2. Select a work item to open it in the preview panel.
3. Select the expand button in the preview panel to open the work item in a modal.
4. Use the navigation arrows within the dialog or keyboard shortcuts to move to the next or previous work item in your list.

Faster work item execution with agent readiness

We’re testing a smarter way to get AI agents working for you even faster.

Some people in your organization may be part of an Agent Readiness experiment. This new check reviews your Jira work items to see if they have enough information for your agent to start immediately – skipping the planning phase so you get your results sooner.

Assign a work item to an agent as you normally would. If the experiment is active, you’ll see a message: “Rovo is reviewing the work item.”

Rovo checks if there’s enough context for the agent to start right away. If there is, the agent bypasses the planning phase and gets straight to work.

Select your space when creating work items in chat

Stay in your flow and capture work the moment it comes up. The /create-work-items skill in Jira now lets you view and select your space directly in chat so the right work lands in the right place, without switching apps.

1. Open your chat app where Jira is integrated.
2. Use the /create-work-items skill in your conversation.
3. Select the space where you want to create the task using the new space selector.
4. Review the work items generated and select Create.

Automation: Claude agent action

Save time and streamline your development workflow by using the Claude agent action in Jira Cloud automation. This new action allows you to integrate Claude, a third-party AI agent, directly into your automation rules to perform complex tasks and process information within Jira Cloud.

1. Go to your Jira space and select Space settings, then Automation.
2. Select Create flow and select a trigger for your automation.
3. Select New action, then search for and select Claude agent action from the list of available actions.
4. Configure the action by providing additional instructions through a custom prompt or change the connection user (who will be used for invoking the coding agent).
5. Select Save, set the flow name, and activate your flow.

Preview panel: Increased maximum width

We've increased the maximum width of the preview panel for Jira’s list to help you view more fields and content without having to open the work item in a modal or new tab. This change allows for faster triage and editing while maintaining the context of your list.

1. In Jira, go to the list view.
2. Select a work item from the list to open the preview panel.
3. Drag the edge of the preview panel to expand it to the new maximum width.

Build automation rules with Rovo

Save time by using Rovo to generate automation rules in Confluence, Jira, and Atlassian Administration. You can now describe the automation you need in plain language, and Rovo will build the rule for you, making it easier to streamline your workflows without needing to manually configure every step.

To view this change in Jira:

1. Open Jira.
2. Navigate to the space where you want to add the automation rule and select Space settings.
3. Select Automation from the sidebar.
4. Select Create rule, then select Create with Rovo.
5. Describe the automation rule you want to create in the text field and follow the prompts to generate your rule.

Personalized onboarding emails for new users

Onboard to Jira with tailored tips delivered straight to your inbox. If you create a work item on your first day, we’ll send you a personalized email the next business day. This email highlights one of your incomplete task and offers up to five smart suggestions to help you add context and make your work more actionable.

1. Open Jira and create a new work item on your first day.
2. Ensure the work item is incomplete (for example, it's missing a description or hasn't been assigned).
3. Check your email the next business day for your personalized onboarding guide.

Get advance notice before Jira configuration limits are enforced

Jira Cloud admins now see a pre-enforcement banner on configuration pages for field options, issue security levels, grants per permission and priorities. The banner gives advance notice before limits are enforced, so admins can plan cleanup and optimization ahead of time.

To get started with this change:

1. Go to Settings in Jira Cloud.
2. Select the relevant configuration page, such as Fields, Permission schemes, or Space settings.
3. Look for the informational banner at the top of the page indicating upcoming limit enforcements for that entity type.
4. Use the reporting and streamlining tools on the page to review usage and clean up unused items before enforcement begins.

Create work items in batch with Rovo

Save time when using Atlassian Rovo to create multiple work items in Jira. You can now review, edit, and select multiple suggestions in a single preview card before creating them all at once.

To get started with this change

1. Open Rovo chat and enter a prompt to create multiple work items, such as "create 3 tasks for the marketing launch."
2. Review the suggestions in the preview card that appears.
3. Select the Edit icon on any suggestion to make changes in the Create work item dialog, then select Save to update the preview card.
4. Use the checkboxes to select specific items, or select Create all to generate the work items in Jira.

New work item view in beta

Jira is introducing a refreshed work item experience that provides a clearer layout and more prominent core actions. This update simplifies common tasks and helps you focus on the information that matters most without changing your underlying data or integrations. Admins can enable the new work item view for their site.

To enable the new work item experience for your site:

1. In Jira, select Settings in the top navigation.
2. Select System under Jira admin settings.
3. Select Beta features from the left navigation.
4. Find the Modern work item option and turn the toggle on.

Issue search: Warnings for JQL queries exceeding its supported limit

Jira now displays a warning banner when a Jira Query Language (JQL) search when it exceeded its supported limit. This helps you identify when a search might not return all expected results due to system limits, allowing you to refine your query for better accuracy.

To get started with this change

1. Navigate to the Issues menu in Jira.
2. Select Search for issues.
3. Enter a JQL query in the search bar.
4. If the query exceeds its supported limits, a warning banner will appear at the top of the search results.

Preview work items from the comments column in list view

Enjoy a more consistent experience when managing your work for business spaces in Jira. When you select a cell in the Comments column, work items now open in the preview pane to match other views across the app.

To view this change:

1. Open your business space in Jira and select List.
2. Locate the Comments column for any work item.
3. Select the comment icon or text in that column to open the preview pane.

Get advance notice before Jira configuration limits are enforced

Jira Cloud admins now see a pre-enforcement banner on configuration pages for versions, workflows, and components. The banner gives advance notice before limits are enforced, so admins can plan cleanup and optimization ahead of time.

1. Go to Settings in Jira Cloud.
2. Select the relevant configuration page, such as Workflows or Space settings.
3. Look for the informational banner at the top of the page indicating upcoming limit enforcements for that entity type.
4. Use the reporting and streamlining tools on the page to review usage and clean up unused items before enforcement begins.

Use the new filtering experience for boards, timelines, and calendars

We've updated the filtering experience in Jira to help you find and organize your work more efficiently. This refined interface, already available in software boards and lists, is now rolling out to business boards, business timelines, and calendars. These improvements make it easier to apply multiple filters and manage your view without losing context.

Filter work items

To use the new filtering experience:

1. Open a business board, business timeline, or calendar in Jira.
2. Select the Filters menu at the top of the view.
3. Choose the criteria you want to filter by, such as Assignee, Status, or Priority.
4. Select multiple values within a category to refine your results instantly.

App switcher: Collapsed sections for third-party apps

The app switcher now automatically collapses third-party apps into a single section when you have a large number of them installed. This change helps you find your Atlassian apps more quickly while keeping your workspace organized.

1. In Jira or Confluence, open the app switcher from the top navigation bar.
2. Scroll to the third-party apps section to find the More apps button.
3. Select the section to expand and view your third-party apps.

Search across multiple sites

Find the information you need efficiently by searching across multiple cloud sites at once with Atlassian Rovo. You can now include results from up to 5 connected sites in your search, giving you a comprehensive view of your work regardless of where it's stored.

This change is available to users who have access to multiple sites that belong to the same unit.

To view this change:

1. Open Confluence or Jira.
2. Select the search bar at the top. This opens the additional filter options.
3. Select the site selection filter to view your sites.
4. Choose up to 5 sites you want to include in your search.
5. Enter your search terms to see results from all selected sites.

Open your work item directly in Claude Code, now with native deep linking support

Jira Cloud now supports native deep linking for Claude from the status button in the work item view. This update improves the transition between Jira and Claude by using supported deep links, replacing the previous command line interface method.

1. Open a work item in Jira Cloud.
2. Select the deep linking icon.
3. Select Claude Code.
4. Enter a custom full path to your coding workspace.
5. Select Open in Claude Code to experience the work item context being passed to your agent.

Plans: Custom field limit enforcement

Jira now enforces a limit of 40 custom fields per plan to improve backend performance and ensure a faster loading experience. If your plan already exceeds this limit, you can continue to use and remove existing custom fields, but you won't be able to add new ones until the total count is below 40.

1. Open your plan in Jira.
2. Select the More actions (three dots) menu, then choose Plan settings.
3. Select the Timeline tab to view and manage your custom fields.

Improved install and setup for agents

Installing and setting up an agent from the Browse agents section in Jira is now clearer and easier. The install flow shows you what's happening as the agent installs, and the steps to configure the agent after install are more guided, so it's simpler to get your agent set up and ready to use.

1. In Jira, go to the Browse agents section.
2. Select an agent, then select Install or Request depending on your permissions.
3. Follow the guided steps to configure the agent after it installs.

Get an improved add status experience with the workflow editor

We've refreshed the add status experience in the workflow editor to make creating and choosing statuses clearer. We updated the wording throughout the dialog, and moved the create option into a fixed footer so it's always visible while you scroll.

To get started with this change:

1. Edit a workflow.
2. Select Add status in the toolbar at the top.
3. Select an existing status to add or create a new one.

Automation: Assign issues to teams using custom fields

Save time and improve workflow accuracy in Jira by automatically assigning issues to teams based on information in custom fields. You can now use the Assign issue action in the automation rule builder to assign an issue to the team stored in a People custom field, such as an On-call field.

To get started with this change

1. Go to Project settings, then Automation.
2. Create a new rule or edit an existing one.
3. Add the Assign issue/Edit issue/Clone issue/Transition action to your rule.
4. In the Assignee dropdown, select Team from custom field.
5. Choose the specific People custom field that contains the team information.
6. Select Save to update your action, then Turn on rule.

Add Rovo agents directly from the agent panel

Save time when managing work by adding Rovo agents directly from the Agent panel in Jira. You can now access the agent picker and add additional agents to a work item from the panel while other agents are already running.

To get started with this change:

1. Open a work item in Jira.
2. Locate the Agents section.
3. If agents are already working on the work item, you will see an Add agent button (+ icon) located in the top-right corner of the Agents section.
4. Select Add agent to open the agent picker. If no agents are assigned, select the Start work button to open the agent picker and add an agent.
5. Browse and assign another agent to your work item.

List view: Smart links in short text fields

Jira now supports smart links within short text fields in the List view. This update allows you to view and interact with rich previews of URLs directly from your table view, making it easier to access linked information without leaving your current context.

To get started with this change

1. Go to the List view in a Jira Space.
2. Locate a short text field that contains a URL.
3. View the URL rendered as a smart link.

Design coherence improvements including clearer labelling and purposeful motion

We’re modernizing the experience across Atlassian apps with UI improvements that make moving between apps, features and pages feel seamless. These updates to labelling, motion and shapes help you and your team get work done in a familiar, predictable way.

These improvements are rolling out progressively across apps from July 2026, beginning with with the apps listed here. Open any of your Atlassian apps, such as Jira or Confluence, to get started.

Comments: Truncation for long text

Jira now truncates long comments to help you scan through your work more efficiently. This change keeps your issue view clean and organized by showing only the beginning of lengthy discussions, allowing you to focus on the most relevant information first.

1. Open any issue in Jira that contains a long comment.
2. Select See more at the end of the truncated text to view the full comment.
3. Select See less to collapse the comment back to its truncated view.

Smart field suggestions now available for your custom fields

Speed up your workflow and reduce manual data entry with intelligent field suggestions in custom fields. By analyzing historical patterns within your specific project, Jira now surfaces the most relevant values for your custom configurations, allowing you to maintain data consistency and speed up work item creation without the manual search.

Smart field suggestions are available with Standard and Premium plans.

To view this change:

1. Ensure that Atlassian Intelligence is enabled for your organization. Admins can manage this setting by navigating to Organization settings then Atlassian Intelligence.
2. Once enabled, suggestions will appear automatically as you create issues work items in spaces with sufficient historical data.

Automation: New settings panel in the rule builder

We’ve moved several configuration options in the automation rule builder to a dedicated settings panel. This change helps you manage your automation rules more effectively..

To get started with this change:

1. Open an existing automation rule or create a new one.
2. Select the More menu (represented by three dots) in the rule builder.
3. Select Settings to open the new panel and manage your rule configuration.

List view: Group work items by agent

Organize your work more effectively in Jira by grouping work items by agent in the List view. This update allows you to see a structured, at-a-glance view of agent workloads, making it easier to identify, triage, and act on delegated work.

1. Open a list view or perform a global search in Jira.
2. Select Group from the view options.
3. Select Agent from the dropdown menu to organize your work items.

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.

A cleaner activity timeline in All work

We’ve updated the activity timeline in All work (previously Issue view). This improves readability and reduces clutter.

It's easier to scan and understand updates, 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.

These improvements enhance the ease of finding and understanding key changes in a work item’s history. A more structured and intuitive layout helps users quickly access relevant updates without overwhelming detail.

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.

Jira: Seamlessly add a due date and assignee when creating work items on a business board

You can now add a due date and assignee when creating a work item, without needing to leave the board view in your business project.

To create a work item with a due date and assignee on a business board:

1. Make sure you have the new navigation enabled (more about the new navigation).
2. From the board, select + Create in the column you want to create a work item for, and enter a summary.
3. Select the due date icon and choose a date from the date picker, or select the assignee icon and choose an assignee.
4. Select Enter to create your work item.

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

Jira: AI-powered child work item suggestions are now proactive

In addition to manually using AI to add child work items, you’ll now receive 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 more efficiently.

When you accept a suggestion, a new child work item will be created and linked to the parent work item.

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.

Beta: Link similar work items as you create with Atlassian Intelligence

Use AI to find and link similar work items or spot duplicates before they’re created.

When you create a new work item, Jira uses AI to automatically find and surface work items with a similar summary. You can then link the existing work items to the one you’re creating. It helps you quickly build context, connect past work, and understand complexity from the start.

Read more about Atlassian Intelligence features

To find and link similar work items:

1. Select Create from the global navigation.
2. Begin to add a Summary to the work item.
3. Jira will use AI to automatically surface similar work items below the Summary field.
4. Select Link to connect existing work items to the one you’re creating.
5. When you’re finished, select Create.

Once a work item is linked, it will display in the Linked work items panel on each work item.

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.

Request forms: New location in the request view

We've added an informational message in the Attached forms section of the work item view, as part of moving request forms to the Request details section in Jira Service Management. This message guides you to the new location of request forms in the Request details section. This message will only be shown if there are no other attached forms in the attached forms section.

1. Open a work item in the portal with a request form.
2. Find the message in the attached forms section if there are no other attached forms.

Human-recongnizable names for Assets objects in JQL

We've updated Jira Query Language (JQL) so that Assets objects now display as human-readable names instead of Atlassian Resource Identifier (ARI) values. This makes writing and validating JQL faster and easier.

To view this change:

1. Open your Jira app and navigate to Filters.
2. Enter a JQL query that includes Assets object operands.
3. View the improved results containing the Asset Objects' names.

Get improved search reliability with circuit breakers

Jira Service Management now includes circuit breakers for alert and incident search to improve service reliability during high-traffic periods. When the search cluster is unhealthy, affected search requests will fail fast with a service unavailable message instead of causing the entire app to slow down. This ensures that critical functions like alert creation, notifications, and on-call schedules continue to work normally even if search is temporarily degraded.

To get started:

1. Navigate to your service project and select Alerts or Incidents.
2. Use the search bar or filtered views to find specific items.
3. If the search cluster is unhealthy, you may see a "Service temporarily unavailable" message.
4. Wait 30 to 60 seconds for the circuit breaker to self-heal, then try your search again.

Notification events for unsubscribed reporters

When a work item notification to a reporter isn't sent because they unsubscribed from the work item, an event is now logged in the space's notification logs. This helps teams track when and why notifications are not delivered, improving transparency for Jira Service Management.

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.

A cleaner activity timeline in All work

We’ve updated the activity timeline in All work (previously Issue view). This improves readability and reduces clutter.

It's easier to scan and understand updates, 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.

These improvements enhance the ease of finding and understanding key changes in a work item’s history. A more structured and intuitive layout helps users quickly access relevant updates without overwhelming detail.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

Manage views directly from the space navigation

Project admins can now add or remove views directly from the space navigation, giving them more flexibility to customize the space to suit their team's need.

To add a view, select the plus icon + in your space navigation and choose which view you want to add.

To remove a view, select the tab options menu (...) next to the tab name, and then select Remove.

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:

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

Back up and restore Jira Service Management Assets

Assets in Jira Service Management is now included in the backup and restore of your Atlassian Cloud services.

1. Make sure you have the required permissions to use backup and restore features in your JSM site.
2. Go to the backup and restore section in your Atlassian Cloud admin settings.
3. Follow the steps to create a backup or restore your JSM Assets data.

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 and organize work by Focus area in Jira Plans

You can now view, filter, and group work by Focus area directly in Jira Plans. This integration lets you see which Focus areas are linked to your Jira work items, making it easier to align and organize your planning. The Focus area field is read-only for now and available to select customers.

To see and use Focus areas in your Jira Plans:

1. Open a plan in Jira Plans where Focus is provisioned for your site.
2. Look for the new Focus area field in your plan’s fields.
3. Use the filter or group options to organize work by Focus area.
4. If you don’t see this feature and have both Focus and Jira Plans, reach out to your Atlassian contact or the #focus-area-in-plans Slack channel to request access.

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.

Unsubscribe option in customer invitation emails

Customer invitation emails in Jira Service Management now include an unsubscribe link, so customers can easily opt out of future invites. When a customer unsubscribes, they no longer receive invitation emails, and new invitations are logged in the project's Customer notification logs.

Field configuration schemes: Field limits for optimized performance

To ensure your Jira apps remain fast and reliable, we’re introducing a limit on the number of fields you can add to a field configuration scheme. This change helps maintain site performance by preventing overly complex configurations that can slow down your experience.

If you have an existing support ticket regarding this change, please refer to the latest communication from support for the most up-to-date information applicable to your instance.

To get started with this change:

1. Go to Settings, then Work items.
2. Select Field configuration schemes.
3. View your existing schemes and try to add a new field configuration to a scheme.
4. If a scheme is already at the limit, Jira will prevent you from adding more fields to it.

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

Limits for work item types and fields

We’re introducing limits and guardrails for work item types and fields to improve site performance and scalability. You’ll see a warning if a space exceeds 700 fields or 150 work item types. To keep your site running smoothly, you won't be able to add more until the space is back within these limits.

Understand data limits and guardrails

To get started with this change:

1. Open Jira.
2. Select Settings (cog icon) in the top navigation bar.
3. Under Jira admin settings, select Work items.
4. Select Work item type schemes or Field configurations.
5. Look for a warning message on schemes that exceed the recommended limits.
6. Use the Site optimizer to identify and remove unused fields or work item types to bring your space back within the limits.

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.

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

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.

Assets Data Manager: A simpler, more powerful admin experience

We’ve updated the admin experience for Assets Data Manager in Jira Service Management to make setting up and managing your data sources easier, faster, and more intuitive. This new Data Manager admin experience ensures a consistent look and feel with the Atlassian apps you already use. We’ve also updated several key terms to be more descriptive of their function, helping you navigate your asset data with less friction.

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.

Prompt for Jira users to return to Confluence after inactivity

If someone has access to both Jira and Confluence but has not used Confluence in the last 28 days, they will now see a flag in Jira encouraging them to rejoin their team in Confluence. This flag includes a direct link to Confluence Home and an option to dismiss the message.

To see and interact with this new flag in Jira:

1. Log in to Jira with an account that also has access to Confluence.
2. If you have not been active in Confluence for at least 28 days, look for a flag at the top of your Jira screen.
3. Select "Go to Confluence" to visit Confluence Home, or select the "X" icon to dismiss the flag.

Add comments when flagging work items in Jira

In Jira, you can now add a comment whenever you flag a work item, no matter where you do it. Previously, you could only add a comment from views like the board, backlog, or the command palette in the work item view. This update adds the same comment prompt when you add or remove a flag from the More actions (•••) menu in the work item view, giving your team consistent context about why work is flagged as at risk.

To get started with this change:

1. In Jira, open the work item you want to flag.
2. Add or remove a flag from any supported view (board, backlog, command palette, or work item view).
3. When prompted, add a comment to explain why the work is at risk.
4. Save your changes.

Beta: Link similar work items as you create with Atlassian Intelligence

Use AI to find and link similar work items or spot duplicates before they’re created.

When you create a new work item, Jira uses AI to automatically find and surface work items with a similar summary. You can then link the existing work items to the one you’re creating. It helps you quickly build context, connect past work, and understand complexity from the start.

Read more about Atlassian Intelligence features

To find and link similar work items:

1. Select Create from the global navigation.
2. Begin to add a Summary to the work item.
3. Jira will use AI to automatically surface similar work items below the Summary field.
4. Select Link to connect existing work items to the one you’re creating.
5. When you’re finished, select Create.

Once a work item is linked, it will display in the Linked work items panel on each work item.

Automate Jira work item approval with smart values

We've introduced new smart values to refer to the manager of a Jira work item reporter or assignee. For example, you could use these smart values to automatically set the approver of a Jira work item to the assignee’s or reporter’s manager.

The new smart values include issue.reporter.manager or issue.assignee.manager.

1. Check the manager you want to refer to is set up through User Provisioning.
2. Set up an approver workflow for Jira or Jira Service Management.
3. Open the automation rule builder in Jira or Jira Service Management.
4. Select a trigger for your rule.
5. Add the action Edit Work Item and select More Options.
6. Add the smart value in the Additional Fields section as code.
7. Once the trigger you set up is triggered, the manager of the assignee is added as the approver.

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.

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

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.

New automation action: Add stakeholders to incident

You can now automatically add stakeholders to incidents using the new Add stakeholders to incident action. This helps streamline communication and ensures the right people are kept informed during incident response.

To give the new automation component a try:

1. Navigate to either project automation (in Jira) or global automation.
2. Create a new rule, or edit an existing rule.
3. Add the new Add stakeholders to incident action to your automation rule.
4. Configure the action to specify which stakeholders to add when the rule is triggered.

New post-incident review automation feature (Premium and Enterprise only)

You can now use the new post-incident review automation feature in Jira Service Management plans (Premium and Enterprise). This helps your team capture learnings and follow-up actions as part of incident resolution.

To use the new post-incident review in automation:

1. Select Space settings, then Automation.
2. Create or edit an automation rule.
3. Add the post-incident review automation to your rule.
4. Edit the title and description using smart values or fields from the incident.
5. Publish your rule.

A better way to manage threaded comments in Jira

This update introduces the ability to show and hide threaded comments in Jira. This makes it easier to focus on the most relevant conversations, and reduces visual clutter when working with long comment threads.

To try out the new threaded comment show/hide feature:

1. Open any work item in Jira that contains threaded comments.
2. Select Hide replies to collapse replies within that thread. Select Show more replies to expand them again.

New automation to set Slack channel topics during an incident

We're adding a new automation action that lets you set the topic of the Slack channel linked to an incident, helping your team keep incident channels up to date with relevant information.

This automation is available for Premium and Enterprise plans.

To use the new automation:

1. In your site settings, select Operations then Chat and Video Tools.
2. Update your Slack app to grant permission for the automation to set channel topics. Here, you'll see a message to grant permission if required.
3. Go to your space settings and select Automation.
4. Create or edit an automation rule.
5. Add the Select channel topic for incident Slack channel action.

Multi-project queue view

We have introduced a new way to view and manage work items across multiple projects in Jira Service Management. This update allows you to see queues from several projects in a single, unified list view, making it easier to track and prioritize work items without switching between projects.

To access and use the new multi project queue view:

1. Open Jira Service Management in your Atlassian app.
2. Navigate to the Views section from the main menu.
3. Select the new List option to see work items from multiple projects in one place.

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.

Field schemes: A new way to manage fields

Jira admins can now use field schemes to manage which fields are available and required for different work types. This new experience replaces the legacy field configurations and field configuration schemes, providing a more intuitive way to ensure projects only include relevant fields.

To use field schemes:

1. Go to Jira settings, then Work items.
2. Select Field schemes from the sidebar.
3. Choose an existing scheme to edit or select Create field scheme to start a new one.
4. Use the Advanced settings sidebar to specify which work types a field is available or required on.

Public status pages for incident communication

Create and manage branded, public status pages directly within Jira Service Management Enterprise. These pages help you communicate service health and incident updates to your stakeholders. You can also have Atlassian Intelligence automatically suggest titles and messages for status page updates (open beta).

Manage and customize your status pages

To set up a status page:

1. In Space settings, go to Operations, then Status pages.
2. Select Create status page to set up a new public page for your site.
3. In the Appearance and Advanced settings tabs, customize your page appearance, including logos, colors, and custom domains.
4. Add services from your Services registry to display their health status on the page.

When viewing an incident, select the Status page option to post updates directly to your public page.

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.

Jira ‘projects’ will soon be renamed ‘spaces’

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.

As part of these efforts, the term project will soon be replaced with space across all Jira Cloud products, including Jira Service Management and Jira Product Discovery.

• Read more about these changes on the Atlassian Community

This change builds on previous terminology updates, like the transition to 'work' in Jira.

Introducing work item priority variable for customer notifications

We're adding a new variable called work item priority to customer notifications. You can add this variable to your notification templates to insert the priority of a work item in your message.

To add variables to your notification templates for customers:

1. From your service project, select Project settings, then Notifications, then Customer notifications.
2. Choose the notification you want to edit, then select Edit.
3. Under Content, select Insert variable to add variables and pull blocks of information from work items.
4. Select Save to confirm your changes.

Improved commit message for Git commands in software projects

We've updated the Git commit message to include the work item summary, making it easier to create commits without manually adding work item details.

To use the updated commit message:

1. Go to your Jira software project.
2. Open a work item.
3. In the development field, select Create commit.
4. Select Copy to copy the updated Git command, which now includes the work item summary.

Asset object variable available in customer notifications

We've added an asset object variable directly to a work item, allowing you and your team to easily view when a work item is updated or created.

To add an asset object variables to your work items:

1. From your service project, select Project settings then Notification.
2. Under Notification, navigate to Customer notifications and select a notification you want to edit.
3. In the Content field, select Asset object under Insert variable.
4. Select Save to confirm your changes.

New Attribute value changed trigger for Assets automation

In Jira Service Management, Assets automation now includes a new Attribute value changed trigger. You can use it to run rules when specific object attributes change, instead of only reacting to object-level events like create, update, or delete. This gives admins more precise control over automation and can reduce manual updates and workaround rules.

To get started with this change:

1. In Jira Service Management, go to a project that uses Assets and open Project settings.
2. Select Automation, then create a new rule.
3. In the rule builder, select Add trigger.
4. Choose the Assets category.
5. Select the Attribute value changed trigger.
6. Configure the object schema, object type, and attributes you want to monitor.
7. Add any conditions and actions you need, then select Turn on rule.

A better way to improve descriptions with Google Docs links

You can now use Google Docs links when improving work item descriptions. This update makes it easier to bring in content from your favorite document tool to help you write better work item descriptions.

To use Google Docs links in the description improver:

1. Open a work item where you want to improve the description.
2. Paste a Google Docs link into the description field.
3. Select Improve description.
4. Follow the prompts to generate an improved description using your linked Google Doc.

This functionality is also available while creating a new work item.

We’re changing the term 'products' to 'apps’

In support of Atlassian’s System of Work and our evolution toward a unified Atlassian platform, we’re 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 experiences. Over the coming months, we’ll continue to roll this out to Atlassian apps, web sites, 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.

Configure real-time chat for internal service teams

We're excited to announce Live chat, a real-time chat channel to assist internal support teams. This new capability lets admins to turn on real-time chat from their space settings, configure how conversations route to agents, and manage all interaction in a dedicated live chat inbox.

To configure live chat for your team:

1. From your service space, select Space settings, then Channel & self service, then Live chat.
2. Create a Rovo agent with a live chat skill or update an existing agent to work with live chat.

Assets is now a standalone platform app

To ensure we give our customers a seamless and secure experience, we're moving Assets from Jira Service Management as its own platform app in Atlassian Administration. Here, you can assign specific roles to people as well as manage billing and data residency. Existing permissions and access will be automatically migrated to minimize any disruptions.

Assets: Increased limit for custom fields

The Assets custom field now supports linking up to 200 objects per field on Jira work item screens (create, edit, view, and transition), Jira Service Management portal and forms, and work item history - a 10× increase from the previous limit of 20. On Jira Service Management queues, list view, board and backlog views, and gadgets and dashboards, the limit increases from 20 to 50.

The field introduces pagination, search, and multi-select, so you can efficiently browse, filter, and select from large sets of linked assets without leaving the issue.

No configuration changes are required for existing Assets custom fields. The increased limit (20 → 200) and new paginated UI apply automatically.

Emails processed by multiple mail handlers

Jira Service Management now allows a single email sent to multiple project email addresses to be processed by each relevant mail handler. This means a separate request is created in each service project, helping teams capture and track requests across multiple projects for improved collaboration and visibility.

1. Send an email to multiple Jira Service Management project email addresses by including several service project addresses in the “To” field.
2. Check each relevant service project to confirm that a request has been created for each addressed email.

Service registry is now powered by Assets

We've updated the services experience in Jira Service Management to provide a more flexible and extensible way to manage your service catalog. We’ve moved services to a new backend powered by Assets. This allows you to add custom attributes, set granular permissions, and create custom object types for your services. This change helps you maintain a single source of truth for all your services and their relationships across your organization.

To get started with this change:

1. Go to the Operations menu in the navigation sidebar.
2. Select Services to view your updated service list.
3. Select a service to view its details, or select Create service to add a new one using the new object types.
4. To manage service schemas and attributes, go to Assets and look for the Software Registry and Business Portfolio schemas.

Activate apps faster from the template picker

App admins of Atlassian organizations that have only Jira apps can now activate Jira Service Management and Jira Product Discovery directly from the template picker. This simplifies the setup by combining app activation and project creation into a single step, helping you start using new features faster.

To view this change:

1. Open the Jira template picker.
2. Select a Jira Service Management or Jira Product Discovery template.
3. Review the template preview and app overview on the new setup page.
4. Select the checkbox to accept the product terms.
5. Select Try this template to activate the app and create your project.

Assets: Automate rules with multiple attributes

Save time and reduce the number of automation rules in Jira Service Management by configuring multiple attributes within a single trigger. You can now use the Attribute value changed trigger to detect changes across single-valued, multi-valued, and inherited attributes for your objects.

To get started with this change:

1. Go to your service project and select Project settings, then Automation.
2. Select Create rule and choose the Attribute value changed trigger.
3. Select the object type and the specific attributes you want to monitor.
4. Add your desired conditions and actions, then select Turn on to activate the rule.

Workforce management: Intelligent routing and scheduling

Manage your team’s capacity and automate work assignment with new workforce management features in Jira Service Management. These tools help service teams plan coverage across time zones, track real-time agent availability, and ensure work is automatically routed to the right person based on their current schedule and workload.

1. In Jira Service Management, select Workforce from the navigation sidebar.
2. Select Set up workforce management.
3. Complete the onboarding steps to connect your teams.
4. Select the toggle to enable workforce management for your project.

Mention a request participant even if they haven't commented before

Agents and administrators can now mention any request participant in a work item or comment, even if the participant has not previously commented. This makes it easier to collaborate and keep all relevant people informed.

To get started with this change:

1. As an agent or admin, open a Jira Service Management work item.
2. In the work item's description or comment, type @ followed by the name of any request participant to mention them.

Assets: Enhanced automation with inherited and multi-valued attributes

Jira Service Management has expanded the capabilities of the Attribute value changed automation trigger. You can now configure multiple attributes within a single rule, support both single-valued and multi-valued attributes, and detect changes in inherited attributes for child object types.

To get started with this change:

1. Go to Project settings, then Automation.
2. Select Create rule and choose the Attribute value changed trigger.
3. Select the object type and the specific attributes you want to monitor.
4. Configure your conditions and actions, then select Turn on rule.

Playbooks: Get suggestions from Rovo

Get playbook suggestions for your Jira Service Management work items with the new Suggest playbook option. Rovo analyzes the work item and suggests relevant playbooks curated by your space admin, or prompts you to contact an admin if none are available.

To get started with this change:

1. Open a work item in Jira Service Management.
2. Go to the Playbooks section.
3. Select Suggest playbook to start a chat with the Rovo Ops agent and view any suggested playbooks.

Assets: Automation support for multi-valued attributes

Jira Service Management has updated the Attribute value changed automation trigger to support multi-valued attributes. This allows you to trigger automation rules when changes occur in attributes that contain more than one value, providing more comprehensive coverage for your asset management workflows.

To get started with this change:

1. Go to Project settings, then Automation.
2. Select Create rule and choose the Attribute value changed trigger.
3. Select the object type and the multi-valued attributes you want to monitor.
4. Configure your conditions and actions, then select Turn on rule.

Filter notifications for new hire events in Jira Service Management

Organization admins can now filter notifications for Workday new hire events in Jira Service Management. This change allows admins to specify which new hire events trigger notifications, ensuring that only relevant updates are sent to the appropriate teams.

To use this feature, you must have Workday integration with Automation set up.

To filter notifications for new hire events:

1. Go to your service space in Jira Service Management and.
2. Select Space settings next to the space name in the sidebar*,* then select Automation.
3. Create a new rule with a worker added or updated in Workday.
4. Select the required Notification triggers and add a corresponding action, for example, creating a work item.
5. Apply and save the automation rule to filter the New hire event to specify your notification criteria.
6. Enable the saved automation rule.

Your automation is now ready to receive and filter new hire notifications from Workday based on selected triggers.

Comments: Performance, reliability, and look-and-feel improvements

Jira Service Management (JSM) has improved the way comments are processed to provide a faster and more reliable experience. By updating the underlying technology used to handle comments, we’ve reduced load times and increased the stability of your service projects.

We've also modernized the look of JSM comments to make them more consistent with other apps.

To see these changes in the UI:

1. Open any request in your service project.
2. View or add a comment in the activity section.

Risk assessment: AI-powered insights for change management

Quickly assess change risk from Rovo or directly within Jira Service Management. This update introduces an explicit Rovo command to trigger AI-powered risk assessment on demand, alongside the existing in-product risk panel. AI scans change details, history, and related context to generate a risk level and suggest mitigation steps, helping teams make faster, more consistent decisions.

To get started with this change:

1. In Jira Service Management, open any change request within your service project.
2. In Rovo, type /assess-change-risk and select the command to explicitly invoke AI risk assessment for the currently selected / linked change.
3. Review the generated risk level (Low, Medium, or High) and the accompanying narrative explanation returned by Rovo.
4. (Optional) Open the change issue and locate the AI risk assessment panel on the right side of the issue view for an in‑context view of the same assessment.
5. Follow the suggested mitigation steps to reduce potential impact before approving or scheduling the change.

Send message on incident Slack channel: Attach files to automation messages

You can now attach up to 10 files (totaling 4MB) to messages sent using the "Send message on incident Slack channel" automation action in Jira Service Management. This helps responders access runbooks, checklists, and supporting materials directly in Slack, reducing context switching and speeding up incident response.

1. Go to Project settings in Jira Service Management.
2. Select Automation and edit or create a rule using the Send message on incident Slack channel action.
3. Save the rule configuration.
4. Add up to 10 files (maximum total size 4MB) as attachments in the action settings.
5. Ensure your Slack app is updated to grant file upload permissions in the Chat and Video Tools admin page.

Help center: Improved knowledge base search relevance

The Jira Service Management help center has been updated to improve how knowledge base articles are ranked when help seekers search for information. This update ensures that the most relevant content, including articles from third-party sources, is prioritized, helping your customers find the right answers faster and reducing the need for them to raise a request.

To get started with this change:

1. Go to your Jira Service Management help center.
2. Enter a query in the search bar.
3. Review the search results to see the improved ranking of relevant knowledge base articles.

New way to start agent sessions in the work item

You can now trigger an agent session for a work item by clicking the Agents button and selecting an agent.

To get started with this change

1. Open a work item in your Jira software or business space.
2. Click on the Agents button to see a list of agents available to collaborate in Jira.
3. Use the search field to narrow down your results.
4. When you select an agent, it will immediately get to work, and you can view the session from the Agents section of the work item.

Service management: Import from CSV in the template gallery

Jira Service Management now includes an Import into JSM (CSV) option directly within the Service management and Jira Service Management template gallery. This update allows teams to quickly set up a realistic project by importing historical tickets, users, and configurations from other service management tools.

To get started with this change:

1. Go to the Service management or Jira Service Management category in the template gallery.
2. Select Import into JSM (CSV).
3. Follow the prompts in the import wizard to upload your CSV file and map your data.

Email logs: Access all notifications from one page

Jira Service Management project admins can now view both outbound customer notifications and inbound email logs from a single Email logs page. This unified experience eliminates the need to switch between the notification settings and the email channel configuration to diagnose delivery issues, saving you time when troubleshooting communication with your help seekers.

1. Go to your service project and select Project settings, then Email logs.
2. Select the Customer notifications tab to view outbound logs for customer invites and request notifications.
3. Select the Incoming emails tab to view inbound logs.
4. Use the channel selector dropdown to choose a specific email channel and toggle between Processing log and Connectivity log to see detailed activity.

Service Collection: New feature discovery for Standard plan trials

When you start a Standard plan trial for Service Collection you’ll now receive a feature-focused email and see in-app notifications to help you understand the benefits of your new plan. These updates provide a clear overview of available features and billing information so you can make the most of your trial.

1. Start a Standard plan trial for Service Collection.
2. Check your inbox for an email highlighting key features and the benefits of the Standard plan.
3. Log in to your app to view the trial awareness dialog for an overview of your trial.
4. Select the plan awareness lozenge in the navigation bar to open the plan benefits dialog.
5. Review the dialog to see which features are now available and find your billing plan information.

Incoming email: Improved findability for raw email files

Admins can now more easily find and download the raw incoming email file from Jira Service Management incoming email logs for faster troubleshooting. This update improves the visibility of an existing action only and does not change how raw email downloads work.

To get started with this change:

1. Go to Space settings → Channels and self service → Email.
2. Click View logs for the relevant email channel.
3. Use Download raw email message to retrieve the raw email file.

Surveys: Gather feedback from your customers

Surveys in Jira Service Management give you a simple way to listen to people across your organization at key moments, without the need for extra tools. Surveys now lets you categorize surveys by type, control single or multiple response submissions and browse surveys in a filterable table view.

Check to see if you have Surveys: If you don’t see Surveys in the navigation on the left in your service space, you’ll need to activate it.

You need to be a space admin to activate surveys, in Features.

Then, follow these steps:

1. Go to your service space and select Surveys.
2. Turn on the toggle next to Surveys, then return to your Space from the navigation on the left and select Surveys.
3. Select Create survey or select the survey you want to review.
4. Select More actions (ICON) in the top right.
5. Select Settings.
6. Select your survey category under General or manage single response collection in Responses.

Improve writing: Enhance incident comments

Save time and communicate more clearly by using artificial intelligence to improve your incident comments in Jira Service Management. This feature helps you refine your language and ensure your updates are professional and easy to understand for all responders.

To get started with this change

1. Open an incident in your service project.
2. Go to the comment section in the work item view.
3. Select Improve writing to see AI-generated suggestions for your text.

Knowledge base: Build articles from scratch with Rovo

Remove the onboarding friction of setting up a knowledge base in Jira Service Management. This new feature lets you add a knowledge base to your space effortlessly. Atlassian Rovo generates draft articles for you to review and publishes them to a Confluence space, so your customers can start finding answers immediately without agents needing to write articles from scratch.

To generate a knowlege based article using Rovo:

1. Go to your service space and select Knowledge base from the sidebar.
2. Click Set up knowledge base.
3. In the dialog that opens, select Create with Rovo.
4. Edit the pre-filled prompt if required to tailor the content to your space's needs.
5. Rovo will generate draft articles for you to review.
6. Review the drafts. Publish them or save as drafts.
7. Choose the Confluence space where the articles will be published or saved as drafts.

Surveys: New ratings and scale question types

Jira Service Management surveys now include ratings and scale question types, giving you more ways to collect feedback across your organization. You can add these new question types to your surveys using the survey builder.

To add new question types:

1. Go to your service space and select Surveys. Make sure you’ve activated surveys, in Features.
2. Select the survey you want to edit or create a new one.
3. Select Add field then drag and drop the Ratings or Scale question types into your survey.
4. Configure your question options, such as the number of stars or label ranges.
5. Select Save to update your survey.

Actions menu: Organized playbook and automation rules

Responders in Jira Service Management can now see a clear distinction between playbook-step rules and standalone automation rules within the actions menu. This update organizes the menu into two sections, making it easier to choose between guided resolution steps and quick, singular actions.

To get started with this change

1. Open any work item, such as an incident, in Jira Service Management.
2. Select the Actions menu (lightning bolt icon).
3. View the categorized sections for playbook actions and automation rules.

Rovo Slack App : Use RovoOps agent in incident/alert channels

Jira Service Management now supports RovoOps agent in Slack This update allows your team to use AI-powered agents to automate tasks and find information directly from your chat app, helping you resolve incidents and requests faster.

1. Connect an incident or an alert to an existing channel or create a new one.
2. The Rovo Slack app gets added to your incident/alert channel with RovoOps configured.
3. You can chat with the RovoOps in these channels with @Rovo queries.

Issue view: Collapsible sections

Manage information density in Jira Service Management by collapsing and expanding sections in the issue view. This change allows agents to hide less relevant details and focus on the most important work, with their preferences saved across sessions.

To get started with this change

1. Open any issue in your service project.
2. Select the collapse icon next to a section header, such as Key Details, Attachments, or Linked items, to hide its content.
3. Select the icon again to expand the section when you need to view the information.

Private status pages: Secure incident communication

Jira Service Management now offers private status pages to help you communicate incident updates securely with specific internal or external audiences. Unlike public pages, private status pages require visitors to sign in and be members of an Atlassian identity group linked to the page. This ensures that sensitive system health information is only visible to authorized users, such as internal employees or enterprise partners, without consuming additional agent or portal-user license seats.

1. Go to Operations, then Status pages.
2. Select Create status page.
3. Choose Private as the page type.
4. Link up to 10 Atlassian identity groups to define who can access the page.
5. Configure your components and branding, then select Publish.

Automation templates for operations teams

Atlassian Rovo now includes pre-configured automation templates specifically designed for operations teams to automate tasks such as incident triage and PIR creation. These templates help you quickly set up automation rules to manage repetitive tasks and streamline your operations workflows across Atlassian apps. A new section on the Rovo Ops settings page lists the available templates. You can select a template to open it in Jira Service Management automation, from there you can edit the template and turn it on.

To get started with this change:

1. Go to the Rovo Ops section in your Space settings You’ll see a new Automate workflows with Rovo Ops section.
2. From the Automate workflows with Rovo Ops section, choose a template.
3. Select Turn on to activate the rule or customize it in the automation editor.

OR

1. Go to the Automation library in your app.
2. Select the Templates tab.
3. Select a template from the Rovo AI category.

Knowledge base: Link Confluence folders to your service project

Project admins can now link individual Confluence folders to a Jira Service Management knowledge base. This allows for finer control over the content surfaced to agents and help seekers by linking specific sub-sections of a space rather than the entire space. This feature supports both native Confluence folders and cross-site folders within the same Atlassian organization.

1. Go to your service project and select Space settings, then Knowledge base.
2. Select Add knowledge.
3. Select site and visibility.
4. Select Content → Folder
5. Select the folder you want to link from the dropdown and select Link.

Assets: Scoped Bitbucket repository selection

Assets is improving how you manage Bitbucket repositories by introducing workspace-scoped selection. This change ensures that repository searches and selections are faster and more reliable by focusing on specific Bitbucket workspaces.

1. Go to Assets in Jira Service Management.
2. Select an object schema, then select an object type that uses the Bitbucket repository attribute or create a new Bitbucket repository attribute.
3. In the Type Value field, select the Bitbucket workspaces you want to allow for this attribute.

Workday panel in the agent work item view

Agents working on HR service management spaces in Jira Service Management can now view Workday employee data for a reporter directly within the work item. This collapsible panel surfaces essential context, such as work schedules and time-off summaries, helping agents resolve HR requests more efficiently without switching between apps.

To view the Workday section:

1. Open a work item in an HR Service Management space.
2. Locate the Workday section in the right-hand context panel.
3. Select the section to expand it and view the reporter's work schedule and time-off information.

Unified AI resolution experience

Agents can now access all AI assistance from a single Resolve with Rovo panel in the work item view. This unified experience automatically surfaces the most relevant AI-powered help—like Rovo-generated resolution plans or suggested actions—based on the context of the request. This simplifies workflows and helps agents resolve issues faster without switching between different sections.

To view this change:

1. Open a service space in Jira Service Management.
2. Select a work item to open the work item view.
3. Locate the Resolve with Rovo section on the work item.
4. Interact with the resolution plan or suggestions to help resolve the request.

Updated colors for approval buttons

The Approve button in the Jira Service Management approval panel is now primary blue instead of green. This update aligns the panel with the Atlassian design system, providing a more consistent and familiar experience when you manage approvals across Atlassian apps.

To view this change:

1. Open a request in Jira Service Management that requires your approval.
2. In the work item view, locate the Approvals section.
3. Select the new blue Approve button or the Decline button to complete your action.

Invite users with pre-selected roles

Space admins can save time when adding new team members to Jira Service Management and Customer Service Management. We've updated the invite modal to automatically pre-select the most likely role based on where you are in the app, ensuring new users get the right access and permissions from day one.

To invite users with pre-selected roles:

1. Go to your service space.
2. Select Add people from the navigation bar or go to Space settings, then People. Or, select Invite team on the Get started page of Jira Service Management.
3. Enter the email addresses of the people you want to invite.
4. Review the pre-selected role, then select Add to send the invitations.

View active journeys

You can now view a table of work items that are parents of journeys currently executing in Jira Service Management. This new page helps you track and manage active journeys more efficiently by providing a centralized view of their parent work items.

1. Go to your service space.
2. Select Journeys from the space navigation on the left.
3. Select the Active tab to view the table of work items.

Custom domains for communication status pages

Jira Service Management now supports custom domains for communication status pages. This update allows you to use your own branded URL for status pages, providing a consistent experience for your customers during service updates and incidents. We've also updated the user interface to make it easier to configure and manage these domains within your service project.

1. Go to you Operations, then Status page.
2. Click on Edit for any status page using … and then go to Advance Settings tab
3. Navigate to “Custom URL” and follow the prompts to configure your custom domain and update your settings.

Recruitment capabilities for HR service projects

Save time and streamline your hiring process with new recruitment capabilities in Jira Service Management. When you create a new company-managed space using the HR Service Management template, you can now include dedicated tools for managing candidates and requisitions. These updates provide your HR teams with specialized workflows, queues, and work types to manage the entire recruitment lifecycle in one place.

1. In Jira Service Management, go to Spaces, then select Create space.
2. Select the HR Service Management template.
3. Choose Use template, then select Company-managed.
4. Enter details and select Create space.
5. View your new recruitment tools in the sidebar under Queues and Request types.

Knowledge base: Link multiple spaces to a single service space

Space admins can now link multiple knowledge sources (native Confluence, cross-site Confluence, and third-party sources) to a single Jira Service Management service space. This update allows your team to pull knowledge base articles from various sources, making it easier for your team and help-seekers to find the information they need in one place.

1. Go to your service space and select Space settings.
2. Select Knowledge base.
3. Select Link space.

Onboarding: Use-case driven project setup

New Jira Service Management users can now get started faster with a simplified onboarding experience that suggests the best project templates for their specific needs. By selecting a team type, such as IT support or HR, users receive tailored template recommendations that reduce setup time and help them realize value from the Jira Service Management app more quickly.

To get started with this change

1. Sign up for a new Jira Service Management site.
2. On the What kind of work do you do? screen, select the team type that best describes your work.
3. Choose one of the recommended templates to immediately kick off your project creation.
4. If you prefer to see all available options, select Explore more to view the full template gallery.

Assets: Usability improvements for Data Manager

We’ve made several usability improvements to the Assets Data Manager admin journey in Jira Service Management. These changes refine the experience for admins following the recent release of the new Data Manager journey, making it easier to manage your data.

To get started with this change

1. Go to your service project.
2. Select Assets from the navigation on the left.
3. Select Data Manager to view the updated admin journey.

Assets Data Manager: New transform functions for data imports

Clean and normalize your imported data more efficiently in Jira Service Management, Assets Data Manager, with two new transform functions in Data Manager: Trim right by count and Trim right by pattern. These functions allow you to automatically remove unnecessary characters from the end of your data strings during the import process, ensuring your asset information remains consistent and easy to manage.

1. Go to Assets, then select Object classes.
2. Select Show data sources for the Object class you need to modify.
3. Select the name of the data source to edit and then click Modify transforms.
4. Select a transform or start typing… (eg trim).
5. Choose Trim right by count or Trim right by pattern from the function list.

Save time with automatic status updates

Jira Service Management now automatically updates agent availability status based on activity. This gives your team a real-time view of who is ready for work, improving routing accuracy without the manual effort.

To get started with this change:

1. In Jira Service Management, navigate to the Space settings of your space.
2. Select Workforce, then Availabilty.
3. View the real-time availability of your team members. This is based on agent interaction with pages in Jira Service Management spaces, such as mouse clicks, page scrolling, or typing.

Agent availability control in profile menu

Manage your availability for work directly from your profile menu in Jira Service Management. This change allows agents to toggle their status between available and unavailable, ensuring that work is only routed to those who are ready to receive it.

1. In Jira Service Management, select your profile avatar in the top navigation bar.
2. Select your current availability status from the menu.
3. Select a new status, such as Available or Unavailable, to update your availability.

Emoji picker: Refreshed UI and new Atlassian emojis

We've updated the emoji picker across Atlassian apps, including Jira, Confluence, and Jira Service Management, to provide a more modern experience. This refresh includes a new set of Atlassian emojis, making it easier for you to express yourself and collaborate with your team.

1. Open any content where you can use emojis, such as a Jira work item or Confluence page.
2. Select the emoji icon in the editor toolbar or type a colon (:) to open the emoji picker.
3. Explore the refreshed interface and select from the new set of Atlassian emojis.

Surveys enabled by default for Standard plans

Jira Service Management Standard customers now have surveys enabled by default across all spaces. If you have a Standard plan, this update helps you collect feedback immediately, regardless of the space template you use. Surveys remain available for all customers on Standard, Premium, and Enterprise plans

To manage surveys with this change:

• For Standard customers, there’s nothing you need to do. Surveys are now enabled by default for all Jira Service Management spaces, so they’ll appear automatically.
• If you’d prefer not to use surveys in a space, you can turn them off by going to Space settings, then Features, and updating the surveys setting.
• For Premium and Enterprise customers, surveys can continue to be enabled for all spaces from the same Features page in Space settings.

View forms directly in the Key details section

Agents can now view forms submitted by help seekers directly within the Key details section. This change moves forms from the Attached forms section to a more prominent location, allowing agents to access critical information faster without switching views.

Note that this change applies only to requests created after this change rolls out.

To view this change:

1. Create any request in your Jira Service Management space with a form.
2. Locate the Key details section at the top of the agent work item view.
3. View the submitted form information directly within the panel.

Manage delivery risks with Jira Delivery Agent

Jira now includes the Jira Delivery Agent, a Rovo Agent designed to help you manage your work more effectively. This agent reads Jira work, identifies delivery risks early, and turns issue activity into clear, actionable updates. By using the Jira Delivery Agent, you can make more informed decisions and keep your team on track.

To use the Jira Delivery Agent:

1. Open Rovo Chat in your Jira space.
2. Select the Rovo dropdown menu.
3. Search and select the Jira Delivery Agent to begin the analysis of your work.

View and manage Studio flows in Product Automation

Manage your automation flows more effectively with the new ability to view Studio flows directly within Product Automation. This update provides a centralized view of your flows, making it easier to track and organize automated processes across your Atlassian apps.

1. Open your Atlassian app and navigate to Product Automation.
2. Select the Studio flows tab from the automation list.
3. Review the list of available flows..

Get a more consistent work item view with similar requests panel

The Similar requests panel in the Jira Service Management work item view now uses a collapsible section design. This update aligns the panel with other sections like Description and Activity, providing agents with a more cohesive and predictable experience when managing requests.

To use the similar requests panel:

1. Open any issue in your service project.
2. Locate the Similar requests panel in the work item view.
3. Select the header to expand or collapse the section as needed.

Automate status page updates in Jira Service Management

Save time and reduce cognitive load during incidents by automating your external communications. Jira Service Management now includes a native automation action that creates and updates status page incidents directly from your incident workflow. This ensures your stakeholders stay informed in real-time without requiring manual context-switching from responders.

To get started with this change:

1. Go to Space settings, then Automation.
2. Create a new rule or edit an existing one.
3. Select the Send update to Statuspage action.
4. Choose your target status page and configure the title, message, and status fields.

Get an improved add status experience with the workflow editor

We've refreshed the add status experience in the workflow editor to make creating and choosing statuses clearer. We updated the wording throughout the dialog, and moved the create option into a fixed footer so it's always visible while you scroll.

To get started with this change:

1. Edit a workflow.
2. Select Add status in the toolbar at the top.
3. Select an existing status to add or create a new one.

Design coherence improvements including clearer labelling and purposeful motion

We’re modernizing the experience across Atlassian apps with UI improvements that make moving between apps, features and pages feel seamless. These updates to labelling, motion and shapes help you and your team get work done in a familiar, predictable way.

These improvements are rolling out progressively across apps from July 2026, beginning with with the apps listed here. Open any of your Atlassian apps, such as Jira or Confluence, to get started.

Automation: New settings panel in the rule builder

We’ve moved several configuration options in the automation rule builder to a dedicated settings panel. This change helps you manage your automation rules more effectively..

To get started with this change:

1. Open an existing automation rule or create a new one.
2. Select the More menu (represented by three dots) in the rule builder.
3. Select Settings to open the new panel and manage your rule configuration.

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.

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.

A better way to manage threaded comments in Jira

This update introduces the ability to show and hide threaded comments in Jira. This makes it easier to focus on the most relevant conversations, and reduces visual clutter when working with long comment threads.

To try out the new threaded comment show/hide feature:

1. Open any work item in Jira that contains threaded comments.
2. Select Hide replies to collapse replies within that thread. Select Show more replies to expand them again.

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.

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.

Connecting remote Cloud or Data Center delivery items to your Jira Product Discovery spaces

You can now connect Jira Product Discovery ideas with delivery items on remote Cloud or Data Center instances linked to your Jira Product Discovery site. After setup, a new Site field appears, letting you choose whether to create or link a delivery item locally or remotely. This integration keeps delivery progress in sync across your Cloud sites and Data Center instances, so you no longer need to update items manually on each platform. You’ll always see up-to-date insights about delivery progress from all linked items.

This integration requires Jira Data Center version 10.3 or higher, a free Marketplace app, and a Jira Product Discovery Premium plan. There are no additional requirements for connecting to a remote Cloud instance.

Check out the app on Atlassian Marketplace and explore the procedure how to setup the integration

Jira ‘projects’ will soon be renamed ‘spaces’

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.

As part of these efforts, the term project will soon be replaced with space across all Jira Cloud products, including Jira Service Management and Jira Product Discovery.

• Read more about these changes on the Atlassian Community

This change builds on previous terminology updates, like the transition to 'work' in Jira.

Standardize views across spaces with global views

Jira admins can now create and manage global views to standardize configurations across multiple Jira Product Discovery spaces. This helps teams enforce processes at scale and ensures a consistent experience by providing pre-configured views that can be automatically added to new spaces.

To get started with this change:

1. Go to Settings (the cog icon) in the top navigation bar.
2. Under Jira admin settings, select Jira apps, then choose Jira Product Discovery from the sidebar.
3. Select Global views to view the list of available views.
4. Select Create global view to create a new configuration or choose an existing view to edit its details.
5. Select Associate to add the view to specific spaces or select the checkbox to automatically add it to all future spaces.
6. Select Update globally to push your changes to all associated spaces.

Alternatively, you can copy an existing space view into a global view. To do so:

1. Open a Jira Product Discovery space.
2. Select More actions (..) next to a view in the sidebar.
3. Select Save as global view.

Managing idea watchers in Jira Product Discovery

Users with the default Administrator and Creator roles can now add and remove watchers for ideas in Jira Product Discovery. This helps you control who receives notifications about idea updates.

To manage watchers:

1. Go to your Jira Product Discovery space.
2. Open the needed idea.
3. At the top of the right panel, select Watch options.
4. Under Watching this work item, select the cross icon next to the user's name to remove that user.
5. Select Add watchers, then enter the user’s name to add that user to the watching list.

Browse view examples and learn how to implement them in Jira Product Discovery

You can now discover the view examples directly within your Jira Product Discovery space. These examples cover various use cases such as scoring and prioritizing ideas, creating quarterly roadmaps, and tracking Jira delivery progress. Browse and preview these examples to quickly identify approaches that fit your workflow.

To get the view example:

• Go to your Jira Product Discovery.
• Next to the space name, select +.
• Under Explore examples, select any view from the list to open its image.
• Select Learn more to open a how-to guide or Explore in sample space to create a dedicated space with pre-built views.

Activate apps faster from the template picker

App admins of Atlassian organizations that have only Jira apps can now activate Jira Service Management and Jira Product Discovery directly from the template picker. This simplifies the setup by combining app activation and project creation into a single step, helping you start using new features faster.

To view this change:

1. Open the Jira template picker.
2. Select a Jira Service Management or Jira Product Discovery template.
3. Review the template preview and app overview on the new setup page.
4. Select the checkbox to accept the product terms.
5. Select Try this template to activate the app and create your project.

View connections directly on the timeline

Visualize relationships between ideas in-context by displaying connections directly within timeline views. Expand an idea card to view connected ideas as timeline bars, and understand how child initiatives or dependencies align with parent timelines. This update makes timing relationships visible during roadmap conversations without needing to navigate away from the view.

To get started with this change:

1. Open a Timeline view in your Jira Product Discovery space. To view this change, you’ll need to be on a Premium plan.
2. Select the Fields menu and ensure at least one connection field is added to the view.
3. Select the Display menu and enable the Connections cards toggle.
4. Select the chevron on an idea card to expand it and view its connections.
5. To quickly create a connection, drag an idea from the Add section in the right sidebar onto a parent idea.

Visualize multi-level hierarchies with the new Tree view

Jira Product Discovery Premium now includes a Tree view to help you organize ideas into multi-level custom hierarchies. This view type allows you to better understand the relationships between different items and manage complex product roadmaps with ease, including roadmap planning and cross-space idea linking through connection fields.

1. Open your space in Jira Product Discovery.
2. Select + Create a view from the sidebar.
3. Choose Tree view from the list of available view types.
4. Configure your hierarchy by selecting work types (like Opportunities or Solutions) or fields (like Goals or Projects) for each level.

Publish your roadmap view

Share your product vision more effectively by publishing your roadmap in Jira Product Discovery. This update allows you to create a read-only version of your roadmap that you can share with stakeholders, ensuring everyone stays aligned on the latest plans and priorities without needing access to the app.

1. Open your space in Jira Product Discovery.
2. Select the Roadmap view from the sidebar.
3. Select Publish to create a shareable link for your roadmap.

Data security policies in Jira Product Discovery: Control over exports, downloads, and public links

Jira Product Discovery now supports Atlassian Guard data security policies, giving organization admins more control over how project data is shared and accessed. This update helps ensure your organization remains compliant by allowing admins to restrict data exports, attachment downloads, and the creation of public links for your discovery projects. Share discovery project views

To get started with this change

1. Go to Atlassian Administration, then select Security.
2. Select Data protection, then Data security policy.
3. Create or edit a policy to include your discovery projects in the policy scope.
4. Choose the actions you want to restrict, such as Export data, Attachment download, or Public links.

See more delivery details without leaving Jira Product Discovery

The Delivery tab in Jira Product Discovery now lets you choose which fields to display for linked delivery work items. Add fields such as assignee, sprint, fix versions, due date, story points right alongside the default summary and status columns. Linked items coming from Jira Data Center will not have team field available due to technical limitations. You can also resize columns to fit your workflow. Layout settings are saved per space so your whole team benefits. Learn more about linking ideas to Jira work items.

1. Open any idea in Jira Product Discovery and go to the Delivery tab.
2. Select the column More actions menu (⋮) to open the field picker.
3. Select the fields you want to see (for example, assignee, sprint, fix versions, due date, story points, or time tracking).
4. Drag column edges to resize them to your preferred width.
5. Your configuration is automatically saved for the space – all space members will see the same layout.

New avatars for idea types

Jira Product Discovery now features a new set of avatars for idea types. This update provides a fresh look for your ideas and ensures a more consistent visual experience across the app.

To see or edit the new icons, go to your Jira Product Discovery space and select Space settings, then Types and workflows.

Invite users directly from views

Project admins can now invite new users to Jira Product Discovery without leaving their current view. This change makes it easier to add collaborators and stakeholders to your project as you work, removing the need to navigate away to project settings or sharing menus.

To get started with this change:

1. Open any view in your Jira Product Discovery project.
2. Locate the visitors stack in the view header.
3. Select Invite next to the visitors stack.
4. Enter the details of the users you want to add in the Invite to space dialog.

New covers for the boards view