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

Automate your response when sensitive data is detected

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

You can now harness the power of Confluence automations to streamline your workflow when sensitive data is detected. Build your own rule using the new content scanning alert trigger, or try one of the templates to get you started.

Not sure how automations would help your workflow? Here’s some ideas:

• Classify the page that contains sensitive data.
• Restrict the page and add a comment or send an email to the actor to explain your company's policy on sensitive data.
• Create a Jira ticket to track the next steps for cleaning up the data.

You can configure the trigger to perform an action when any content scanning alert is generated, or just for specific alerts, such as API keys or credit card numbers. Thanks to the huge number of actions and conditions available in Confluence automation, the possibilities are endless.

How does automation work with Guard Detect?

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

1. In Confluence, go to Automations.
2. Select the Templates tab.
3. Select the Respond to security alerts category
4. Select a template and follow the prompts to configure it.

You’ll also see an option to add an automation rule in your next content scanning alert.

We suggest you create a rule in a test space first. Once you’re happy with the rule, you can create a global rule. If you have multiple Confluence instances, you’ll need to configure the rule in each instance.

Content scanning alerts are available with Atlassian Guard Premium. Automation is available with a Confluence Premium or Enterprise plan.

Filter the user list with added roles

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

The roles we’re introducing include:

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

To filter the user list by roles:

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

Brand your Jira products with a custom domain

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

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

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

To create a custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.

Enforce single sign-on for external users from your identity provider

You can now start using single sign-on to verify the identity of your external users. You'll be able to configure all user security from one place  – your identity provider.  When you connect your identity provider and set up SAML single sign-on (SSO) , you can enforce SSO in your external user policy.

SSO counts towards Atlassian Guard Standard bill
When you enable SSO in an external policy, we bill you for the external users in the policy. When you select one-time password or none as the authorization method, we don’t bill you for the external users in the policy.

Here’s a summary of what is and what is not billable for Atlassian Guard Standard
External user counts as billable
External user is in a billable external user policy and has product access to Jira, Jira Service Management, and Confluence.

External user doesn’t count as billable
External user is in a billable external user policy and has product access to Enterprise versions of Jira, Jira Service Management, Confluence, and Trello. And also for Statuspage: Startup, Business, and Enterprise

User has no product access to Jira or Confluence
External user is in a non-billable or test policy

Understand external user security

Before you begin:
Subscribe to Atlassian Guard Standard from your organization. Understand Atlassian Guard
Make sure you're an admin for an Atlassian organization.
Add an identity provider directory to your organization. How to add an identity provider
Configure SAML single sign-on with an identity provider Configure SAML single sign-on with an identity provider

To enforce single sign-on:

1. Log in to admin.atlassian.com > Security > External users.
2. Select the External user policy.
3. Select Single sign-on.
4. Select the Identity provider you use to manage single sign-on.
5. Select Update.

Create custom domains for your Jira products

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

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

To create a custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.

Data residency for Marketplace apps

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

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

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

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

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

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

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

To access this feature:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Copy product data.
3. Select Create copy plan.
4. On the How it works page, select Next.
5. Select your source and destination.
6. Select the spaces you want to copy.
7. On the Copy users and groups page, select Copy users and groups related to the selected spaces from the Users and groups section.

We’re replacing Jira Software with Jira in CSV exports

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

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

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

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

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

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

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

More about what we copy to sandboxes

Atlassian Access is now Atlassian Guard

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

Explore the future of Atlassian Guard

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.

Copy Jira data from one instance to another in Atlassian Administration

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

To copy Jira data:

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

Enhanced audit log filtering with new product filter

We're excited to announce an enhancement to our audit logs filtering capabilities! With the introduction of the new product filter, navigating through audit logs has never been easier or more efficient.

Save time and quickly locate specific audit logs by filtering through products. Combine the new product filter with existing filters for a comprehensive and intuitive search experience.

To start utilizing the new product filter, simply select it from the filter options, choose your desired product(s), and apply any additional filters as needed.

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.

Get the products your team has requested, faster

You can now review and approve new product requests from your users and add them to your organization, all from one place in admin.atlassian.com.

This is available for Confluence, Jira, Jira Service Management. Coming soon to Bitbucket.

You’ll still have the option to deny product requests or mark them as under review.

How to review product requests

To approve product requests:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security then Product requests.
3. Find the product request, and select Review request.
4. From the product request, select Approve.
5. Read the information and select Next to continue.
6. Choose a name for the new site.
7. Select Accept and add product to finish. We’ll email the requestor to let them know you approved their request.

It can take a few minutes to create your new site and product. If you don’t see the new product immediately, check Products after a few minutes.

Once you can see the new site and product, invite the requestor and any other team members that need access.

See what’s happening across your organization with your new overview

Get an enhanced idea of what’s going on across your organization with our new overview page at admin.atlassian.com. Quickly find your most important tasks, monitor what’s happening with insights, and explore new features.

Prevent your team from using new Bitbucket workspaces without your approval

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

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

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

More about product requests

To manage product requests for Bitbucket:

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

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

Audit log feedback collector

Exciting news! Audit Logs feedback just got easier!

You can now share your thoughts directly within the feature itself. We're dedicated to making Audit Logs work best for you, so tell us what you think. Head over to the new feedback collector in Audit Logs and let your voice be heard.

To give feedback using the feedback collector:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Audit log
3. Select Give feedback or suggestions
4. Tell us what's on your mind

Rovo customer admins can now add bookmarks

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

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

How to add or edit Rovo Search bookmarks

Adding admin controls for the "Hide unused fields" feature in Jira

We're responding to requests from admins who have requested to control the Hide unused fields feature in Jira. So, we've added the ability to globally switch the feature on or off.

To manage features on your site:

1. Go to Settings > System.
2. Select Edit Settings.
3. Scroll to Options and choose the settings you’d like to turn on or off
4. Select Update to save your changes.

A new home for help center customization features

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

Updates to service project templates

We've made some changes to service management templates when creating a new service project. Only new templates are affected by this change.

The IT service management template no longer includes problem management, change management, and advanced incident management features. These features are now found in the advanced IT service management template.

These changes are reflective of our updates to what's included in Jira Service Management's Standard and Premium plans. Read more about updates to Jira Service Management's pricing and packaging.

Brand your Jira products with a custom domain

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

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

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

To create a custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.

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

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

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

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

Streamlining general and blank project templates in Jira Service Management

We’re simplifying our Jira Service Management project templates and no longer splitting out our general and blank templates by IT and business team types. Now you’ll see just one general service management template and one blank template to cater to all needs - no matter the team type.

These project templates will replace the previous general service management for IT teams and general service management for business teams templates, and the blank project for IT teams and blank project for business teams.

Use the general service management template if you wish to get up and running with basic pre-configured settings to start managing incoming service requests, whilst blank projects let you fully customize how you manage incoming service requests.

Find out more about projects templates in Jira Service Management

Improved search using summary and description fields

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

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

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

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

New ways to edit card covers

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

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

Assets object list counter updated to show a max of 1000 (until clicked)

As part of our ongoing work to speed up the performance and improve the reliability of Assets in Jira Service Management, we're making a few minor UI changes.

This change involves that little counter at the bottom of the object list - it's getting updated to show a maximum count of 1000 objects, more than that and it'll show 1000+. And if you ever want to see how many more than 1000 that is, then simply select the 1000+ and it'll update to show the full object count. Simple huh? Happy Assets-ing!

Surface multiple software releases on a business calendar

Jira Premium users can now select up to 5 software projects to show on their business teams' calendars. Surfacing these release dates will give your business teams a clearer picture of their software team’s progress.

To get started:

1. Select a business project.
2. From the Calendar view, select …More.
3. Under Software release dates, select the projects you’d like to show.

Read more about showing software release dates in business team calendars

We're adding an upgrade button for Free customers

In the top right of the navigation, you might see a new button that will help you upgrade to a new plan when you get close to the user limit.

This button will help you understand how many users you have, what you get when you upgrade, and how to upgrade.

Get notified when your issues transition to another status

In team-managed projects, users can now receive a separate email when an issue transitions to a different status.

Previously, users in team-managed projects received the same email regardless of whether an issue was edited or transitioned to another status.

Project admins can now enable a separate email to notify their team when an issue is transitioned. This provides more granular control about email notifications and reduces clutter for users who are only interested in issue transitions.

To enable email notifications to users when an issue is transitioned:

1. From your project’s sidebar, select Project settings and then Notifications.
2. Select Add notification.
3. Using the dropdown, search for and select the issue event An issue is updated by a workflow transition (generic event).
4. Select the users and roles that will receive this notification.
5. Select Add.

More about customizing notifications in team-managed projects

Discover Confluence templates within your Jira issue

If you’re using Jira and have recently added or been given access to Confluence, you'll now see templates in certain issues. The templates will be for relevant types of documents to your issues. For example:

Bug issue type = Known errors Confluence template
Story issue type = Product requirement Confluence template
Epic issue type = Project plan issue type

If you select one of these templates, you'll be able to create the page without leaving Jira. It will then automatically be linked to your issue. After that, you won’t see the templates in any Jira issue.

These templates will appear for up to 14 days after Confluence is first added to your site, after which they'll disappear.

You can remove the templates from your Jira issues at any point using the more actions menu on the placeholder itself.

Quickly view images directly from your board issue cards

By adding an image attachment to an issue, you can show or hide images directly from your board in a company-managed software project.

To add or change an issue’s cover image:

1. Navigate to your board view.
2. Hover over an issue.
3. Select ••• (more) on the issue.
4. Select Edit cover image and choose from the options.

Forms now support cascading fields

There may be times when you want to surface only specific values to customers that are dependent on another choice they've made. These could be on forms that need to capture a customer’s address, for example. Instead of seeing all possible cities or states, you can make it easier for customers by letting them narrow down their options by selecting a country first.

This is possible with cascading fields. This new field type lets you create conditional fields with two lists of values: a parent list of values and a child list of values that are dependent on what is selected in the parent list.

Read more about using forms

New Jira instances are now domain-enabled

New Jira instances will be automatically domain-enabled from now on, meaning anyone with your organization's email domain (the one you used to sign up) will have access to projects that you send them links to. It'll save you time – you won't need to grant them access, after you've invited them. (Excludes existing Jira instances.) Find out how to disable this feature in your new Jira instance.

Create a board more easily for your company-managed software project

For those who are on our Early Access Program, we've streamlined the board creation experience. You'll still be able to create a board for your company-managed software projects directly from the sidebar navigation. Boards can also be starred, allowing you to easily navigate to the areas where you most often work.

Note: This is only for company-managed software projects and for customers who have been selected to participate in the Early Access Program.

More control over your board and backlog view

We're offering more customization options when viewing the board and backlog. Quickly show or hide any field that can be displayed on a card from the refreshed View settings panel. This includes fields such as issue type, key, epic, assignee, status, priority, and more.

Find the View settings button in the top right of your board and backlog to switch on what you need and switch off what you don’t.

Changes to the copy for Confluence listing in App Switcher

The app switcher in your Atlassian products is used to switch between different apps and products.

If you have Confluence, you will see it listed in the app switcher with a short sentence about what it is and what you can use it for. This sentence disappears after your first 15 days of having Confluence.

This sentence has been updated. It will now read: Confluence. Document collaboration.

Add and delete transition rules in the new workflow editor

As we continue to improve workflows in Jira, we're working to add important features from the old workflow designer to the new workflow editor. In this release we've made approval-related transition rules visible in the sidebar when you select a transition, and added the ability to add or delete those rules as needed.

Edit your Jira summary straight from Smart Link list view

This update to Smart Link list view allows you to edit the Jira summary without the need to open the issue.

While viewing Jira issues in Smart Link list view, select the summary from one of the items. Once the cursor appears, you can edit the summary straight from the cell.

Removal of SEN from UPM Manage apps

The SEN field has now been removed from the Manage apps section of UPM. To identify an entitlement, you'll have to use the new cloud identifier, which is the Entitlement number.

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.

Simplify your marketing work intake with a form template

With a ready-to-go template, you can quickly request information from your stakeholders for marketing campaigns, content creation, event planning, social media posts, graphic design, or email marketing.

To get started:

1. Select Forms from the project view navigation.
2. Select Templates to open the templates drawer on the right.

Learn more about creating forms

Admins can now delete previous project keys

We’re giving admins the ability to delete previous project keys so they can be used for new projects.

Whenever you change your project key, we automatically save your previous project keys. This ensures any links, filters, and queries using your previous key continue working.

Admins can now delete a previous project key from a project so it can be used for a new project.

To delete a previous project key:

1. Select Project settings, then Details.
2. In the Previous project keys field, delete the relevant project key.
3. Select Save.

We recommend letting users know before you delete your previous project key so that they can update any links, filters ,or queries using the previous project key.

More about project keys

Custom fields available in the automation smart values panel

We're adding a new feature to the smart values panel in Jira and Confluence automation. The panel will now have an additional filter called Custom fields, which will contain up to 50 custom issue fields from the current instance you have access to. You can search and copy these custom fields to use them while creating rules in the rulebuilder. Custom fields can be filtered by either the smart value or the untranslated name using text input. We will also display if these fields can be used globally or are bound to a single project.

To start using this feature:

1. Open the automation rulebuilder.
2. Select a trigger for your rule.
3. Add an action that has smart value text fields, such as the Log action, Send web request or Create issue action.
4. Select the {} button to open the smart values panel.
5. Select the Custom fields tab to browse available custom issue fields.
6. You can now copy and use these custom fields in your rule.

Learn more about using smart values in Atlassian automation

Smart Links available in more fields

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

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

New filtering options in your board

In business projects, we're adding the ability to filter by parent issues in your board. This will make it easier and simpler to filter by all associated child issues.

From the board, select Filter, then scroll to find and select from your Parent filter options.

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.

Customize duration for waiting for a response while running the AWS SSM document and resume rule in case of no response

When running the AWS SSM document, you can configure the action to wait for a response for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if AWS SSM doesn't return a response within the specified time.

Customize duration for waiting for a response while running a query in New Relic and resume rule in case of no response

When running a query in New Relic, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if New Relic doesn't return a response within the specified time.

Customize duration for waiting for a response while launching a job template in Ansible and resume rule in case of no response

When launching a job template in Ansible, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Ansible doesn't return a response within the specified time.

Customize duration for waiting for a response while starting a runbook in Azure and resume rule in case of no response

When starting a runbook in Azure, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Azure doesn't return a response within the specified time.

Customize duration for waiting for a response in Virtual Machine in Azure and resume rule in case of no response

When restarting Virtual Machine in Azure, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Virtual Machine in Azure doesn't return a response within the specified time.

The requests beta feature is leaving soon

We’re removing the Requests beta feature on October 4, 2024. This feature was intended to make it easy to view your Jira Service Management requests from your Jira Software project, but we’ve found its performance wasn’t quite up to scratch.

If you’ve participated in the Requests beta in your software project and have been using it, all your request data will still be available in Jira Service Management. You can still work with requests from your software request by implementing one of the alternative options we’ve provided on Atlassian Community.

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

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

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

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

Nest media and codeblocks in quotes

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

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

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

New and updated virtual agent Channel management

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

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

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

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

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

The openCreateIssueDialog function now opens the new Jira issue create experience

If you use the openCreateIssueDialog function to create issues through plugins and Marketplace apps, you’ll now see the new Jira issue create experience. This provides a faster, modernized way of creating issues.

More about the openCreateIssueDialog function

Automation: Filter audit log by actions

In the Automation audit log, you can now show or hide entries based on actions, making it easier to find specific rule runs. For example, you could choose to see all rule runs where the "Send email" action was used.

1. Navigate to automation:
   • For Confluence automation, go to Confluence settings > Automation
   • For Jira automation, go to Jira settings > System > Global automation
2. Select Audit log.
3. Select Actions and choose which actions you want to filter by.

Say hello to smart replies in Jira issues

Adding comments to issues has just become faster and easier. With the touch of a button, you can add a pre-populated comment to an issue and instantly save it, or use it as a starting point to type more information before saving.

NOTE: This feature is currently rolling out. If you'd like access to it now, contact Atlassian Support.

What’s the benefit of smart replies? Jira’s real superpower lies in collaboration. By encouraging your team to respond to work and comment on issues faster and more often, smart replies can help your team embrace Jira’s unlimited power of accelerated collaboration.

If you don’t want to use a smart reply, simply start typing in the issue’s comment box, and the smart replies will disappear.

To disable the feature, go to Settings > Personal Jira settings > General, and disable the smart replies toggle within the Jira labs section. (This only affects you.) Or to remove the feature entirely (affecting everyone in your Jira instance), contact Atlassian Support.

Read more about smart replies.

Search for boards by project

Filter boards by project to quickly find the exact board you’re looking for. To try it out, go to Your work > Boards > View all boards. From there, you can search for boards by both keywords and project.

Archive your Jira issues

Instead of deleting issues, Premium and Enterprise users can now archive issues from your project to reduce clutter.

If you archive an issue, it will only appear in Archived issues and can no longer be edited. You can restore an archived issue if you need it in the future.

To help your team start archiving issues straightaway, we’ve automatically allowed users, groups and roles to archive issues if they already have the permission to delete issues.

More about archiving issues

To archive an issue:

1. Make sure you're viewing an issue either in the side bar or in full screen.
2. Select More actions.
3. Select Archive and confirm your changes.

Changes to when the parent field can be edited

In Jira, administrators can configure screens for an issue operation (create, view, and edit).

If a screen has been associated with the “Edit Issue” operation, only fields added to this screen should be editable. However, the parent field previously ignored the edit issue screen. If the parent field was not on the edit issue screen, it was still considered editable. We are changing this behaviour to make the parent field behave like other fields, and ensure it is not editable if the parent field is not on the edit issue screen.

To avoid problems arising from the change in behaviour, the parent field will be added to all existing screens configured for the edit issue operation.

When this change has rolled out, Jira administrators can remove the parent field from the edit issue operation screen if they wish to restrict the editing of the parent field.

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.

Use automation rules to add text to new pages

The Publish new page automation component now supports adding text to the body of the page. We're adding an additional field that allows you to input content that will be added to the page when it's created.

Add the Create page action to your automation rule and input your custom text in the Page content field.

Copy URL button available in the automation audit log

We've added a new button to Jira and Confluence automation that allows you to copy the URL of the audit log to your clipboard. This button will help you easily copy and share your audit log's URL.

To start using this feature:

1. Open the audit log from either Jira or Confluence automation.
2. Select Copy link in the audit log to copy the URL.
3. The URL is now copied to your clipboard and ready to use.

Learn more about using the audit log in Atlassian automation

View and filter virtual service agent conversations by channel

On the Conversations page in the virtual service agent, you can now see conversations from all of your connected channels (instead of just Slack).

We've added a Channel column so you can see the source channel at a glance, as well as a filter to narrow down conversations by channel.

Read more about using conversation data to improve your virtual service agent's performance

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.

New business project templates with approvals set up

We've created and added four new templates with approvals already set up so you can get started as quickly as possible.

If you're working on a project that requires approvals, consider using one of the following templates to get you started:

• Manage approvals for your business project
• Manage approvals for documents
• Get approval for your budget
• Manage approvals for your campaign

Using these templates will help you save time in setting up and customizing your own approvals process in your project.

Save automation rules in a disabled state

We're introducing a new feature that allows you to save automation rules in a disabled state, which means they are draft rules that you can come back to edit and turn on later. Previously, rules couldn't be saved as drafts and had to be turned on immediately after creation. This new feature provides more freedom for users and allows you to more effectively edit and refine your rules before turning them on.

To get started with this change:

1. Open either Jira or Confluence automation.
2. Select Create rule and create your desired rule in the rulebuilder.
3. Click on the dropdown arrow next to the Turn on rule button.
4. Select Save rule without enabling.
5. You'll now be able to see the draft rule under your Rules list in automation. It will appear as 'Disabled'.
6. When you're ready to turn on the rule, move the Enabled toggle to the right so a tick appears.
7. Your rule is now turned on and ready to use.

Move data between sites with cloud-to-cloud migration

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

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

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

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

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

To connect pending Bitbucket workspaces on the Code page:

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

To connect pending Bitbucket workspaces using the development dialog:

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

Read more about integrating Bitbucket with Jira

Move a mighty amount of issues from a completed sprint

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

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

Colourful categories

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

Track and triage incidents affecting your services in Jira

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

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

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

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

To get started with the incidents feature:

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

To turn it on manually:

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

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

Hide unused fields when creating issues

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

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

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

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

Get suggestions for child issues from AI

Use Atlassian Intelligence to generate a list of suggested child issues, based on the details of the parent issue.

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

To see a list of AI-generated suggestions:

1. Open the parent issue.
2. Select Add a child issue under the issue summary. If you are in a company-managed project and want to create a subtask, select Create subtask.
3. Select Suggest issues.

We’ll then create a list of suggested child issues which you can accept, edit, or decline.

Template bundles in the project create page

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

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

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

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

Another way to create a bundle is to:

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

Structuring your Asana and monday project data

We added more options to structure your Asana and monday data when importing into a new Jira business project.

Udpated:
• Sections (Asana) and Groups (monday) can now be imported as Epics, Issue statuses, or Category fields.

Existing:
• Tasks and Items will be imported as Issues.
• Subtasks and Subitems will be imported as Subtasks.

Learn more about importing data from Asana or monday

Use Atlassian Intelligence to define words in the issue description

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

To use Atlassian Intelligence to define words:

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

Definitions are only available in the description in view mode.

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

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

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

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

Improved editing experience for Queues

We've made improvements to the "Basic" editing experience for Queues in Jira Service Management. The update includes improved dropdown fields and the ability to select multiple options for ordering your queue.

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

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

Create Confluence whiteboards directly from your Jira backlog

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

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

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

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

You can remove this button anytime by turning off all product recommendations at admin.atlassian.com. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Manage email notifications based on your role

Due to popular demand, we’re bringing back the ability to manage emails in Jira based on whether you’re a reporter or assignee for an issue.

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

To manage email notifications based on your role:

1. Select Settings > Personal settings.
2. Select Projects and issues.
3. Turn on the toggle to the right of Send emails for issue activity.
4. Select when you’d like to receive emails for issue activity.

Site optimizer now archives projects

You've heard of the Site optimizer (if you haven't, here's some reading you'll love); now we've made it better. It now allows you to clean out old projects as well as issues, project role permissions, and custom fields.

When looking at projects that can be deleted, you can select projects to clear out from your site based on those that:

• have no issues or
• haven't been updated in a certain amount of time

From here, you can choose to either archive them or send them to the trash.

Accessibility improvements in the project timeline

Over the next few weeks, we'll be shipping a few accessibility improvements when viewing the project timeline. These changes make it easier for those using assistive technologies (such as screen readers) to track their work using the timeline view.

Board and backlog insights now available to all Jira users

We’ve updated the Insights feature on the board and the backlog for company-managed projects in Jira. Now, all users can view insights, regardless of what permissions they have.

With real-time data, you can use insights to review your team’s progress, identify issues that need attention, and plan your sprints with confidence. Adjust, maintain, or refocus your priorities to keep the team on track.

Read more about insights in Jira Cloud

To view your insights:

1. Find your team's Jira software project.
2. Select the board or backlog.
3. Select Insights.

Bulk duplicate and delete components in the automation rulebuilder

We're introducing a new feature that allows you to select multiple components at once in the automation rulebuilder and either duplicate or delete them. This change affects both Jira and Confluence, and should help to improve efficiency in the rulebuilder, as you'll no longer need to select each component one at a time to edit them.

To select and edit multiple components at once:

1. Hold down the Ctrl / Command key and click the left button on your mouse or touchpad.
2. Select the number of components you want to duplicate or delete.
3. Once the components are selected, you can use the new menu to duplicate or delete them.

Jira Plans: Change plan owner

You can now change who is listed as the owner of a plan in Jira, so you'll always know who's in the driver's seat.

Connect issues to goals in your Jira list

Use the Goals field in Jira to connect your team’s work to higher-level business objectives. Goals help your team understand how their efforts drive impact and help leaders manage dependencies and mitigate risk. All issue types can now be linked to a goal in software projects, business projects, and plans.

Enable the Goals field to show as a column in your list. Once enabled, you can create goals, link issues to the goals they contribute to, and filter issues in your list based on goals.

How to link and unlink goals to issues

New workflow editor: Trigger a webhook rule

Connect Jira to other tools with the Trigger a webhook rule. By adding it to a transition in the new workflow editor, you’ll be able to send a webhook and notify an external system when an issue moves through that transition. This allows your other tools to act on this updated information accordingly.

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.

New validation for fields in the workflow editor

We've revamped how field validation works when building workflows for company-managed projects, as well as introduced this feature to team-managed projects.

When building a project workflow, validators let you specify criteria for when an issue can move through a particular transition.

Go to Project settings > Workflow to get started, then follow these instructions to add validators depending on your project type:

• Add or edit rule to a team-managed project
• Add or edit a rule for a company-managed project

If you're already using validators for a company-managed project, don't worry, your existing rules still work and are fully compatible with the new experience.

Speed up your next Jira import with configuration files

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

To use a configuration file during an import:

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

Read about configuration files

Priorities page refreshed and more accessible

Adding priorities to work communicates urgency and brings focus to the most important tasks.

Use the refreshed Priorities page to add, delete, and re-order priorities. You can also add priority names and colors and upload icons.

To see the list of priorities on your Jira site, go to Jira settings, then issues, then priorities.

Plans in Jira - Change the duration of the program board

We're a few months into the Program board Open Beta, and we've gotten a lot of feedback about how to improve it. One of the most requested improvements was the ability to change the number of sprints shown on the board and the duration of them.

Guess what we're releasing today?

That's right: when you create a new Program board, you can now change:

• the duration of each column to between one and four weeks
• the total number of columns to show between four and 13

Using these, you can adjust the total duration of your board to be as little as seven weeks and as much as 16.

Haven't met the Program board yet? Allow me to introduce you.

Create issues directly in your calendar

With just a few clicks, you can create and schedule issues directly in your calendar.

Prior to this change, issues were scheduled by adding start and due dates or using the unscheduled work panel. Issues can still be scheduled in those ways, but this is now the quickest way to do it.

How to create, edit, and delete issues in your calendar

To create an issue in your calendar:

1. Select an empty space on the date you’d like the issue scheduled. The date selected will be the issue’s due date.
2. Enter a summary, select the issue type, then select Create.

To create an issue that spans multiple days:

1. Click and drag to select multiple days. The first and last dates selected will be the issue’s start and due date.
2. Enter a summary, select the issue type, then select Create.

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.

Company-managed projects: Fixed bug for attachments in private comments

We've fixed a bug where attachments in private comments were visible to all users. If your issue cards were configured to show images, these would show on the board and backlog too.

This is no longer the case — if you can see attachments in private comments or images on the board and backlog, rest assured that you're the intended audience.

Custom Compass component types support in Jira

We're introducing a new capability in Compass that allows product admins to create component types based on the terminology their teams use to categorize them. Custom type names will be supported in Jira, but will use the OTHER icon.

In Compass, product admins can create up to 14 component types, but anyone on their Compass plan can use them. This customization helps software teams better group components at a high level across their distributed architecture.

Connect issues to higher-level goals in the issue view

You can now align your team’s work to higher-level goals directly in the issue view. Goals help your team understand how their efforts drive impact and help leaders manage dependencies and mitigate risk.

If you linked an issue to a goal before this change, the Goals field will be automatically enabled in the issue view. This change will replace the previous experience of connecting goals in the issue view.

If you haven’t linked an issue to a goal before, you’ll need to enable the Goals field for an issue type.

To enable the Goals field:

• Open an issue of the type you'd like to add the Goals field to.
• Select Configure at the bottom-right of the issue (near the created and updated dates).
• In the Fields panel, search for Goals.
• Drag the Goals field to the Context fields section.
• Select Save changes to finalize.

Use the virtual service agent in email (beta)

You can now activate the virtual service agent in email (beta) so that your customers can find the help they need. When your customers send requests to the email address connected to your project, the virtual service agent responds using Atlassian Intelligence answers.

Find out more about using virtual service agent in email

Updated project settings navigation in Jira Service Management

We've made some updates to the project settings navigation in Jira Service Management. The new navigation makes it easier to scan and find what you’re looking for, and aligns more closely with other Jira projects.

Related items are now in groups – considerably reducing the number of items displayed upon landing in project settings. These groups can be expanded and collapsed as required.

Labels have been updated for some items – giving a better indication of what to expect on pages.

Layout and patterns are now consistent across Jira – meaning you'll have a similar experience whether you’re using Jira or Jira Service Management.

Email requests settings page update

We've updated the code on the Email Requests page (accessed by selecting Settings, then Products). We've also added a new section for enabling DMARC protection on incoming emails.

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

Hide unused fields when creating issues

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

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

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

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

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

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

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

Find out more in our Community blog

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

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

To set up emoji rules in automation:

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

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

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

Use Atlassian Intelligence to define words in the issue description

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

To use Atlassian Intelligence to define words:

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

Definitions are only available in the description in view mode.

The new Parent field is coming to Request forms

As part of our ongoing work to introduce the Parent field, this change removes the Epic Link and Parent link fields from the Request type configuration in Jira Service Management, and replaces them with the unified Parent field.

As part of this migration, the new parent field will inherit values from either the Epic Link or Parent link fields:

• For base-level issue types (level 0 - such as Story issues), the Parent field will inherit whatever value is in the Epic link field. Only if that field is empty will it take the value from the Parent Link field.

• For epic-level issue types (level 1 - such as Epics), values in the Epic link field will be ignored in favor of what’s in the Parent Link field regardless of whether there's any values in the first field. This is because a Level 1 issue type can't have an issue at the same level as its parent.

Data limits for object schemas in Assets

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

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

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

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

Improved editing experience for Queues

We've made improvements to the "Basic" editing experience for Queues in Jira Service Management. The update includes improved dropdown fields and the ability to select multiple options for ordering your queue.

Approvals for the new workflow editor in company-managed projects

You can now use approvals in the new workflow editor in Jira Service Management! This was one of your most requested features from the old workflow designer, so we're excited that approvals are now supported in the new workflow editor. This means you no longer need to move back and forth between the workflow designer and editor to add approvals to your issues.

To add an approval step to your workflow, look for the 'Approvals' section in your workflow panel and select the add button (+) to start adding your approval.

Find out more about adding approvals to your workflows.

Attach a form directly from the request type configuration page

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

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

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

Read more about adding forms to request types

Choose your own date fields for the calendar view

The calendar view of issues is a great way for team members to plan, track, and prioritize their work and for team leads to see potential roadblocks before they cause delays. Read more about the calendar view.

By default, issues appear on the calendar based on the data in Jira’s default date fields - start date and Due date - but you can now select any date fields from your project, giving you more flexibility to work in the way that's best for your team.

For example, you might want to use Planned start and Planned end date fields to track when you plan to work on an issue, or your team might prefer issues to be shown on the calendar by the Actual Start and Actual End dates.

To change your date fields:

1. From your service project, go to Calendar.
2. Select Configure calendar from the more menu (•••).
3. Go to Date fields.
4. Select a field for the Start date and a field for the End date from the dropdowns. We recommend using two date-time fields, rather than date-only fields.
5. Select Save.

Not seeing your issues on the calendar? Head to the Request types page in Project settings and add your newly selected fields to your request types.

Learn how to select your own date fields for issues on the calendar

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.

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

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

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

Learn more about the GitHub for Jira app.

Make a view accessible to people outside your organization

This feature enables creators with an Atlassian account and the permission to make a published view visible to anyone on the Internet who has a link and not an Atlassian account. That means you can share the link to a published view in your social media feed, email, or anywhere else you may want to share it, and anyone can view it.

Find out more about publishing views

UI visual refresh and enhancements

We're changing a few things in the UI to improve your experience.

Jira Product Discovery Roadmaps improvement (Premium edition)

When visiting the Roadmap homepage, you can now visualize which projects are used in each Roadmap.

See the projects in your roadmap and filter them by projects

You can now see which projects are contained in each roadmap, and filter your roadmaps by projects.

In your project, click Roadmaps on the top nav bar to land on your roadmap.

Voting in Confluence whiteboards

Simplify collaborative decision-making with voting in whiteboards. Use it for brainstorming, retrospectives, and more with your team. Anyone on the whiteboard can start, manage, and conclude voting sessions.

View detailed results with the top-voted items and individual votes.

Prevent people from using public links in specific spaces

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

You can now use the public links rule to prevent people creating and accessing public links in particularly sensitive Confluence spaces. Previously, this was only available for policies that covered classification levels or entire Confluence instances. How the public links rule works

The public links rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

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

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

Automate your response when sensitive data is detected

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

You can now harness the power of Confluence automations to streamline your workflow when sensitive data is detected. Build your own rule using the new content scanning alert trigger, or try one of the templates to get you started.

Not sure how automations would help your workflow? Here’s some ideas:

• Classify the page that contains sensitive data.
• Restrict the page and add a comment or send an email to the actor to explain your company's policy on sensitive data.
• Create a Jira ticket to track the next steps for cleaning up the data.

You can configure the trigger to perform an action when any content scanning alert is generated, or just for specific alerts, such as API keys or credit card numbers. Thanks to the huge number of actions and conditions available in Confluence automation, the possibilities are endless.

How does automation work with Guard Detect?

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

1. In Confluence, go to Automations.
2. Select the Templates tab.
3. Select the Respond to security alerts category
4. Select a template and follow the prompts to configure it.

You’ll also see an option to add an automation rule in your next content scanning alert.

We suggest you create a rule in a test space first. Once you’re happy with the rule, you can create a global rule. If you have multiple Confluence instances, you’ll need to configure the rule in each instance.

Content scanning alerts are available with Atlassian Guard Premium. Automation is available with a Confluence Premium or Enterprise plan.

New analytics for company hub

We’re excited to roll out analytics for your Company Hub. Understand how your hub is performing and discover what content is most relevant to your users. See the total number of visits, unique visitors, clicks, and more! You can also filter your dates by a specific time frame to see which content has the most views, click-through rates, and unique visitors.

To access this feature,

1. Navigate to your Company Hub editor.
2. Select the more … icon on the top right corner of your page.
3. Under Company Hub settings, select Analytics.
4. Filter the data based on a specific date range to see specific analytics or content.

Save automation rules in a disabled state

We're introducing a new feature that allows you to save automation rules in a disabled state, which means they are draft rules that you can come back to edit and turn on later. Previously, rules couldn't be saved as drafts and had to be turned on immediately after creation. This new feature provides more freedom for users and allows you to more effectively edit and refine your rules before turning them on.

To get started with this change:

1. Open either Jira or Confluence automation.
2. Select Create rule and create your desired rule in the rulebuilder.
3. Click on the dropdown arrow next to the Turn on rule button.
4. Select Save rule without enabling.
5. You'll now be able to see the draft rule under your Rules list in automation. It will appear as 'Disabled'.
6. When you're ready to turn on the rule, move the Enabled toggle to the right so a tick appears.
7. Your rule is now turned on and ready to use.

Free user limit awareness

We're making it easier to know when your team is near or has reached the Free user limit.

A modal will appear when your team is near and reaches the Free plan user limit of 10 users. Plus, the button at the top right of your screen with change colors to let you know you're nearing the limit.

Automatically get a personal space

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

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

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

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

Learn more about personal spaces

Transfer of page ownership between users

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

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

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

Learn more about page ownership and how it can be transferred

Control what you see in your products

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

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

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

Premium and Enterprise: Customize a dynamic info hub for your entire company with Company Hub

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

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

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

Restore and reattach inline comments, even after deleting highlighted text

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

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

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

Configure and display labeled content with clarity and ease

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

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

Seamlessly migrate from Notion to Confluence with bulk importing

Our new bulk importer tool makes it easy for you to migrate your content from Notion to Confluence, ensuring a smooth transition and minimal disruption. With support for importing up to 40,000 pages, including attachments and page comments, site and organization admins can now move their workspaces with confidence. The tool also allows you to preserve user data and permission settings to boost familiar patterns within Confluence.

• Site and organization admins can import to 40,000 pages from Notion to Confluence, including attachments, page comments, @mentions, and author information.

• Preserve user data and permission settings for a more seamless transition.

• Supports importing entire workspaces or selected pages.

• A completion report email shows an overview of the import outcome, providing transparency and simplifying following up.

Select Import from other tools in the Spaces menu and follow the step-by-step guide to import your content from Notion.

Catch up quickly with page comments summary

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

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

Introducing content generation with richer context

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

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

Admins can now create automation rules for public links

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

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

Automatically build automation rules for public links

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

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

Automatically build automation rules to assign guest users to a space

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

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

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

Comment on whiteboards for further collaboration

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

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

New cross-product actions available in Confluence automation

We've added 3 new cross-product actions in Confluence automation: Create version, Comment on issue, and Delete issue. Previously, these actions were only available in Jira automation. However, with this update, you can now create versions in Jira and delete or comment on Jira issues via Confluence automation.

To use the Create version action:

1. In the Confluence automation rulebuilder, select any trigger.
2. Select Add action and then select Create Version in Jira.
3. Enter a valid name into the Version name field.
4. Open the More options section and then select a valid project.
5. Turn on your rule. You can check the audit log to verify a new version was created.

To use the Delete issue action or Comment on issue action:

1. In the Confluence automation rulebuilder, select any trigger.
2. Select Add a branch, then select Branch rule / related Jira issues.
3. Configure a connection to your selected site.
4. In the branch, select Add action.
5. Add the Delete issue or Comment on issue action. This action's connected site should automatically be the same as the branch's.
6. Turn on your rule. You can check the audit log to verify if the issue was deleted or commented on.

Join the conversation and give us feedback

Bulk change page status in Content manager

Enhance your content lifecycle management with the ability to bulk change the status of pages in Content manager. This feature supports key admin jobs-to-be-done, streamlining the verification process for spaces used as a source of truth.

• Bulk change the status of pages or page owner within the Content manager feature.

• Aids admins in efficiently managing content lifecycle loops, such as marking pages as verified or changing verified pages to needs verification.

To bulk change the status of pages:

1. Select Space settings in the left sidebar of your site, then Content manager.
2. Select the checkbox for each page that you want to update.
3. Select Change owner or Change status, then choose your new status or owner.

Create Confluence whiteboards directly from your Jira backlog

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

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

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

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

You can remove this button anytime by turning off all product recommendations at admin.atlassian.com. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Effortless content arrangement with drag-and-drop

This update introduces new drag-and-drop functionality for top-level elements in the Confluence editor, making it easier than ever to arrange your content. This feature enhances the user experience by allowing smooth content movement, reducing the need for cut-and-paste actions, and providing a more intuitive and modern editing experience.

What's new:

• Drag and drop for top-level elements: A new drag handle makes it easy to rearrange any top-level element on your page.
• Instant selection: Select any element with a single action on the drag handle for fast and convenient movement.
• Auto-scroll functionality: Move content above or below the fold with automatic scrolling, ensuring smooth navigation while rearranging elements.

Fixed column widths for tables

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

How to use:

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

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

Rename space key in Confluence Cloud

We’re adding the ability to change your space key. Renaming space keys can help with accurately representing a company to users and publicly as organization changes take place. It can also help to prevent conflicts during migrations for newly created spaces.

• Space admins can rename their space (for example, during acquisitions, organization restructuring, or if the department, username, or team name changes).

• The old space key will redirect to the new URL.

To rename your space key:

1. As a space admin, go to Space settings > Manage space > Space details.
2. Select Edit space details.
3. Enter your new name in the Space key text box.
4. Select Save.

Enhanced inline commenting

You can now comment directly on inline elements such as emojis, statuses, mentions, dates, and inline cards (Smart links). Users can now leave comments on these specific elements, streamlining the commenting process and making it more intuitive and efficient for providing feedback and collaborating on documents.

Folders in Confluence Cloud

We've added folders to Confluence to help you keep work organized with less hassle. Unlike parent pages, which you can think of as containers with built-in “Read Me” files, folders are simple containers, without extra information or context included.

Folders live alongside parent pages in Confluence, so you can choose which one to use based on your team's needs. For more information on how you can use folders to keep work organized in Confluence, see our documentation.

To create a folder:

1. Navigate to a Confluence space.
2. Hover over Content in the content tree, then select +.
3. Select Folder from the drop-down menu.
4. Give your folder a title, making sure you don’t include any PHI.

To nest a folder under another content item, hover over its title in the content tree, then select + and repeat steps 3-4 above.

Introducing a new UI and bulk actions to the Content manager

We're excited to introduce a new UI to the Content manager, along with new bulk change owner and status features for nested tables. These updates aim to improve your workflow efficiency and table management experience.

• • Bulk change owner and status for nested tables*: Now available in nested tables, these actions streamline your content management by allowing bulk updates, previously only possible in filtered, flat versions.

• • New UI*: Enjoy a more flexible table interface with options to resize, pin, and show/hide columns, enhancing your data visualization and management.

• • Improved load times*: Experience quicker load times for the table, ensuring a smoother and more efficient user experience.

These enhancements are designed to make managing your content more intuitive and efficient. Dive into the new features and optimize your workflow today!

To get started, go to Space settings, then select Content manager. Or, select Content manager from the space sidebar.

Blogs are moving

To help you keep your spaces clean and tidy, we're hiding blogs for new spaces and current spaces where blogs aren't being used.

For all other spaces, we're moving blogs into the content tree so they're close to the rest of your work. You can find them in their own section, below Content.

To turn blogs back on, or turn them off if you're no longer using them:

1. Navigate to the space, then select Space settings.
2. Under Manage space, select Features (only space administrators have this option).
3. Select the toggle next to Blogs to turn them on or off.

Add hyperlinks to whiteboards

Hyperlinks can now be added to whiteboards text.

Easily share links with your collaborators on a whiteboard through free text or text within an element. Hyperlinked text will appear blue.

More control over notifications

Page owners no longer receive notifications by default when someone interacts with their page. Instead, they can opt-in to notifications by choosing to Watch the page. This change reduces the noise of unnecessary communications (for example, when pages are no longer actively monitored or updated) — and improves the value of the notifications that do appear in the person's inbox and message feeds.

Read more about how to watch a page

Bulk duplicate and delete components in the automation rulebuilder

We're introducing a new feature that allows you to select multiple components at once in the automation rulebuilder and either duplicate or delete them. This change affects both Jira and Confluence, and should help to improve efficiency in the rulebuilder, as you'll no longer need to select each component one at a time to edit them.

To select and edit multiple components at once:

1. Hold down the Ctrl / Command key and click the left button on your mouse or touchpad.
2. Select the number of components you want to duplicate or delete.
3. Once the components are selected, you can use the new menu to duplicate or delete them.

Improved Jira issue creation from a page, featuring Atlassian Intelligence

We’ve improved the Create Jira issue menu option in Confluence pages.

When you select text, you can now create a single issue in the right-side panel. This gives you access to all Jira issue fields while staying in context of the page you’re viewing.

We’ve also added the ability to select text and ask Atlassian Intelligence (AI) to generate your issue for you. AI will use both the selected text and the surrounding content to generate a Jira issue’s summary, description, assignee, and other relevant fields.

Atlassian Intelligence is available and automatically activated for all products on Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

Editor AI: Improved command palette

We've redesigned the command palette for AI options in the editor. The palette height has been extended, and less-frequently used prompts have been organised into sub-menus.

• Palette organization: The editor AI palette options like Translate and Change are now grouped into submenus for better organization.
• Back button: The palette now supports a Back action, allowing you to navigate back within the command palette.
• Layout update: The general AI response-layout has been updated for a cleaner look.
• Keyboard shortcut for chat: A quick shortcut for the Open in chat action has been added for faster access.

Manage your Confluence spaces

Introducing a new feature for product admins to view and manage all their Confluence spaces with supportive metadata and actionable insights. This feature is available to customers on all Confluence plans.

Admins can now easily view, filter, and take actions on their spaces, such as archiving or deleting inactive spaces, copying permissions (for customers on Confluence Premium and Enterprise editions only), and more.

To get started with this change:

Admins can select Spaces in Confluence settings.

Custom fields available in the automation smart values panel

We're adding a new feature to the smart values panel in Jira and Confluence automation. The panel will now have an additional filter called Custom fields, which will contain up to 50 custom issue fields from the current instance you have access to. You can search and copy these custom fields to use them while creating rules in the rulebuilder. Custom fields can be filtered by either the smart value or the untranslated name using text input. We will also display if these fields can be used globally or are bound to a single project.

To start using this feature:

1. Open the automation rulebuilder.
2. Select a trigger for your rule.
3. Add an action that has smart value text fields, such as the Log action, Send web request or Create issue action.
4. Select the {} button to open the smart values panel.
5. Select the Custom fields tab to browse available custom issue fields.
6. You can now copy and use these custom fields in your rule.

Learn more about using smart values in Atlassian automation

Customizable page creation from Confluence databases

Utilize more flexible and customizable page creation configurations in the page link field of Confluence databases.

You can choose a fixed or dynamic page location. This means new pages can always be created in one place or dynamically created from wherever you're editing.

Additionally, where you could previously only choose one, you can now use both a page template and a database entry macro for newly created pages.

Simplify access troubleshooting

Admins can now easily audit user access across spaces from a consistent and convenient location. This will reduce the time and effort required to resolve access and permissions blockers. Admins can also generate an exportable CSV report to quickly identify which spaces a user or group has access to, ensuring that the right users have access to the right information.

Key changes:

• Improve visibility into user permissions to resolve access issues faster.
• Troubleshoot access issues from a central location.
• Generate a CSV report showing all spaces a user or group can access.

To access this feature, site admins can navigate to Confluence settings, then User access.

Manage and customize your company hub with greater ease

It's easier than ever to control and calibrate who has edit access to your company hub. You can now access Hub permissions directly from the More actions (...) menu while editing your hub page, to add or remove hub editors as needed.

We've also improved some Company Hub adjacent settings in Customize navigation and General configuration. This makes it more intuitive to customize your Confluence navigation bar to fit your company's branding or preferences.

Customize duration for waiting for a response while running the AWS SSM document and resume rule in case of no response

When running the AWS SSM document, you can configure the action to wait for a response for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if AWS SSM doesn't return a response within the specified time.

Customize duration for waiting for a response while running a query in New Relic and resume rule in case of no response

When running a query in New Relic, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if New Relic doesn't return a response within the specified time.

Customize duration for waiting for a response while launching a job template in Ansible and resume rule in case of no response

When launching a job template in Ansible, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Ansible doesn't return a response within the specified time.

Customize duration for waiting for a response while starting a runbook in Azure and resume rule in case of no response

When starting a runbook in Azure, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Azure doesn't return a response within the specified time.

Customize duration for waiting for a response in Virtual Machine in Azure and resume rule in case of no response

When restarting Virtual Machine in Azure, you can configure the action to wait for a duration of 1 to 15 minutes. Additionally, you can now set the rule to resume even if Virtual Machine in Azure doesn't return a response within the specified time.

We've simplified space creation

With just two kinds of pre-set spaces, each made to suit a specific purpose, creating a space is easier than ever before. Choose between Knowledge base and Collaboration, add a description to the overview, and dive into content creation faster than ever before with one of our suggested templates. Or, if you know you want something really specific, choose Custom to manually configure the features and settings for your space.

To read about these changes in more detail, check out the Community post.

To create a space:

1. Select Create from the Confluence navigation bar at the top of the screen.
2. Select Space from the dropdown menu.
3. Choose the option that best fits the purpose of the space you're creating.
4. Confirm your choice, making changes to the defaults as needed.

Mention users in automation actions

You can now mention users in your Automation for Confluence rules. The Add comment and Publish page actions now support mentioning users by their "accountId" and by smart values such as page.owner.accountId.

To mention a specific user:

• Visit their profile page and copy the characters at the end of the URL:
• https://hello.atlassian.net/wiki/people/_557057:1d4fd7f4-bbac-4466-82ee-aaabbbccc_

• Add [~accountId:<user's account ID>] to the action component.

To mention a user with a smart value:

• Replace the account ID with any smart value that includes the "accountId" field.

• For example: [~accountId:page.owner.accountId]

Editor: Nested drag and drop

We are introducing an enhancement to the drag and drop feature in the Confluence full-page editor, allowing you to nest content within certain elements. This update aims to reduce the reliance on cut and paste actions to improve the efficiency of your content creation.

• Single-click nesting: Drag and drop to nest content such as tables, code blocks, expands, panels, and layouts.
• Improved content management: The new feature supports nesting of paragraphs containing inline elements, making content organization more intuitive.
• Enhanced table interactions: Nest within tables, which represents the highest proportion of nesting scenarios, is now more seamless.

Automation: Filter audit log by actions

In the Automation audit log, you can now show or hide entries based on actions, making it easier to find specific rule runs. For example, you could choose to see all rule runs where the "Send email" action was used.

1. Navigate to automation:
   • For Confluence automation, go to Confluence settings > Automation
   • For Jira automation, go to Jira settings > System > Global automation
2. Select Audit log.
3. Select Actions and choose which actions you want to filter by.

Smart buttons coming to templates and blueprints

You can now add automation smart buttons to user-created templates and page blueprints. When someone creates a page with a template that has a smart button, they will be able to configure the button.

In space settings or admin settings, find Templates and blueprints and edit a template. Type /smart button to add an automation smart button.

When any user creates a page using your template, they can select the button to configure each its fields.

Rovo customer admins can now add bookmarks

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

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

How to add or edit Rovo Search bookmarks

Task editing permissions for Live Pages

This update introduces a new "request to edit" feature for tasks on Live Pages, allowing users without edit access to request permission to make changes.

• Request to edit: Users can now request edit access for tasks on Live Pages, if they currently have view-only access.
• Admin approval: Admins receive notifications for edit requests and can grant or deny access directly from the notification.
• Access tracking: All edit requests and approvals are logged for better tracking and auditing.

Editor: Add media from web links

You can now add media, including images and videos, directly from web links into your Confluence pages. This is an update to the existing image upload process. In the Add image, video, or file toolbar dropdown and backslash command palette, you can now upload files or media from links.

• Image and video upload from web links: The new feature allows you to insert media by pasting a URL, making it faster for you to add online resources to your content.
• Updated toolbar and quick actions: The toolbar and quick action commands now open a popup with two tabs, "file" and "link", for more flexible media insertion.

Summarize whiteboards with Atlassian Intelligence

Save time and get the details you need to do your work faster by generating a summary of the content on an whiteboard using Atlassian Intelligence.

1. Go to the Confluence whiteboard you want to summarize.
2. Select Summarize from the top right (to the left of the share button).
3. Atlassian Intelligence will generate a summary of the whiteboard's contents.

At this time, summaries generated by Atlassian Intelligence don’t include content from images or links.

New user input fields for automation components

We are adding dynamic selections to the user fields in Automation for Confluence components.

You will now be able to choose to options related to users referenced in your rule. These include "Rule initiator" and "Current user in rule."

The initiator is the user who took the action that triggered the rule.

The current user is the user that was most recently referenced by another component earlier in the rule's workflow.

Use automation rules to add text to new pages

The Publish new page automation component now supports adding text to the body of the page. We're adding an additional field that allows you to input content that will be added to the page when it's created.

Add the Create page action to your automation rule and input your custom text in the Page content field.

Summarize changes to a page or blog post

Now when Premium and Enterprise customers visit a page for the first time in a while, they can use Atlassian Intelligence to generate a brief summary of changes since their last visit. Use this feature to quickly catch up on changes to a project plan after an important review, or to get a sense of what you missed while you were on vacation.

Atlassian Intelligence will only generate a summary if someone has edited the page since your last visit. If there aren't any changes to summarize, it will present you with a summary of the page to help you refresh your memory on the key points.

Atlassian Intelligence is available to all customers with Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

To summarize changes using Atlassian Intelligence:

1. Navigate to a Confluence page or blog post that you’ve visited before.
2. Select Summarize changes from the drop-down menu in the Summarize button on the top right.
3. Atlassian Intelligence will generate a summary of changes since you last visited the page or post.

You can copy the summary to your clipboard, rate the quality of the summary, and provide feedback on the feature using the buttons at the bottom of the summary panel.

Copy URL button available in the automation audit log

We've added a new button to Jira and Confluence automation that allows you to copy the URL of the audit log to your clipboard. This button will help you easily copy and share your audit log's URL.

To start using this feature:

1. Open the audit log from either Jira or Confluence automation.
2. Select Copy link in the audit log to copy the URL.
3. The URL is now copied to your clipboard and ready to use.

Learn more about using the audit log in Atlassian automation

Classify content from the more actions menu

You can now classify content by selecting More actions (•••) > Classify content.

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

You can classify content once your organization admin has set up classification levels for your organization.

To classify an item:

1. Edit the item (only required for pages and blogposts).
2. Select More actions (•••) > Classify content.
3. Choose a classification level.
4. Select Update.

More about data classification:

• Classify a page or blogpost
• Classify an issue
• Classify a request
• Set a default classification level for content
• Set a default classification level for issues
• Set a default classification level for requests

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

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

Upgrade your Compass GitHub app:

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

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

Custom Compass component types support in Jira

We're introducing a new capability in Compass that allows product admins to create component types based on the terminology their teams use to categorize them. Custom type names will be supported in Jira, but will use the OTHER icon.

In Compass, product admins can create up to 14 component types, but anyone on their Compass plan can use them. This customization helps software teams better group components at a high level across their distributed architecture.

Visual SQL: Write custom formulas using Atlassian Intelligence (AI)

You no longer need to worry about memorizing SQLite syntax for custom formulas. You can use natural language to tell AI how you want to transform the data in one of your columns, and AI will generate the SQLite expression for you.

To try it out:

1. Add a Formula column or Apply formula step.
2. Select Custom from the formula options.
3. Select AI.
4. Use natural language to describe how you want to transform your data.
5. Select Submit.

Easier way to query Jira custom fields

To simplify querying your custom fields, we've added a new Issue custom fields table to the "Jira family of products" schema. Each of your custom fields is represented as a column in the table. This also means you can now add multiple custom fields to a single query.

To try out the new table:

1. Create or edit a visual mode query. Note that the table isn't available for SQL mode queries.
2. For the query's data source, select an Atlassian Data Lake connection that includes Jira data.
3. Select Add column to open the schema browser. The Issue custom field table should appear in the list under "Jira family of products".