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

Keep on top of sensitive data in your organization with redaction

Keeping sensitive data out of your team’s Confluence pages is an ongoing battle, and redaction is one strategy you can use to reduce the risk to your organization.

Guard Detect sends an alert if sensitive data is detected when a Confluence page is published or updated. The alert now includes an excerpt of the sensitive data to help you investigate.

If you decide that the data is sensitive and should not be stored in Confluence, you can redact the content directly from the alert, regardless of any space permissions or page restrictions.

This deletes the sensitive data and replaces it with a solid bar in the current version of the page. You also have the option to remove any historical versions that contained the data from the page history.

It’s important to note that redaction permanently deletes the data. It doesn’t simply mask or restrict it for certain users.

How to redact sensitive data

To get started with this change:

1. In Guard Detect, view a sensitive data alert.
2. Review each instance of sensitive data highlighted in the alert and the suggested investigation steps.
3. Select Redact and indicate whether you also want to remove the page history.

The sensitive data will be deleted and replaced with a solid bar everywhere it appears in the current version of that page. It can’t be restored or undone. What happens when data is redacted?

Redaction requires Atlassian Guard Premium.

Detect potentially sensitive data in Jira in real time

Managing sensitive data is a huge priority for many organizations.

If you have Atlassian Guard Premium, you can now detect when sensitive data is added to a Jira issue, including financial details, credentials, and other terms that may be sensitive to your organization.

We detect sensitive data in the issue summary, description, any other field that contains free text. We don’t currently detect sensitive data in comments, or in fields that are not free text, such as dropdown menus.

As an issue may have many subsequent updates, we update the existing alert if more sensitive data is added, and only send a new alert if more sensitive data is detected after 24 hours.

For every content scanning detection you have the option to send alerts for Confluence, for Jira products, or both. For example, if storing International Bank Account Numbers (IBAN) in Jira is part of your process, you can turn the IBAN content scanning detection off for Jira, and keep it on for Confluence.

Because you may have legitimate reasons to store certain sensitive data in Jira, we’re rolling out this change with all content scanning detections turned off for Jira.

To start getting sensitive data alerts go to Detections > Content scanning then expand each of the detections you want to turn on.

What sensitive data is detected?

Be alerted about user API token changes

If you have Atlassian Guard Premium, you’ll now get an alert when a user API token is created by a user you manage, or when a token is revoked, either by the owner or by an organization admin.

This helps your security team be the first to know when tokens are created or revoked unexpectedly.

This detection is enabled by default if you have Atlassian Guard Premium. Alerts are only sent for tokens created by managed accounts.

If you don’t want to get alerts about user API token changes, go to Guard Detect > Detections > User activity and turn off the User API token changes detection.

SCIM API keys expire in one year

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

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

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

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

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

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

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

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

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

Scroll and filter Atlassian product changes with ease

The new table layout in Product updates allows you to view more release notes on one page.

Filter by Status, Change type, or Product to get an overview of the changes most important to you, in the order they’re rolling out, so you can plan more efficiently.

How to keep up with Atlassian changes

To find and view release notes:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product updates.

Get early access to goals, projects, and more for your sites

You can now enable a handful of early-access features for sites in your organization. Goals, projects, and other platform experiences can be created in Atlassian Home and used across Atlassian products. These features help establish regular communication practices, helping teams and stakeholders stay up-to-date and in the loop.

To get started:

1. Switch to Administration from the app switcher, or go to admin.atlassian.com.
2. Go to Settings at the top of the page.
3. Select Platform Experiences on the left navigation bar.
4. Select the Sign up now button and follow the prompts.

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.

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

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

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

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

More about what we copy to sandboxes

We’re replacing Beacon with Guard Detect

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

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

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

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

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

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

Accessibility and style improvements to tables and page layouts

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

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

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.

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

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

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

This process requires Atlassian Guard Premium.

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

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

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.

Turn on Direct Access for products on a domain with a one-time prompt

When a user requests access to a new product, admins who don't have Direct Access enabled on their domain will need to review and approve each request manually.

To make managing access requests easy and efficient, admins can now turn on Direct Access for products on their domain via a one-time prompt. They can dismiss this prompt and turn on Direct Access anytime in Admin Hub in User Access Settings.

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.

Rovo customer admins can now add bookmarks

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

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

How to add or edit Rovo Search bookmarks

Copy product data early access program: Solving duplication of Jira entities

We're working on a solution to allow you to make decisions on how conflicting entities should be handled before copying data. We expect this to help in reducing the effort taken for post-migration clean-up. Before we make this feature generally available, we’re looking for individuals who would like to partner with us in an early access program to ensure our solution meets your needs.

Read the[ community blog|https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Early-Access-Program-for-solving-duplication-of-Jira-entities/ba-p/2862936] which has steps for how to sign up for the early access program.

Apply security settings to different mobile apps

You now have the flexibility to set up different security policies to meet the security needs of specific Atlassian mobile apps. A mobile app policy allows you to apply security settings to all or one mobile app at a time.

Your default mobile policy applies security settings to Confluence, Jira and Opsgenie. To apply different levels of security to one of these mobile apps, you can create a mobile app policy or edit your default mobile app policy.

To create a mobile app policy:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Mobile app policies.
3. Select Create mobile app policy or Add mobile app policy and follow the prompts*.*

To edit a mobile app policy:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Mobile app policies.
3. To edit a mobile app policy, select Actions (…) and follow the prompts*.*

Prevent people who are not logged in from viewing Confluence pages

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

You can now use the anonymous access rule to prevent people who aren’t logged in from viewing Confluence pages.

Previously, the rule only blocked anonymous access to Jira issues. Now, in policies that cover Products, it will block Confluence pages as well.

The anonymous access rule requires Atlassian Guard Standard.

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

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

Prevent people who are not logged in from viewing Confluence pages

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

You can now use the anonymous access rule to prevent people who aren’t logged in from viewing Confluence pages.

Previously, the rule blocked anonymous access to Jira issues and in policies that cover Products in Confluence. Now, it will also block access to Confluence pages within policies that cover spaces and projects.

The anonymous access rule requires Atlassian Guard Standard.

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.

Sync user principal name from Microsoft Entra

You can now identify users you sync from Microsoft Entra (formerly Microsoft Azure AD) to Atlassian with user principal name.

By default all existing organizations use email when they sync users to Atlassian. You can change the setting from email to user principal name.

To select how to identify users:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your Microsoft Entra directory.
4. Select Edit to update how you identify users.
5. Select either user principal name or email.
6. Select Save settings.

API token controls no longer require Atlassian Guard Standard

You no longer need a subscription to Atlassian Guard Standard to use API token controls.

When you set up an authentication policy, you can allow or block members from:

-Creating a new API token to authenticate
-Using an existing API token to authenticate

You can do this without a subscription to Atlassian Guard Standard

To try out the API token setting:

1. Log in to admin.atlassian.com
2. Select Security > Authentication policies.
3. Select Edit for the policy you want to change.
4. Select block API token setting.

Knowing when you're approaching the Free user limit just got easier

We're making it easier for you to know when you're approaching the Free user limit when you're looking at Admin settings by including a banner under Directory > Users.

Tailor your Jira Service Management sandbox setup

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

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

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

Learn about what we copy to sandbox

Track Rovo usage with insights on Agent interactions

You can now view the number of requests users have sent to Rovo Chat or Agents. Usage metrics also include the percentage of unused quota left for the month. For a limited time, usage beyond quotas will not incur additional charges.

How Rovo usage quota works

To view quota usage for Rovo requests:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security then Insights.
3. Navigate to the chart named Requests sent to Rovo.

Deleting extra mobile app policies that we don’t enforce

We currently allow you to create one mobile app policy per organization.

Some of you may have created multiple mobile app policies with the Admin REST API. Even if you created more than one, we only enforce the most recent policy.

Effective 04 December 2024, we will delete any extra mobile app policies that we don’t enforce. You will see the policy we deleted in audit logs.

You can use the Admin REST API to view deleted policies for up to 30 days.

We are making this change in order to enable the introduction of a new update: you will soon be able to create one mobile app policy per app.

Understand mobile app policies

Get security alerts in your language

Guard Detect generates alerts when suspicious user user activity or sensitive data is detected.

You can now use Guard Detect in more than 20 languages. Like Atlassian Administration, it uses the language preference set in your Atlassian account profile.

Guard Detect requires Atlassian Guard Premium.

Block the download of files attached to pages with extended data export rule

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

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

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

This change will affect any existing policies that have configured the data export rule to block exports. At this stage, it will not block attachment downloads in Jira.

To check whether your data security policies currently block exports:

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

The data export rule requires Atlassian Guard Standard.

Be alerted about insecure mobile devices

If you have Atlassian Guard Premium, you’ll now get an alert when our periodic checks detect that a mobile device used to access the Jira Cloud, Confluence Cloud, or Opsgenie cloud app doesn’t use a screen lock or has unauthorized modifications.

Mobile devices that don’t meet minimum security requirements have a higher risk of unauthorized access. One way to protect your organization is to consider using a mobile app policy to only allow access from devices that require a PIN, passcode, or biometrics to unlock the screen, and have not been jailbroken, rooted, or otherwise compromised.

This detection is enabled by default if you have Atlassian Guard Premium.

If you don’t want to receive alerts about potentially insecure devices, go to Guard Detect > Detections > User activity and turn off the Access mobile app from insecure device detection.

Create and edit status names from the project summary

Admins in team-managed projects can now create and edit status names directly from the project summary page, without navigating to project settings. Simply select Create status, or hover over the name to see the Edit icon, make your updates, and confirm.

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

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

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

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

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

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

Creating a Jira issue can now trigger an automation in Confluence

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

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

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

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

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"

Highlight work with color in your list

Identify and highlight key work that needs your attention with format rules in your list. With a format rule, you can automatically format individual cells or entire rows with colors, when specific criteria is met.

For example, to highlight work that’s running behind schedule, you could create the rule: red row when due date is before today. More examples of format rules and their purpose, plus how to create a format rule.

To create a new format rule in your list:

1. Go to your project, and select List.
2. Select Format.
3. Select + Add a rule in the Format rules sidepanel.

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.

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.

Validate your rules in Jira and Confluence automation

We're introducing a new feature to Jira and Confluence automation that allows you to check your rule for errors before enabling them. This validation feature will help to improve efficiency and accuracy during rule creation, as you'll no longer need to search for errors yourself before turning on your rule. Please note that some errors may not be identified during the validation process, so keep an eye on the audit log to ensure no more errors occur after the rule runs.

To get started with this change:

1. Navigate to the automation rule builder in Jira or Confluence automation.

2. Create your desired rule.

3. Once you have finished editing your rule, click on the dropdown arrow next to the Turn on rule button.

4. Select Validate rule.

5. We'll advise you if any errors or warnings were found in your rule. Follow the steps provided in the rule builder to fix these.

6. Select Validate rule again to ensure your rule no longer contains any identifiable errors.

7. Once your rule is ready, turn it on.

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.

Create and edit issue types from the project summary

Admins in team-managed projects can now create and edit issue types directly from the project summary page, without navigating to project settings. Simply select Create issue type, or hover over the name to see the Edit icon, make your updates, and confirm.

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.

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.

What is Smart Link list view?

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.

It's easier for end users to connect the right type of Confluence docs to Jira issues

Jira issues have a field for Confluence content so that you can link important documents to your tasks in Jira. Now, if you’re viewing a bug, story, or epic issue, you may see a recommended Confluence template.

These templates are customized based on the issue type. For example, a ‘known errors' template will appear in a bug issue.

Before, end users could only use these templates by sending a request for Confluence to their admin. Now, end users on Free plans can access Confluence and the templates straight away, without leaving Jira and without waiting for request approval.

You can dismiss these template recommendations at any time.

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.

More text formatting for Jira paragraph custom fields

With more edit options available in newly created paragraph custom fields, you can style long-form text and links how you like. Now available for company-managed projects.

To view this change to paragraph custom fields:

1. Create a new paragraph custom field in your Jira project.
2. Add the newly created paragraph field to any issue type in project settings.
3. Open any issue within the same issue type.
4. Select the newly created paragraph custom field from the issue, to view and use the new edit experience.

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 are now available in more fields

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

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

Read more about using Smart Links

Create action items in Jira issues

There may be times when you just want a simple to-do list instead of creating subtasks within issues.

You can now add action items within the description and comments of an issue. This feature lets you use checkboxes to format your text, helping you compile a list of the things that don’t need separate tracking.

More about action items

To get started:

1. Navigate to a Jira issue.
2. In the Description field, select Action item (checkbox icon) from the toolbar available in the editor or type [] (open and close square brackets).
3. Type your action.

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.

Edit the name or icon of a business project

You can now edit a business project’s name and icon directly in line, without navigating to project settings. Simply select either the name or project from anywhere in the project, make your updates, and confirm.

Create custom fields while building forms

Admins in team-managed projects can now create custom fields within a form as they're building the form, without having to go to project settings.

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.

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.

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.

Filter form-related requests in Jira

You can now quickly filter and locate requests linked to a submitted form, without the need to manually search.

To get started:

1. Open Jira and navigate your business project.
2. Go to the Forms tab.
3. Locate the recent form.
4. Select View submitted.

You’ll be taken to your list view with the new search filter already applied.

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

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

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

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

Nest media and codeblocks in quotes

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

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

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

New and updated virtual agent Channel management

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

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

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

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

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

A new home for help center customization features

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

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 available on Free sites. If you'd like access to it, 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.

Introducing weekly view for the Jira Service Management calendar

We’re excited to add the highly requested week view to Jira Service Management's calendar alongside the existing monthly view of work. Now, you can plan, track, and prioritize work with a focused view week by week, and schedule work items by the hour for more granular control of your tasks and requests.

1. Go to Calendar in your service project's navigation.
2. Select the Month menu, and switch to Week.
3. View and schedule your work items on the calendar by week.

View settings and bug fixes for calendars in business projects

We're rolling out the following improvements to the calendar experience in business projects.

View settings
We’ve added a View settings button to make it easier to navigate, stay informed, and customize your view. Now you can:

• Quickly open issues from the sidebar
• Hide done items
• Show or hide issue keys
• Show or hide weekends
• Choose which day the week starts on
• Show software release dates

Bug fixes
• You can now unschedule work even if the schedule work panel is empty.
• Summaries are no longer truncated.

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

Compact way to see all linked issues in Jira

Instead of scrolling through a long list of linked issues, they’re now neatly displayed in the Linked issues column.

When selected, a smaller window opens with linked issues sitting side-by-side. Each is still hyperlinked so you can quickly refresh your memory, and a scroll bar means you still have access to them all.

This saves on space and helps to reduce page load times too.

Record or upload Loom videos on a Jira issue

Users can now record Loom videos directly from the Jira issue view, or insert existing Loom videos directly into a Jira issue, ticket description, or comment. If Loom is not an active product on a site, attempting to record a Loom video in the issue view will allow users to activate Loom, or send a request to activate Loom to the site admin.

From the + Add menu in a Jira issue, select the Record a Loom video option to record directly into the issue. These Loom videos will appear under a new Loom video section in the Jira issue.

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.

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.

Connect your coding tools with ease

It's now easier than ever to connect your source code management tools to your software projects. GitHub, GitLab, Bitbucket? Too easy – the options are practically endless. Minimize context switching, know the exact development status of work, and more.

Collect work requests with forms for all Jira projects

Collect work requests from stakeholders directly into all Jira projects. Once someone completes your form, this creates an issue ready to be prioritised and worked on straight away.

To create a Jira form, you’ll need project admin access:

1. Open a project, and navigate to Forms in the project navigation.
2. Select an existing form, or select + Create form.

How to create a form.

An improvement to the Jira search experience

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, Description and all text custom fields. The Search issues field in the top navigation will also follow this rule.

Before this change, results were also based in Comments and Worklog, 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, go to the issue navigator in your project and select Issues.

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

View recent links from Smart Link hover cards

You can now view relevant documents, pages, and other work items straight from Smart Links.

To view recent links:

1. Hover over an inline Smart Link.
2. Select View recent links.

The modal that opened will show you documents and work items:

• found in the link
• where the link is inserted

Update story points directly in the issue navigator list view

You can now edit the Story points and Story point estimate fields directly in the list view of the issue navigator.

1. Go to Issues in the project sidebar
2. Switch to List view
3. Find the Story points or Story points estimate columns and update them without opening the issue

We’ve cleaned up your Jira backlog

Only view the issues that need doing from your backlog. We’re now automatically filtering out any issues if they have a done status or a resolution.

To view this change to your backlog, you'll need to be using a team-managed software project with sprints enabled:

1. In your project navigation, open your Backlog.
2. View your list of issues in your backlog. This should no longer include issues with a status category of done.

To view done issues, navigate to other views such as the board or list.

Create embedded release notes with a Confluence template

You can now create release notes in an embedded Confluence page using our improved release notes template.

When you start the release process, you can create release notes in a Confluence page. Select the issue types and Jira fields you want to add to the template.

The release notes will open in a new Confluence page that you can edit and share.

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.

Signing up for Confluence from Jira just got easier

If you’re using Jira and don’t have Confluence, you might see a prompt to try it out. If you select this prompt, you will go through a signup flow. Previously, this flow was full-screen and used an older style of Atlassian branding.

The flow has been updated with new branding. It also opens on a smaller popup screen that overlays your Jira screen.

The popup will vary depending on which Confluence plan you’re signing up for.

Efficiency improvements in the calendar view

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

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

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

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

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

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

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

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

Collect more relevant work requests with Jira forms

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

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

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

Clear date and time filters in the automation audit log

We're introducing a new feature to Jira and Confluence automation that allows you to clear all selected filters in the audit log with a click of a button. This change will help you to save time and improve efficiency, as you'll no longer need to manually de-select all the selected filters yourself.

To start using this feature:

• Open the audit log in either Jira or Confluence automation.
• Apply any desired date and time filters to the audit log.
• Once you are done with these filters, select the Date and time button.
• Select Clear filter. All selected date and time filters will automatically be de-selected.
• Your audit log will now have no date and time filters applied to it.

Learn more about using the audit log in Jira and Confluence automation

Change the status straight from Smart Link list view

Update the status using a Smart Link list view without the need to open the Jira issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select the status from one of the items. Once the dropdown appears, you can update the status straight from the cell.

Change the assignee straight from Smart Link list view

Change the assignee using a Smart Link list without the need to open the issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select assignee from one of the items. Once the dropdown appears, you can change the assignee straight from the cell.

Change the priority straight from Smart Link list view

Update the priority of Jira issues straight from Smart Link list view.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select the priority from one of the items. Once the dropdown appears, you can update the priority straight from the cell.

Choose how long done items remain on your Jira board

On Jira business projects, you now have more control over what work you can see from the Board. Once you move a work item into a done column, they will now remain visible from that column for the chosen number of days. After this, you can find those work items from other views such as the List.

To choose how long done items remain on your board:

1. Open a Jira business project.
2. Select Board from the project view navigation.
3. Select More to open the View options.
4. Select Hide done items after.
5. Choose from the available number of days.

Updates to filter name searches

We’re updating the filter name searches in dashboards and the filters page to provide consistent and predictable results.

Previously, filter name searches used the JQL text search syntax, which produced inconsistent results when the search term contained certain special characters. Now, search results will display all filters that contain the search term.

The 'Show sum' functionality has moved in Assets in Jira Service Management

We've made a few minor changes to the feature in Assets in Jira Service Management that allows you automatically calculate and display the sum of multiple 'Float' or 'Integer' attributes.

This feature used to be available as a setting in the Attribute screen, visible to all users. Now the feature is available in the List view > Columns screen, and can be configured individually for each user.

If you like, take a further look at the documentation here.

Use Atlassian Intelligence to create issues (beta) from Slack

You can now use Atlassian Intelligence (AI) to create Jira issues directly from Slack messages and threads. AI uses the context of your conversations to generate the summary and description, enabling you to create issues faster.

Find out how to use Atlassian Intelligence to create issues from Slack

To use Atlassian Intelligence to create an issue from Slack:

1. Install the Jira Cloud app for Slack.
2. Go to a Slack message or thread.
3. Select More actions, then select Create issue from Jira Cloud.
4. Choose a Site and Project.
5. Select Use Atlassian Intelligence to generate the summary and description.
6. Complete other fields as necessary and select Submit.

The Assets object field will only display the label of an object when viewed from within the portal in Jira Service Management

When you display an object in the Assets object field in Jira Service Management, you can also select one or more attributes in the User Interaction panel that will appear after the label of the object. You could use this feature to display - for example - the date the object was last modified, or the manufacturer of a piece of equipment.

These attribute values originally appeared in the search results and as part of the selected items. We will continue to show these in the search results, but this was too much detail to appear in the selected items, so now the Assets object field will only show the label when you select an item in the object picker in the portal.

This change won't affect the Assets object fields anywhere else in Jira Service Management.

Manage deadlines and overdue work easily from your Jira board

Track and manage approaching deadlines easily via the Sprint Insights on your Jira board. With the new Due tab in the Issues for attention widget, you can quickly view overdue and upcoming work items, tailored to your board type.

For scrum boards, you can view overdue issues, and upcoming issues due within the current sprint. For kanban boards, you can view overdue issues, and upcoming issues that are due within the next 2 weeks.

To try it out on any software project:

1. Open a Kanban or Scrum board.
2. Select Insights.
3. Locate the Issues for attention widget.
4. Select the Due tab.

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.

Colourful categories

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

Template bundles in the project create page

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

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

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

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

Another way to create a bundle is to:

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

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

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

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

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

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 in your Jira settings. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

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.

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.

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.

Improvements to the workflow editor

We've updated the workflow diagram in company-managed projects to be faster and more accessible.

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

Plan Timeline header issue create improvement

You can now create issue types directly on your plan timeline without hunting through the work hierarchy level.

From the Timeline header create button, you'll be prompted to select a project, which will then display all possible child issue types. Save time and start creating new work inside your plan with less hassle.

New rules coming to the New Workflow Editor

In the new workflow editor, you will soon be able to use the following rules:

• Set issue security level
• Validate that an issue has a specific status
• Restrict which users can transition issues between statuses

All of these were available in the old workflow editor before, but now you can also use them in the new workflow editor.

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.

Maintain approval history when bypassing approvals

This change allows users to bypass approvals while preserving approval data, preventing data loss and improving history tracking.

During an approval state of a workflow, an issue can't transition to the approved or declined status until all approval decisions are finalized.

However, transitions other than ‘Approve’ or ‘Decline’ can be used to manually transition issues and bypass the approval state. Previously, if you transitioned an issue’s approval state to a status other than ‘Approve’ or ‘Decline’, it deleted the approval along with any recorded approver decisions from the database.

As part of this change:

• if an issue’s approval state is transitioned to a status other than ‘Approve’ or ‘Decline’, it will be recorded as a ‘canceled approval’
• we preserve any active approvals (including approver decisions) that exist for an approval state when an approval state has been bypassed
• all approvals data will be retained in the approvals activity history
• JQL queries will return issues with approvals activity, even if the approval is canceled.

Tip: To ensure your approval state status and approver decisions are clearly conveyed to your customers in the portal activity log, check how your workflow statuses will appear to customers in the portal based on the display names assigned to each workflow status.

1. From your project settings, go to Request types.
2. Select the name of the request type you want to modify, then select the Workflow statuses tab.
3. Review and update the Status name to show customer for each workflow status.

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.

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.

Introducing a brand new toolbar for bulk actions

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

To use the new toolbar:

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

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.

Add external sprints to your plan

You can now assign issues to any sprint in your site regardless of whether it's included in your plan. This allows planners to assign work that belongs to teams outside their plan without leaving the page. Your plan refers to these as external sprints, and adds the EXT. lozenge next to their name.

External sprints are not added to your plan when you assign issues to them. To use the more complex sprint-based planning capabilities such as capacity planning, you'll need to add the board in which that sprint was created as an issue source of your plan.

Jira Plans - Dependencies on the Program board, and the end of Open Beta!

As of today, the Program board is leaving Open Beta and becoming a full-fledged feature of Plans! To mark the occasion, we're shipping a highly-requested feature: dependency management on the Program board.

Read our post in the Atlassian Community about this.

With this change, planners can now:

• filter the Program board to show on or off-track dependencies
• show lines between dependencies
• create new dependencies from the board

and more! See the full depth of these changes in our documentation.

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.

Now it’s easier to add a Loom video to Jira issues

Loom is a video tool that allows people to easily record their screen, add audio commentary, and quickly edit the clips.

If you’re using Jira you may see a recommendation to try Loom out while adding a comment or editing a description in a Jira issue. The recommendation will only show on ‘Bug’ issues.

Admins and end users will see this Loom recommendation. If you have permission to add new products, you can add Loom from the recommendation. If you don’t have permission to add new products, you can send your admin a request to add Loom from the recommendation.

You can dismiss the recommendation anytime. If you have Loom already, you won’t see the recommendations at all.

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.

Quick-add buttons decluttered in the issue view

We’ve consolidated all the quick-add buttons to declutter the issue view, enhance clarity, and scale. You’ll now find buttons, such as "Attach” and “Linked issues”, under the Add button, and buttons from your third-party integrations under Apps.

Read more about the changes

Get new work suggestions for pull requests needing attention

Work suggestions in Jira will now show you new suggestions for pull requests that need your attention.

You’ll see suggestions when your pull requests are ready to merge, have been inactive for more than five days, or when someone adds you as a reviewer on their draft pull requests.

Depending on the source code management tool you’re using and its connection with Jira, you may receive some or all of these work suggestions.

When you select your avatar on the board, these suggestions, if available, will automatically appear in the work suggestions panel.

The new suggestions will be available in scrum and kanban projects in Jira.

Read more about work suggestions in Jira

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.

Update to exclusion rules in Jira plans

We’re making tweak to the way our exclusion rules apply in Jira plans.

Previously, if a parent issue was excluded from a plan timeline, but the child issue was visible, then the parent issue would still show based on “parent completion.”

From now on, the exclusion rule will apply regardless of the completion status of a parent and simply exclude based on the specific exclusion rule.

This unifies exclusion rule behaviour across plans.

Get work suggestions for pull requests with new comments

You’ll now get work suggestions in Jira when new comments are added to your open pull request since the last time you got this suggestion for the same pull request. When you select your avatar on the board, any available suggestions will automatically appear on the work suggestions panel.

The availability of this suggestion type depends on the source code management tool you’re using and its connection with Jira. The new suggestions will be available in scrum and kanban projects in Jira.

Read more about work suggestions in Jira

Updates to creating linked issues for business projects

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

Share your plan using Smart links

Share your plan using the same Smart links you'd find in the rest of Jira. To see how your favorite sharing method might have changed, take a peek at our documentation.

Using the Share button on your plan, you can now:

• share it with other Jira users or people with whom work in Slack (if connected)
• embed your plan in another Atlassian product such as Confluence
• export your data as a .csv file
• create a static image of your plan

A lot of these were available before, but this new way of sharing them is easier, faster, and more flexible.

Create a child issue from your plan timeline

You can now create a child issue type directly on your plan timeline without hunting through the work hierarchy level. Using the inline menu above the issue, you'll be prompted to select a project, which will then display all possible child issue types. Save time and start creating new work inside your plan with less hassle.

New additions to the More (•••) menu on an issue

When viewing the timeline in business projects, you can now change parent issue, edit an issue's start and end dates, and link to to issues using the More (•••) menu on the issue.

Your Program board in Plans now recommends sprints

When you sync sprints in your Program board, you'll now see recommended sprints that align with the dates of the columns.

Plans Group now displays related child work items

When grouping, child issues will now appear under their parent’s group, regardless of their assigned group. This change to the plan timeline behaviour aligns with the list view and project timeline.

Create issues faster by hiding unused fields

Creating issues in Jira is now easier and faster with the ability to focus on the fields you use the most. We’ve added a new setting that lets you quickly hide any fields you haven’t used in the past 30 days. This only updates your personal settings, so it won’t affect anyone else on your team.

To try it out:

• Select Create to create a new issue in Jira.
• Select More actions (•••), then select the toggle next to Hide unused fields to turn the feature on or off.

Create Google Docs in your Google Drive with Jira and Confluence automation

We’re introducing a new component to Jira and Confluence automation that allows you to create a Google Doc in your Google Drive by simply executing a rule. This feature will help you to create Google Docs more quickly and easily, as you’ll no longer need to create them manually - Atlassian automation can do it for you!

To get started with this change:

1. Navigate to the automation rule builder in Jira or Confluence.
2. Select a trigger for your rule.
3. Select the Create Doc in Google Drive action and add it to your rule.
4. Select a Google Drive folder for your Google Doc to be placed in. Your Doc will be placed in your My Drive folder if you don't have permission to select a location for it.
5. Add a title and any body content you want your Google Doc to contain.
6. Add any other desired components to your rule.
7. Once you've edited and finalized your rule, turn it on.
8. Your rule is now ready to go.

Epic Link and Parent Link changes no longer show in the audit logs

As part of our larger stream of work towards deprecating the Epic Link and Parent Link fields (which you can read about in our documentation as well as our updates in our Community space), changes to these fields no longer generate a change record. On issues, this means that changes made to the Epic Link and the Parent Link no longer show in the issue's History tab.

Changes to these fields are also no longer being communicated via the API, which we announced in the developer community.

New restrictions in the new workflow editor experience

We've added two more transition rules to the new workflow editor experience. Prior to this change, these rules only existed in the old workflow editor.

Jira Admin - User filtering for User Picker (multiple users) custom field type

This update is based on a feedback ticket: JRACLOUD-40963 - Allow user filtering for User Picker (multiple users) custom field type

With this change, administrators can limit which users appear in User picker (multiple users) custom fields based on groups and project roles. This behavior mimics the same function found in Data Center versions of Jira.

See how to limit users in User Picker (multiple users) custom fields.

Jira Admin - Restrict who can change an issue's status

When configuring workflows, you can now restrict who can transition an issue's status. This was a rule in the old workflow that we've ported into the new workflow.

Read more about this configuration

Improve issue description clarity with AI

Use Atlassian Intelligence to add clear, consistent structure to your Jira issue descriptions.

Once you have added all the details to include in your description, AI can restructure it into meaningful sections based on the issue type, including:

• User story, context and acceptance criteria (for stories)
• Impact, expected behaviour, and workarounds (for bugs)
• Objectives, scope, and risks (for epics).

The more detail you include in your description to start, the more complete the improved description will be.

To get started:

1. While editing your description, select Writing assistant.
2. Select Improve description.

Atlassian Intelligence will restructure your description and, when you’re happy, you can select Replace to add it to your issue.

Dependency column label changes to Blocks and Blocked by

We’ve changed the plan dependency view column labels from ‘Incoming dependencies’ and ‘Outgoing dependencies’ to Blocked by and Blocks.

We made this change to promote better visibility of the label, which was always cropped due to its length. The long label was a problem for a lot of customers during recent customer testing and investigation. The new label reflects the default name for issue link types that can be added as dependencies, and it aligns with the dependency behaviour in plans, even if another link type name is chosen. We also widened the column length.

The Assets object field will only display the label of an object when viewed from within the portal in Jira Service Management

When you display an object in the Assets object field in Jira Service Management, you can also select one or more attributes in the User Interaction panel that will appear after the label of the object. You could use this feature to display - for example - the date the object was last modified, or the manufacturer of a piece of equipment.

These attribute values originally appeared in the search results and as part of the selected items. We will continue to show these in the search results, but this was too much detail to appear in the selected items, so now the Assets object field will only show the label when you select an item in the object picker in the portal.

This change won't affect the Assets object fields anywhere else in Jira Service Management.

Group alerts using Atlassian Intelligence

Atlassian Intelligence groups related alerts and offers insightful suggestions, helping your on-call teams manage alerts and resolve issues more effectively. Rather than dealing with each alert separately, on-call agents can view a collective summary of similar alerts through an alert group. The current release includes an enhanced alert grouping model that offers an improved quality of groups based on the similarity of alert content.
You can also use Atlassian Intelligence to speed up the process of creating incidents from alerts from List view or AI view. It suggests a title, a description, and a priority for the incident you’re creating which you can use to save time.
The alert detail page shows the alert group generated by Atlassian Intelligence that the alert is part of, so you can quickly access alerts similar to the one you’re viewing to speed up the diagnosis and resolve incidents more efficiently.

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

Virtual service agent in email is now generally available

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

Find out more about using virtual service agent in email

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.

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.

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.

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.

Now access smart values for forms and form fields

Eliminate manual data entry and leverage dynamic data by accessing smart values on submitted forms on issues. Not only can you now retrieve form data in Jira Service Management, but can also use these values to power automations and fuel reporting.

Access any submitted forms on an issue by using forms and the automation lists smart values to format the value of forms in a list when setting up a rule. Plus access any specific smart values of form fields and combine, reformat, and manipulate values to suit your specific needs.

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.

Maintain approval history when bypassing approvals

This change allows users to bypass approvals while preserving approval data, preventing data loss and improving history tracking.

During an approval state of a workflow, an issue can't transition to the approved or declined status until all approval decisions are finalized.

However, transitions other than ‘Approve’ or ‘Decline’ can be used to manually transition issues and bypass the approval state. Previously, if you transitioned an issue’s approval state to a status other than ‘Approve’ or ‘Decline’, it deleted the approval along with any recorded approver decisions from the database.

As part of this change:

• if an issue’s approval state is transitioned to a status other than ‘Approve’ or ‘Decline’, it will be recorded as a ‘canceled approval’
• we preserve any active approvals (including approver decisions) that exist for an approval state when an approval state has been bypassed
• all approvals data will be retained in the approvals activity history
• JQL queries will return issues with approvals activity, even if the approval is canceled.

Tip: To ensure your approval state status and approver decisions are clearly conveyed to your customers in the portal activity log, check how your workflow statuses will appear to customers in the portal based on the display names assigned to each workflow status.

1. From your project settings, go to Request types.
2. Select the name of the request type you want to modify, then select the Workflow statuses tab.
3. Review and update the Status name to show customer for each workflow status.

Add permissions to detail fields for customers and entitlements

Jira admins can now configure view and edit permissions for customer and organization detail fields in projects with the Customer and organization profiles feature enabled. Permissions can also be set for entitlement detail fields in projects with the Products and entitlements feature enabled.

To manage permissions for a detail field:

1. Select Actions (•••) next to the detail field.
2. Select Manage permissions in the dropdown menu.
3. Choose your permissions.
4. Select Save.

Restrict request types to customer accounts and organizations in Jira Service Management

Control who can raise certain requests in both company and team-managed service projects by giving access not only to users and groups, but now to customer accounts and organizations - one of your top requested features!

There may be times when only specific customers should be able to raise certain requests. These could be requests reserved for different departments in your company, or even those managing multiple clients in external companies. Now you have the power to restrict specific request types to these customers who don’t have Atlassian accounts, and with customer organizations, you can save time by not having to add the same customers to multiple service projects.

Read more about restricting request types

Link service projects to a help center

Jira Service Management Premium and Enterprise users can now link specific service projects to a help center, ensuring that customers see only relevant resources.

Linking projects to a help center allows admins to display relevant help resources on the home page, in topics, and in search results.

To link a service project to a help center:

1. Navigate to Settings > Products > Jira Service Management > Configuration.
2. In the Help center section, select View all help centers.
3. Use the More (…) menu next to the desired help center to access Settings and manage project links.

This feature is designed to help admins manage multiple help centers effectively, targeting distinct audience groups with tailored content. Read more about linking service projects to a help center.

Now it’s easier to add a Loom video to Jira issues

Loom is a video tool that allows people to easily record their screen, add audio commentary, and quickly edit the clips.

If you’re using Jira you may see a recommendation to try Loom out while adding a comment or editing a description in a Jira issue. The recommendation will only show on ‘Bug’ issues.

Admins and end users will see this Loom recommendation. If you have permission to add new products, you can add Loom from the recommendation. If you don’t have permission to add new products, you can send your admin a request to add Loom from the recommendation.

You can dismiss the recommendation anytime. If you have Loom already, you won’t see the recommendations at all.

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

View Assets objects across change management features

Jira Service Management now provides enhanced visibility for Assets objects within change management features, expanding beyond service-focused insights. By setting up an Assets objects custom field and adding it to your change and incident request types, you can:

• View change conflicts on Assets objects, just as you would for affected services, within specified time ranges from the risk insights panel

• View recent incidents on Assets objects from the risk insights panel

• Monitor Assets in the change calendar by selecting Assets objects from within your changes.

Read more about connecting Assets schemas with changes

Read more about connecting Assets schemas with incidents

Updates to creating linked issues in Jira Service Management

When you create linked issues in Jira Service Management projects, you can no longer upload attachments.

Instead, upload attachments after you create the linked issue.

These changes apply for both commercial and FedRAMP Jira Service Management projects.

A new way to manage issue security on request types in Jira Service Management

No longer do you need to add the Security level field to request types, now manage restrictions all in one centralized place in company-managed service projects.

Select Restrictions when you are configuring a request type, and from there you’ll be able to control both who has access to raise requests and view issues. This gives you more control and confidence when it comes to knowing how request types are locked down.

Plus for those who use default security levels, you’ll now have better visibility of how it applies to request types in your project.

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 fields in the virtual service agent's 'send web request' step

We've added new fields to the send web request step in the virtual service agent.

• The Request timeout (in seconds) field allows you to choose a specific timeout (between 5 and 30 seconds) for web requests. In the event of a timeout, the conversation continues down the ELSE branch.
• The Response variable field lets you store web responses from send web request steps, and then use them in send message and send web request steps later in a conversation.

We've also added the ability to use Jira custom fields and system fields in the send message step, using templating expressions that were previously only accessible via web request variables.

Read more about creating a 'send web request' step in a virtual service agent conversation flow.

Introducing ‘Request type groups’ for HR company-managed service projects

Enhance your service management with Request type groups, which enable the efficient categorization and management of HR services. This feature makes it easier for HR teams to define, organize, deliver, and report on services, enhancing visibility and collaboration within and across departments.

Similar to how portal groups are used to group related request types in the customer portal, request type groups can group related request types within a single project, improving visibility and management for the team(s) handling these requests.

For example, a request type group like ‘Employee onboarding’ might have request types such as ‘Conduct background checks’, ‘Set up payroll’, and ‘Provision hardware for new employee’ assigned to it. Here, ‘Employee onboarding’ represents the service a team or individual is responsible for, while the request types detail the specific types of work or tasks that form a part of that service.

You can use request type groups to create custom queues and use them in JQL queries to facilitate reporting across grouped request types.

To see this change, you must create a new company-managed service project using the HR project template after this feature has been released, or:

1. From your company-managed service project, select Project settings, then select Features.
2. Find Request type groups in the ‘Feature lab’ section.
3. Select the toggle to turn on the Request type groups feature.
4. Under ‘Request management’ in the left navigation, select Request types.

On the request types settings screen, you’ll see a ‘Request type group’ column in the table that displays the name of the group to which each request type has been assigned. There is also a filter that enables the display of the project’s request types by selected request type groups.

Some HR-specific request type groups will be available when creating a new company-managed service project using the HR project template. You can rename or delete these, or create your own.

To assign a request type to a group (or change the group the request type is assigned to):

1. Next to the request type you want to update, select More actions then in the ‘Request type group’ section, select Edit.
2. Make sure you’re in the Assign to group tab in the modal.
3. On the ‘Request type group’ field, use the dropdown arrow to display the list of available request type groups, then select the one you want to assign the request type to. Note that request types can be assigned to only one request type group at a time.
4. You can create a new request type group by entering the new group name into the field, then selecting Create “name of group”.
5. To remove the group the request type is assigned to, select the cross next to the group name. If no group is selected, the request type will be ‘Unassigned’.
6. Select Done.

To manage request type groups:

1. On the request types settings screen, select More actions for any request type, then select Edit in the ‘Request type group’ section.
2. Make sure you’re in the Manage groups tab in the modal.
3. To add a new request type group, select Create request type group at the bottom of the modal. Enter the name of your new group, then select the check icon.
4. To rename a request type group, select the name of the group you wish to edit, make your changes then select the check icon.
5. To delete a request type group, select Delete next to the group you wish to delete. You’ll see a message showing the number of request types that will become ‘Unassigned’. Select Delete to proceed.
6. When you’ve finished editing your groups, select Done.

To turn off this feature:

1. From your company-managed service project, select Project settings, then select Features.
2. Find Request type groups in the ‘Feature lab’ section.
3. Select the toggle to turn off the Request type groups feature.

New issue security scheme for company-managed service projects

We’re introducing a new default issue security scheme, a useful starting point for fast-tracking the implementation of issue security in your new Jira Service Management company-managed projects.

Previously, restricting access to sensitive or confidential data in issues required an admin to create an issue security scheme and associated levels, assign users, groups and/or custom fields, and then add the security level system field to the relevant request types.

The new issue security scheme will be associated with every new company-managed service project created using a project template, removing the need to create a scheme from scratch and enabling admins to quickly and easily implement issue security levels. It can be used as is or customized to suit the needs of any teams (like HR, legal, and finance) that need assurance that only certain people can see particular issues.

Find out how managing issue security is about to get a whole lot easier.

To see this change, you must:

• be on a Standard or Premium plan for Jira Service Management
• be a Jira admin (only Jira admins can configure issue-level security)
• create a new company-managed service project using a project template (after this feature is released).

To view and configure the issue security scheme:

• Select Settings ( ), then select Issues.
• In the Issue attributes section in the left navigation, select Issue security schemes.
• You’ll see the ‘Default Issue Security Scheme for JSM' among the list of available schemes.

The issue security scheme comes with two preconfigured issue security levels:

• Sensitive cases: These work items are only visible to the assignee and the reporter to lock down access to the most restrictive audience. This is recommended for use cases like HR case management where the information is extremely sensitive.
• Service desk team: This will restrict the work item to the reporter and the service desk team (as well as the assignee, project lead, and project admins). This is recommended for less critical use cases, such as HR queries, leave requests, contract management etc.

You can tailor these levels to meet your needs or add your own levels, then choose one to set as the default security level that will be applied to issues. Read more about how to manage security levels for issues.

To associate the issue security scheme to an existing company-managed service project:

• From your project, select More actions next to the project name, then select Project settings.
• Select Access, then Issue security.
• Select Actions, then Select a scheme or Use a different scheme (to change schemes).
• In the Scheme drop-down list, select ‘Default Issue Security Scheme for JSM’, then select Next.
• Select Associate, then select Acknowledge.

Once the scheme has been assigned to your project and you’ve set your default security level, you can ensure that issues have security fields added by default.

The virtual service agent is now available on your help center

Allow customers visiting your help center to quickly get the information they need – without having to manually search for articles or request forms!

The virtual service agent uses machine learning to recognize questions and requests. It can automate repetitive tasks using turn-by-turn conversation flows, artificial intelligence connected to your knowledge base, or a combination of both.

Find out how to use the virtual service agent in your help center

Dedicated page for Atlassian Intelligence answers in the virtual service agent

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

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

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

Read more about Atlassian Intelligence answers.

Address gaps in your knowledge base with suggested topics

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

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

Read more about suggested topics in knowledge base.

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

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

To turn on suggestions for a project:

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

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

Read more about suggestions.

Tailor your Jira Service Management sandbox setup

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

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

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

Learn about what we copy to sandbox

Enhanced customer and organization directory for Jira Service Management

We are excited to introduce a refreshed directory experience in Jira Service Management, featuring separate views of Customers and Organizations. This update provides a more modern and user-friendly interface, allowing you to easily switch between customer and organization views, reducing clutter and enhancing focus. The new layout is available to all service projects, enhancing navigation and clarity without requiring any additional setup.

To get started with this change:

1. From your service project's sidebar, go to Directory.
2. Select Customers to view the customers in your project.
3. Select Organizations to view the customer organizations associated with your project.

Multiple AI features in Jira Service Management are now generally available

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

• Similar requests panel that helps agents easily find issues similar to the one they’re working on.
• Customer sentiment that helps you quickly understand how customers are feeling based on their comments.
• Triage issues that suggests new request types for multiple issues in your queue.

Read more about Atlassian Intelligence features in Jira Service Management.

Find resources related to your incidents using Atlassian Intelligence

Atlassian Intelligence speeds up the process of finding the right resources related to your incidents so your on-call teams can save time. Select an incident and then Find resources to generate a list of knowledge articles (from Confluence, Google Docs, etc.), post-incident review (PIR) reports, Jira issues, and resources from third-party tools such as Slack (provided you have appropriate access permissions). Read more about finding related resources.

New onboarding and navigation for the virtual service agent

Getting started with the virtual service agent is now even easier than ever!

When you create a new virtual service agent for a project, you'll now see an updated landing page, experience a streamlined onboarding process, and brand new navigation.

Discover how the virtual service agent works, or find out how to set up your virtual service agent.

Global on-call schedules and escalation policies in your operations

With this release, you can view, create, and manage on-call schedules and escalation policies for your team's operations at a global level. Configuring and managing on-call schedules and escalation policies for the entire site allows you to add multiple people from across teams rather than being restricted to a single team. Having responders from across teams speeds up the scheduling and escalation process, ensuring greater efficiency in the incident management process.

Summarize incidents and create incident timelines in Slack using Atlassian Intelligence

The "Summarize incident" feature powered by Atlassian Intelligence helps your on-call teams quickly catch up on the latest updates with concise summaries when they join an incident's Slack channel, eliminating the need to scroll through lengthy chat histories. The "Create incident timeline" feature provides a clear, step-by-step record of the incident by integrating key messages from Slack and updates from Jira Service Management, helping your team trace the incident's flow and understand what happened. You can also send selected entries from the generated timeline record back to the incident in Jira Service Management. Read more about summarizing incidents and creating incident timelines in Slack using Atlassian Intelligence.

Manage requests better: New automation rules and the Service Triage Agent

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

Currently, we’ve introduced the following templates:

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

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

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

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

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

Read more about how to connect to Rovo.

Read more about Rovo Agents in automation.

Jira Product Discovery Roadmaps improvement (Premium edition)

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

Enable Free access level in Jira Product Discovery

If your site is on the Free plan, as of November 15th, 2024, everyone with creator product access will be a project admin. The access permission scheme cannot be changed.

Quickly clear your search query

You can now clear your search query by clicking the X in the search bar.

1. Go to + Project settings > Access.
2. Type something in the search field.
3. Select the X to delete the query.

Notify if a global formula field has missing inputs.

If a global formula field uses other global fields as input or if one or more of these fields get removed from the project, a tooltip notifies that the global formula field has missing inputs.

See linked ideas inside the Jira issue view

The new ideas section inside the issue view enables you to see linked ideas and also search and link existing ideas from within an issue.

1. In Jira Product Discovery, select an idea, and on the right-side panel, click Delivery.
2. Create or link an issue to the idea and then go inside the issue view. You can now see a section for ideas.
3. Click the idea to display its details on the right-side panel.
4. In the issue view, click and search existing ideas that you might want to link to the issue.

New informative banner in plans

The banner that shows up when you are in a plan using an idea field.

New permissions for roadmaps

We've introduced roadmaps permissions to add more control to your roadmap audience and editors.

To start adding permissions to your roadmaps: 

1. Select a roadmap and click (...) next to the roadmap name.
2. Click Roadmap settings. A side panel opens up.
3. Click the lock icon and configure the permission level.

More on roadmap permissions

Jira plans are included with Jira Premium

Jira plans are included with Jira Premium and allow you to combine work items from Jira boards, projects, and filters to create an all-encompassing plan that spans multiple teams or your entire organization.

Removing manual automation triggers from page view

We are removing the manual automation trigger (lightning bolt icon) option from the page header.

You can now access manual automation rules from the More menu (three dots icon) in the left sidebar.

1. Select the three dots menu on a content item in the sidebar to open the More menu.
2. Then select Automate. If you have manually triggered rules set up, the Page automations window opens.
3. Select a rule.
4. Select Automate to run the rule.

Create a set of visually appealing cards that update automatically

The new Cards macro now has the option to automatically create dynamic cards that update based on filters.

Deliver the latest news to your team using filters that deliver a customized set of automatically populated cards showing the latest links, text, and images. You can select a label, filter by owners and contributors, choose content in specific spaces or folders, and more.

Dynamic cards are available as an option in the Cards New macro on Company Hub and in pages and blogposts.

Type / and select Cards New from the list of macros.

From the configuration panel on the right side, select Dynamic and then Build dynamic cards.

Select one or more filters from the following options:

• Recent updates
• Label
• Space
• Owner or contributor
• Verified content
• Parent item

Editor: Agents appear next to page contributors

We're introducing a feature that lets you view Rovo Agent avatars in the page controls section of the Confluence Editor. Rovo Agents that you, or your collaborators, use in the AI Command Palette will appear next to the page contributors. This update aims to enhance visibility and collaboration within Confluence.

• Editing: When you select a Rovo Agent in the AI Command Palette, its avatar appears in the page controls toolbar to the left of contibutors' avatars.
• Collaborator awareness: Other collaborators can see the Rovo Agent avatar if someone else uses it.

Mission Control will now suggest improvements

Mission Control will now analyze your content across Confluence and make suggestions that can improve your spaces and content.

The suggested actions will surface automatically based on the release of new features, your percentage of inactive content, guests without space access, and more.

Confluence administrators with a Premium or Enterprise plan can select the administration gear icon (formerly settings) and navigate to Mission Control. If we have suggestions to show you, they will be visible at the top of the page. Take action to solve the issue or explore the new feature. You can also dismiss the message.

Scroll down on Mission Control for more detailed information about these suggestions.

Receive a weekly mention reminder email from Confluence

Users on paid Confluence Cloud instances will receive a weekly email notification summarizing any mentions of them from the previous week that are unaddressed.

By default, everyone will be automatically subscribed to receive this email. Users can also unsubscribe from this email at any time through their email settings.

Creating a Jira issue can now trigger an automation in Confluence

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

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

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

Use templates to create Confluence databases

Use templates to get started easily with Confluence databases. Current templates include product requirements, a content library, and a research repository.

To use a template in a new database, select one from Templates in the setup panel. To use a template in an existing database, open the More menu at the top of the database and select Import & templates.

Confluence adds content types to onboarding

When onboarding into Confluence, you'll be asked whether to start with a page, whiteboard, or a database. This allows you to pick a selection that best meets your needs.

1. Create an Atlassian Account or sign-up for Confluence.

2. You'll be asked: What do you want to create first? This is where you'll see the content types selections.

3. Make a selection based on your team needs and proceed.

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.

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.

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.

A better way to browse, preview, and select page templates is here

From a blank page, page templates can now be previewed with improved clarity and context. Users can also browse all template options, or undo a template selection if need be, with greater ease.

Create Confluence whiteboards directly from your Jira backlog

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

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

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

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

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

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.

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.

Create a new page draft while editing a page with greater speed and simplicity

While editing a page, you can now type /Create Confluence page and instantly create a brand new page with greater simplicity and speed than ever before. Now, this action will automatically generate a new page draft in a new tab and insert a link to that draft within the page you're currently on.

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.

Import Miro boards to Confluence whiteboards

Keep all your work in one place by importing your boards from Miro to editable, native elements in Confluence whiteboards.

Export your Miro boards as vector PDFs and import to Confluence whiteboards for this functionality. Read more about how to do this and what we support.

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.

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.

Validate your rules in Jira and Confluence automation

We're introducing a new feature to Jira and Confluence automation that allows you to check your rule for errors before enabling them. This validation feature will help to improve efficiency and accuracy during rule creation, as you'll no longer need to search for errors yourself before turning on your rule. Please note that some errors may not be identified during the validation process, so keep an eye on the audit log to ensure no more errors occur after the rule runs.

To get started with this change:

1. Navigate to the automation rule builder in Jira or Confluence automation.

2. Create your desired rule.

3. Once you have finished editing your rule, click on the dropdown arrow next to the Turn on rule button.

4. Select Validate rule.

5. We'll advise you if any errors or warnings were found in your rule. Follow the steps provided in the rule builder to fix these.

6. Select Validate rule again to ensure your rule no longer contains any identifiable errors.

7. Once your rule is ready, turn it on.

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.

Updates to Confluence's daily digest

We're excited to roll out new enhancements for our daily digest. In this update, you'll receive a summary of the pages and blogs you've watched and viewed.

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.

Collaborate more easily on whiteboards by following your teammates

Follow your teammates wherever they are on Confluence whiteboards for easier collaboration.

You can follow anyone by clicking their avatar at the top of the whiteboard.

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.

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.

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.

Slack notifications for invited users

We're introducing a new Slack notification to remind invited users to join an instance if they haven't accepted their invitation yet.

This notification will be sent automatically. No action is required for setup.

Helpful ways to find the link to use for your Smart Link

You now have a list of recent links to pick from when creating a new Smart Link and not just from Confluence, from other tools like Google Drive and Microsoft 365. You can also search for the link you want to add by typing in the link field.

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

Nest expands within expands

We've introduced the ability to nest expands within other expands in the editor. This can help you organise the hierarchy of content, improving readability and navigation within documents.

• Nested expands: You can now create nested expands within other expands, allowing for deeper levels of content organization.
• Improved Editor functionality: The editor now supports more complex content structures, making it easier to manage detailed information.

Insert and share anchor links with greater ease and clarity

The anchor link macro (formerly called the "anchor macro") has been updated to look and function more intuitively. Now, it is easier than ever to create a hyperlink to a specific part of a page. Upon inserting an anchor link, you'll be able to quickly select Copy link from the floating toolbar and share that link wherever needed.

Quick calculations in Confluence databases

Calculate sums, averages, min, max, and other insights with quick calculations in Confluence databases.

Right-click on any field, go to Calculate, and select the calculation you want to see. Results appear at the bottom of the database.

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.

Analytics is now easier to use

We’ve redesigned Confluence Analytics across Page, Space, and Site Analytics to improve its look and feel and make it easier to interact with your data.

The following changes apply to Pages, Space, and Site Analytics:

You can now select from a set of preset “time-range” filters such as the last seven days and year-to-date and you can use a drop-down to select grouping by weeks or other timeframes.

You can now select Total views and Unique viewers directly from the chart and make both visible at the same time.

It's now easier to find users, content, or spaces with the new search bar available in all analytics tables.

For page analytics, we've made these changes:

On the Page Analytics Overview, we've added quick access to the most-used metrics with summary cards for views, viewers, and mentions.

You can also send reminders to mentioned teammates who haven’t viewed the page yet—available from both the Views tab and the Mentions tab.

To simplify Page Analytics and reduce clutter, we’ve removed the rarely-used Attachments tab from the Analytics screen.

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.

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.

Enhanced table features in the comments editor

This update brings a new, improved table experience to the comments editor, matching the capabilities of the full-page editor. It ensures consistent and enhanced table functionality across different editor surfaces, reducing cognitive load and preparing for future platform-wide adoption.

• Custom table widths: Adjust table widths to fit your content needs for greater flexibility.
• Drag and drop: Easily reposition tables within the comments editor for a more intuitive editing experience.
• Table alignment: Use new alignment options to better organize and present your data.

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.

Whiteboards voting improvements

Run more flexible voting sessions in Confluence whiteboards with anonymous voting and the ability to mark yourself as done.

You can also delete old voting sessions, and hide votes on the whiteboard as needed.

Summarize changes to a page or blog post

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

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

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

To summarize changes using Atlassian Intelligence:

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

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

Page previews are better than ever before

Premium and Enterprise customers will see a new and improved page preview when they hover over a page title in the content tree. This preview will contain a sampling of three short sentences taken from the page, selected and ranked for relevance by Atlassian Intelligence (AI).

Because this feature uses Atlassian Intelligence (AI), it is only available to customers on the Premium and Enterprise plan. There won't be any change to page previews for Free and Standard customers.

Adding custom fields and compatible values filters to Confluence automation

We're adding two new features to the Smart Values Panel in Confluence automation. The first feature will appear as a tab named Compatible values which can be used to view the smart values that are most compatible with the components in your rule.

We're also adding a Custom fields feature to Confluence automation. This feature will also appear as a tab in the Smart Values Panel, and allow you to see which issue field smart values can be used for any related Jira components in your rule. If your rule contains multiple connections to Jira, all available custom issue fields from these connections will be combined under a single Custom fields tab.

We’ve also made Jira-specific smart values available in Confluence automation, so if you have used a Jira component in your rule, the relevant Jira smart values will be avaliable in the Smart Value Panel.

To get started with this change:

1. Navigate to the automation rulebuilder in Confluence.
2. Create your desired rule.
3. Select any component in your rule that requires you to enter a message, such as the Send email component.
4. Select the { } button to open the Smart Values Panel.
5. Select either the Compatible values or Custom fields tab to view relevant smart values.
6. Copy your desired smart value and paste it into your message.
7. Once you're finished creating and editing your rule, turn it on.
8. Your rule is now ready to go!

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

View recent links from Smart Link hover cards

You can now view relevant documents, pages, and other work items straight from Smart Links.

To view recent links:

1. Hover over an inline Smart Link.
2. Select View recent links.

The modal that opened will show you documents and work items:

• found in the link
• where the link is inserted

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.

Improved Jira creation from a page

We have improved the ability to create a Jira issue from highlighted text on a Confluence page. When you highlight text and begin to create an issue but then navigate away from the highlighted text, we will now warn you that the issue creation process was interrupted.

Version history now available for whiteboards

You can now view and restore previous versions of your whiteboards, giving you greater flexibility and control over your whiteboard content.

To view a whiteboard’s history, open the whiteboard’s ••• menu in the top right and select History.

From there, you can view previous versions of the whiteboard, and if you want to restore one of them, you can create a new whiteboard using that version’s content. Permissions on the new whiteboard will be the same as the original.

Get contextual suggestions with the new Atlassian Intelligence (AI) button in Confluence

We're introducing a new, floating menu for Atlassian Intelligence features, which Premium and Enterprise customers can access from the bottom right of any published page in Confluence. Currently, this new button is where you'll go whenever you want an AI-generated page summary, comments summary, or summary of changes. We'll also add new AI actions to this button going forward.

To make things even better, you no longer have to sort through a long list of AI actions to find the right one. Instead, Atlassian Intelligence will infer the most relevant action from context and suggest it to you. Don't worry, though — if you need something else, just select the AI icon next to the button text to see a list of other AI actions you can take.

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 try out the new AI button:

1. Navigate to a published page or blog post in Confluence Cloud.
2. Select the text next to the Atlassian Intelligence icon to perform the displayed action, or select the icon itself to choose an action from the menu.

Space details now have a modernized look

The space details settings page now has an updated modern look and have been consolidated from two pages down to one.

Space admins can now edit the space name, key, description, and home page with fewer clicks. The list of Admins is now identified with profile pictures instead of full names.

We have also provide localization for dropdown options that were previously untranslated.

To get started with this change:

1. Go to a space.
2. Select Space settings on the side nav.
3. Under the General card, select Settings.

Double-click on a cell to enter edit mode in databases

Double-click on a cell to enter edit mode in Confluence databases for a more controlled editing experience.

Values copied to your clipboard can be pasted directly into the database by selecting a cell and pasting.

Signing up for Confluence from Jira just got easier

If you’re using Jira and don’t have Confluence, you might see a prompt to try it out. If you select this prompt, you will go through a signup flow. Previously, this flow was full-screen and used an older style of Atlassian branding.

The flow has been updated with new branding. It also opens on a smaller popup screen that overlays your Jira screen.

The popup will vary depending on which Confluence plan you’re signing up for.

Creating Jira issues from Confluence is easier than ever with Atlassian Intelligence

Use Atlassian Intelligence (AI) to automatically generate issue summaries and descriptions when you create multiple Jira issues from a Confluence page.

This feature is only available to customers on the Premium and Enterprise plan.

To use Atlassian Intelligence to create Jira issues from Confluence:

1. Select the AI button on the bottom right of the page, then select + Create Jira issues. Confluence will generate a list of issues for you in the right side panel.
2. Hover over an issue and select the pencil icon to review the summary and description for accuracy, make any necessary changes, and add additional information as needed.
3. Select Create to save your changes and create the issue in Jira or Cancel to discard changes.
4. To remove an issue from the list, hover over the issue and select the X.

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.

Add numbered entries to Confluence databases

Add numbered entries to your databases in Confluence for better organization.

Enable Number entries from the Table Layout settings for a view.

Editor: media interaction improvements

We are improving media interactions within editor for a more intuitive workflow and experience.

• Double click to open media viewer: You can now double-click to open the media viewer in both Live Pages (view and edit modes) and the default editor, providing a quicker way to access media content.
• Navigate media within documents: You can now navigate all media within a document, making it easier to manage and review multiple media files when in the media viewer.

Editor: Spotlight for inline comments

We are introducing a spotlight guide to inline comments, if you have not used a comment on inline elements before.

Spotlight on inline elements: When you select content that includes an inline element, a spotlight will appear to provide guidance on where you can now leave comments.

Create Google Docs in your Google Drive with Jira and Confluence automation

We’re introducing a new component to Jira and Confluence automation that allows you to create a Google Doc in your Google Drive by simply executing a rule. This feature will help you to create Google Docs more quickly and easily, as you’ll no longer need to create them manually - Atlassian automation can do it for you!

To get started with this change:

1. Navigate to the automation rule builder in Jira or Confluence.
2. Select a trigger for your rule.
3. Select the Create Doc in Google Drive action and add it to your rule.
4. Select a Google Drive folder for your Google Doc to be placed in. Your Doc will be placed in your My Drive folder if you don't have permission to select a location for it.
5. Add a title and any body content you want your Google Doc to contain.
6. Add any other desired components to your rule.
7. Once you've edited and finalized your rule, turn it on.
8. Your rule is now ready to go.

Clear date and time filters in the automation audit log

We're introducing a new feature to Jira and Confluence automation that allows you to clear all selected filters in the audit log with a click of a button. This change will help you to save time and improve efficiency, as you'll no longer need to manually de-select all the selected filters yourself.

To start using this feature:

• Open the audit log in either Jira or Confluence automation.
• Apply any desired date and time filters to the audit log.
• Once you are done with these filters, select the Date and time button.
• Select Clear filter. All selected date and time filters will automatically be de-selected.
• Your audit log will now have no date and time filters applied to it.

Learn more about using the audit log in Jira and Confluence automation

Find Company Hub settings, analytics, and editor access all in one place

We're introducing a redesigned settings page for Company Hub. This provides a consolidated place for settings, analytics, and managing editor access.

See hub settings from view mode, see recent engagement stats, and view and restore previous versions. You can also add and remove access for users who need to edit the hub.

Hub admins can select Manage Hub from the top of the hub to access the new settings page.

Change the status straight from Smart Link list view

Update the status using a Smart Link list view without the need to open the Jira issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select the status from one of the items. Once the dropdown appears, you can update the status straight from the cell.

Create Jira issues from Confluence using Atlassian Intelligence

We’ve made it easier to create Jira issues from Confluence pages. You can now use Atlassian Intelligence to do it. Just select the relevant text on the page to create a Jira issue from and Atlassian Intelligence will use both the selected text and the surrounding content to generate a helpful Jira issue summary and description.

Note: Your organization needs to have Atlassian Intelligence enabled. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

Better filters for Content Manager

The Content manager now has ten new filters and five new table columns that provide additional options for space admins to better manage their space's content.

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

Change the assignee straight from Smart Link list view

Change the assignee using a Smart Link list without the need to open the issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select assignee from one of the items. Once the dropdown appears, you can change the assignee straight from the cell.

Editor AI: Refine command palette prompts

We're introducing a new feature to the AI command palette in Editor. The Refine button allows you to select follow-up prompts for any AI-generated response, so you can continue to generate AI-prompts within the command palette.

What's new:

• "Refine" button for follow-up prompts: Easily select follow-up actions for AI responses.
• Streamlined interaction: Access additional AI-generated suggestions within the AI command palette.

Change the priority straight from Smart Link list view

Update the priority of Jira issues straight from Smart Link list view.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select the priority from one of the items. Once the dropdown appears, you can update the priority straight from the cell.

Whiteboards improvements

Improvements to Confluence whiteboards include the ability to:

• attach lines to the same shape and snapping lines to shapes to improve precision and complexity in diagrams
• drag sections from their title, smart sections won’t action on every load
• bulk import all Jira issues from a JQL query
• click on the zoom percentage to easily adjust zoom level

Block the download of files attached to pages with extended data export rule

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

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

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

This change will affect any existing policies that have configured the data export rule to block exports. At this stage, it will not block attachment downloads in Jira.

To check whether your data security policies currently block exports:

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

The data export rule requires Atlassian Guard Standard.

Import HTML content into Confluence spaces

You can now seamlessly import your HTML content directly into Confluence spaces using our new importing tool.

To import content from HTML, verify that you first have permission to create a space. Follow these steps:

1. In Confluence, select Spaces from the top navigation, then Import from other tools.
2. Select HTML.
3. Upload your HTML Zipfile.
4. Select Next.

For more information, check out our guide on Importing data from HTML.

Editor: Default image insertion update

We're changing the default behavior for image insertion in the editor to always insert images as blocks rather than inline. This update addresses user feedback and analytics showing a preference for block images, enhancing document layout and usability.

Default block image insertion: Images will now be inserted as blocks by default, improving document structure.

Use third party secret providers in Bitbucket Pipelines

Bitbucket Pipelines is excited to introduce third-party secret integration. This powerful new feature allows you to seamlessly retrieve secrets directly from your preferred secret store. This functionality is now available for Bitbucket Cloud-based runners, and self-hosted runners.

To get started with this feature, you'll need to code your own middleware to let Bitbucket communicate with your third-party secret provider.

Then, you'll need to configure your Bitbucket pipelines to retrieve the appropriate secrets at runtime.

If your pipelines are using a self-hosted runner, you'll also need to point that runner to your middleware.

All of these steps are detailed in our help documentation.

Update to how comments are displayed in your Activity feed

Previously, when you replied to a comment on a pull request, the comment thread was immediately updated to display the most recent comment which caused the comment thread's position in the activity feed to be reordered. This was causing confusion and also making it more difficult for you to find and reply or react to a comment thread.

Now, the comment thread will not move from your display when a user replies to a comment thread on your pull request. The threads will still be ordered by the timestamp of the latest comment, but will not be reordered until you reload or refresh the page.

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.