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

Filter the user list with added roles

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

The roles we’re introducing include:

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

To filter the user list by roles:

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

Brand your Jira products with a custom domain

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

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

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

To create a custom domain:

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

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

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

Option 1: Manually set up user provisioning

Recommended when you need:

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

Learn how to add an identity provider for this option

Option 2: Automatically set up user provisioning

Recommended when you need:

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

Learn more about Azure AD for nested groups

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

Learn more about identity providers

Find Atlassian Administration settings faster

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

To use the Administration search field:

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

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

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

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

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

Create custom domains for your Jira products

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

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

To create a custom domain:

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

Data residency is now supported in six new regions

We're launching data residency in United Kingdom, Japan, India, Brazil, South Korea, and Switzerland to allow you to control where your data is stored.

There are a few limitations with these new locations. Find out more about any limitations

We're adding these locations to the list of supported locations in phases, so expect to see updates in the coming weeks.

To schedule a data residency move for the United Kingdom, Japan, India, Brazil, Switzerland, and South Korea:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data residency.
3. In the data residency table, select Move product.
4. Go to Select location, and select the desired country as the location.

Discover more about data residency

Data residency for Marketplace apps

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

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

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

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

Stay on top of your organization’s security

We improved the security guide so you can see your security setup in one place.

Understand your organization’s mix of users and their login methods at a glance. Then, review your security recommendations to keep your users and data protected.

To go to the security guide:

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

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

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

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

To access this feature:

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

Brand Confluence with a custom domain

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

You can create a custom domain if you have a Confluence Premium plan.

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

To create a custom domain:

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

We’re replacing Jira Software with Jira in CSV exports

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

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

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

It’s now faster to copy data to your sandbox

Save time copying data to your sandbox by choosing only the projects and spaces you need. Understand how to select data to copy

To copy specific Confluence spaces or Jira projects from production to its sandbox:

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

Find out what we copy to the sandbox

Atlassian Access is becoming Atlassian Guard

We are changing the Atlassian Access name to Atlassian Guard. This change reflects the expansion of our security solutions beyond identity and access management.

You’ll see the new name in Atlassian Administration on June 12, 2024. The capabilities you currently have with Atlassian Access remain unchanged.

Explore the future of Atlassian Guard

Improved experience for moving Marketplace apps to another location

Improved experience for app data residency with email notifications for scheduled moves, when moves are in progress, and when they are completed, cancelled, or failed.

To request a data residency move for apps:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data residency.
3. In the data residency table, select View details.
4. Select the Eligible tab.
5. If you have eligible apps, select Move apps.
6. Review information about the steps involved in moving your eligible apps. Select Next.
7. Review the apps. Select Next.
8. Select the 24-hour move window. Select Next.
9. Review your app data residency move details. Select Submit request.

More about moving your apps to another location

Atlassian Access is now Atlassian Guard

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

Explore the future of Atlassian Guard

Prevent people who are not logged in from viewing Jira issues

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

You can now use the anonymous access rule to prevent people who are not logged in from viewing issues in specific projects or across entire Jira product instances. Previously, this was only available for policies that covered classification levels.

The anonymous access 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.

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.

Prevent people from exporting content in specific spaces and projects

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

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export 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.

Prevent people from exporting Jira issues

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

You can now use the data export rule to prevent people exporting issues from entire Jira sites. Previously, this was only available for policies that covered classification levels.

The data export rule requires Atlassian Access (soon to be known as Atlassian Guard Standard)

About data security policies

If you already have a policy that covers Confluence products, you can edit the policy coverage to include Jira product instances.

Alternatively, create a new data security policy:

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

You’ll then be able to configure what product instances your policy will cover and add rules to protect that data.

We’re replacing Beacon with Guard Detect

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

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

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

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

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

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

Copy Jira data from one instance to another in Atlassian Administration

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

To copy Jira data:

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

Enhanced audit log filtering with new product filter

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

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

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

Control usage of Atlassian Analytics with IP allowlisting

To give you more control over your data security, you'll be able to apply IP allowlists to your Atlassian Analytics workspaces so that your users can only access Atlassian Analytics from specific IP addresses.

To apply an allowlist to Atlassian Analytics:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > IP allowlists.
3. Select Create allowlist. A pop-up will appear where you'll enter your allowlist details.
4. For Applies to, select Atlassian Analytics.
5. Select Create.

Read more about IP allowlists.

Track usage of mobile Atlassian apps

We’re giving you the ability to track mobile Atlassian app usage in your organization. App users include bots, managed accounts, and external users. The totals show how many users accessed content from these Atlassian mobile apps.

Confluence
Jira
OpsGenie

To view mobile app usage:

1. Log in to admin.atlassian.com > Security
2. Select Insights.
3. On the Insights page, go to Mobile app usage.

Jira’s dot menu will be removed from August 19

We’ve removing the dot menu in Jira to make way for a new and improved command palette.

The dot menu will be removed across Jira from August 19. For a more seamless experience, users will be able to access the command palette to find work, update their issues, access project and admin settings, and more.

To get started with the command palette:

1. Open the command palette.
   1. If you’re a Mac user, press command + K to open the command palette.
   2. If you’re a Windows user, press Ctrl + K to open the command palette.
2. Search for commands in the search bar or use a forward slash / to search work.

More about the command palette

Why are we removing the dot menu?

Use Confluence templates in pages you create in Jira

When you create a Confluence page from a Jira issue, you now have a choice of templates to add to your page.

From the Jira issue's drop-down menu, select Create and choose Page. We will start a draft and you'll have the option to choose a template from a list on the right side of the page.

Automation: Filter audit log by date and time

Small change to the Automation audit log - we've updated the look and feel of the date picker to make it easier to use.

To check it out:

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

Brand your Jira products with a custom domain

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

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

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

To create a custom domain:

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

Duplicate dashboard gadgets

When you're editing a dashboard, you can now duplicate a gadget and its configuration to appear alongside the original.

To try it out:

1. Open a Jira dashboard that you can edit.
2. Select Edit.
3. Select More actions (...) > Duplicate for the gadget you want to duplicate.

The duplicate gadget will appear at the top of the leftmost column on your dashboard.

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

You can now copy Jira Service Management data between cloud sites from admin.atlassian.com, using the Copy product data feature. In addition, we've added the capability for team-managed projects to be copied.

Read more about what moves when copying product data. Keep an eye on this page to stay up to date on what data is available to copy between cloud sites.

Copying Jira Service Management data now lives in admin.atlassian.com, by selecting Settings, then Data management, then Copy product data.

You need to have organization admin permissions to access and use this feature.

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

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

Resize your columns in the new issue navigator

You can now resize columns in the issue navigator list view. To try it out, go to the issue navigator by selecting Issues in the project sidebar. Alternatively, select Filters in the navigation, then select View all issues.

From the list view, drag the right border of a column to resize it. Alternatively, select the More actions (︙) menu on a table header, then select Resize column.

Additionally, we've updated the appearance of the list view, making it more modern, compact and easy to use.

View parent, team, development and version information as columns

You'll also be able to filter by team, parent and versions.

To view your new fields, scroll the list all the way to the right. You can then organize your fields how you like.

To view your new filters, select Filter at the top right of your list. They will be available in the menu.

Keyboard navigation updates and new fields for Jira list

Edit issues easier and quicker by navigating updates just with your keyboard. We've also added new fields including team, parent, development and versions.

To edit an issue using only a keyboard:

1. To enter a value and move focus to the field on the right, press tab.
2. To enter a value and move focus to the field below, press enter.

Your new fields will be shown in your list automatically. You can remove fields as you usually would.

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.

Collapsible transition labels in the New Workflow Editor

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

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

Other small but mighty changes to the workflow editor include:

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

Read our community post about these changes to learn more.

New global transitions and lozenges in the new workflow editor

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

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

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

Other small but mighty changes to the workflow editor include:

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

Read our community post about these changes to learn more.

Template recommendations in your Projects directory have a new home

When you click on ‘Projects’ in your top navigation in Jira you land in your Projects directory. Previously, recommended templates were listed at the top of this directory.

Now, the templates we recommend sit to the side. You can display and hide them as before; the main difference is that when you hover over any of the templates, you can see a preview of what that template looks like and how it works.

We've also changed the logic behind the recommendations so that they’re more specific and useful.

Bringing Plans and Overviews together!

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

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

Find out how this supercharges your planning experience

Use Atlassian Intelligence to define words and acronyms in the issue description

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

To use Atlassian Intelligence to define words:

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

Definitions are only available in view mode in the description.

Simplifying the Toolchain settings page

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

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

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

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

Improved search using summary and description fields

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

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

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

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

New ways to edit card covers

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

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

Bulk edit issues in Jira list

Bulk edit up to 1000 issues at one time from your Jira list.

To bulk edit multiple issues:

1. Select multiple issues from your list using the issue checkboxes.
2. Once you’ve chosen the issues you’d like to edit, select Edit from the toolbar that appears.
3. A sidebar will open which allows you to make edits for the shared fields across your selected issues.

View even more issue information from your Jira list

View project, groups, cascading select, radio buttons, resolution, and status category information as field columns.

To view your new fields, scroll the list all the way to the right. You can then organize your fields how you like.

Shorter, saveable, downloadable, emailable reports for Assets

We've got a whole bunch of improvements in store for Reports for Assets in this release... Reports are now distinct dashboards, can be saved for ease of access later, can be downloaded, and can even be emailed to you!

Inline create for custom CMP boards

You can now create cards directly on boards with certain custom board filters.

Copy and share a link to your Jira dashboard

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

Create multiple help centers on your site to serve different audiences

Create multiple help centers on your Jira Service Management site and customize each of them for your various teams or audiences. Each help center can feature distinct branding, topics, portals, and announcements to effectively cater to specific user groups.

You need to be a Jira admin to create and manage multiple help centers.

To create a new help center:

1. Go to Settings > Products > Jira Service Management > Configuration.
2. In the Help center section, select View all help centers.
3. You’ll be taken to the help center management page. Select Create help center.
4. Enter a name and URL slug for your new help center and select Create.

We've also moved all the help center settings to a single place. Select your avatar from any help center on your site and you can find your requests, profile settings, and customization capabilities in the menu.

Group notifications in one email

Choose when you want to get notified about issue activity and we’ll group your notifications into one email.

We’ll group notifications for the same issue into one email. You can then choose how often you want to receive notification emails for an issue.

To group notifications together:

1. Select Settings > Personal settings.
2. Select Projects and issues.
3. Turn on the toggle to the right of Group notification emails together.
4. Use the dropdown menu to choose how often you want to receive emails.

Inline create for boards with query swimlanes in company-managed projects

You can now create cards directly on boards with certain swimlanes configured with JQL.

This announcement marks our fifth iteration of inline card creation for boards in company-managed projects.

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

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

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

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

Improve the clarity of issue descriptions with AI

Use Atlassian Intelligence to add clarity to your issue descriptions. Quickly improve your descriptions with clear structure and headings so they’re easier to read.

To get started, while you’re writing an issue description:

1. Type / in the issue description field, or select the Atlassian Intelligence button.
2. Type or select Add structure.

Using AI, we’ll generate a new, structured issue description for you to review. Look over the new description, and choose to replace your existing description or add the new one underneath.

View and schedule project work in a calendar

View all your project’s work in a calendar to track your team’s progress toward due dates and deadlines. While planning upcoming work for your team, use the calendar to view releases and sprints and to schedule issues.

How to schedule and track work in the calendar

Jira’s calendar view is enabled by default on all software projects. To view your calendar, navigate to your project, then select Calendar from the sidebar.

Move data between sites with cloud-to-cloud migration

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

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

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

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

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

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

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

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

Plan the next quarter of work with the Program Increment Planning Board

Plans now has an interface to help you plan the next quarter of work.

Introducing the Program board – a new way for planners to coordinate and align the delivery plans of multiple teams at the team-of-teams level.

Check out our community post.

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

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

To connect pending Bitbucket workspaces on the Code page:

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

To connect pending Bitbucket workspaces using the development dialog:

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

Read more about integrating Bitbucket with Jira

Use filters to search and display Jira issues

Now you can use filters to search for Jira issues and display them in a list, without leaving the Confluence page.

This improvement follows the release that allows you to search for issues using keywords or JQL, and flexibility to add, remove, and reorder fields.

How to display Jira issues in a list

Start using filters to search for Jira issues:

1. Edit a Jira description or comment.
2. Type /jira and select Jira issues.
3. With Basic selected, use the filters to search by Project, Type, Status, or Assignee.
4. Select Insert issues.

This will display your selected issues in a list format you can interact with.

To edit your list of Jira issues:

1. Select anywhere on the list.
2. Select the Edit button (left-most icon) from the menu that appears at the bottom of the table.
3. Edit your search query using Basic or JQL.
4. Select Insert issues.

Move a mighty amount of issues from a completed sprint

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

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

Colourful categories

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

Manage custom fields for your project in context of the list view

You can now create and manage custom fields in context of the list view.

Certain types of work may require specific information for your team to get the job done. Jira now allows you to create and manage these additional fields in context of the list view to save you from navigating away from your work.

This will help your team with viewing the right, relevant information upfront when completing tasks.

To get started with the change, select the plus symbol at the top right of your list view to show or hide more fields, and manage your custom fields.

Track and triage incidents affecting your services in Jira

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

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

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

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

To get started with the incidents feature:

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

To turn it on manually:

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

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

Finish setting up your development tools from the issue view

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

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

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

To get started:

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

Filter results dashboard gadget improvements

The gadget now displays issues in the same way as they appear in the issue navigator. When you configure the gadget, changing the displayed columns and their ordering also works the same as in the issue navigator.

Take a look at the improvements by adding a new Filter results gadget to one of your Jira dashboards.

Hide unused fields when creating issues

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

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

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

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

Get suggestions for child issues from AI

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

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

To see a list of AI-generated suggestions:

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

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

Template bundles in the project create page

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

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

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

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

Another way to create a bundle is to:

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

Use Atlassian Intelligence to define words in the issue description

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

To use Atlassian Intelligence to define words:

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

Definitions are only available in the description in view mode.

See how your issues relate to each other in the timeline

We’ve made it easier to see the relationship between parent and child issues in your business project's timeline.

These changes are being rolled out, so don’t worry if you can’t see them yet - they’ll be there soon! This is only available for Jira business projects.

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

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

To create a child issue from the timeline view:

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

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

Maximum cardinality limit on multi-value attributes in Assets

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

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

For this reason, we're introducing a maximum cardinality limit of 20,000 per object type attribute for Assets. Read more about recommended data structures for Assets.

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

Customize your navigation

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

Project admins can customize the following in their business project:

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

Find out more about customizing the navigation in your business project

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

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

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

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

Find your attachments even faster

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

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

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

You can filter attachments by:

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

More about using filters to find attachments

The team field in Jira issues now shows the team icon

Previously, selecting the team field in an issue would prompt a search displaying the singular "Person" icon. The correct "Team" icon now shows to indicate what should be selected for the field.

Drag and drop to reparent issues

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

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

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

Jira: Import from ClickUp

Moving your work from ClickUp to Jira just got easier. Using the ClickUp importer, you can directly import projects into Jira.

Save the effort of manually moving data and ensure the project information is relevant and accurate.

To directly import your data using the ClickUp importer:

1. From the navigation bar, select Projects > Create project.
2. From the sidebar, go to More > select Import data.
3. Select Import to a new business project.
4. In the import from an app section, select ClickUp.

View project work in a single list

View all your project's work in a single list that can be quickly scanned and sorted by field. Jira's list view can also be used to create, edit, and view issues in your project.

The list view is enabled by default in all projects. To view your project list, navigate to your project then select List from the sidebar in the Planning section.

Find out more about how to manage and update work in the list view.

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

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

Improved Jira import support

We’ve expanded import support to Airtable, Azure DevOps, GitLab, GitHub, Linear, Notion, Smartsheet, YouTrack, and Wrike. Admins can download the CSV file from these apps, upload it to Jira, and import their data into a Jira business or software project with just a few clicks.

To import from these apps:

• Select Projects > Create project.
• From the sidebar, go to More > select Import data.
• Select the app you’d like to import from and follow the directions.

Read about importing data into Jira

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

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

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

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

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

Jira plans, warning filter update

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

Prevent people from exporting content in specific spaces and projects

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

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export 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.

Moving data from Asana to Jira just got easier

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

To directly import your data using the Asana importer:

1. From the navigation bar, select Projects > Create project.
2. From the sidebar, go to More > select Import data.
3. Select Import to a new software project.
4. In the import from an app section, select Asana.

Read more about the Asana importer

Easily control the visibility of work suggestions in Jira

We're adding a "Turn off work suggestions" link to the Work suggestions panel footer to let you easily find the Work suggestions toggle under the View settings menu. When you turn the toggle off, you'll no longer get any suggestions, and the work suggestions panel won't open when you select your avatar on the Jira board.

You can always turn Work suggestions on at any time from the View settings menu to start getting suggestions again.

Read more about Jira work suggestions

Product admin support for Jira imports

Along with organization admins, product admins can also use Jira’s new import experience to quickly and seamlessly import data into new business or software projects with just a few clicks.

To import data into Jira:

1. Select Projects from the navigation bar > Create project.
2. From the sidebar, go to More > select Import data and follow the instructions.

Read about the new import experience

The new global issue create experience is enabled for all instances

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

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

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

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

Learn more about the GitHub for Jira app.

Control what you see in your products

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

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

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

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

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

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

To set up SAML SSO for portal-only customers:

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

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

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

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

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

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

Use filters to search and display Jira issues

Now you can use filters to search for Jira issues and display them in a list, without leaving the Confluence page.

This improvement follows the release that allows you to search for issues using keywords or JQL, and flexibility to add, remove, and reorder fields.

How to display Jira issues in a list

Start using filters to search for Jira issues:

1. Edit a Jira description or comment.
2. Type /jira and select Jira issues.
3. With Basic selected, use the filters to search by Project, Type, Status, or Assignee.
4. Select Insert issues.

This will display your selected issues in a list format you can interact with.

To edit your list of Jira issues:

1. Select anywhere on the list.
2. Select the Edit button (left-most icon) from the menu that appears at the bottom of the table.
3. Edit your search query using Basic or JQL.
4. Select Insert issues.

Filter results dashboard gadget improvements

The gadget now displays issues in the same way as they appear in the issue navigator. When you configure the gadget, changing the displayed columns and their ordering also works the same as in the issue navigator.

Take a look at the improvements by adding a new Filter results gadget to one of your Jira dashboards.

Hide unused fields when creating issues

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

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

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

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

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

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

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

Find out more in our Community blog

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

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

To set up emoji rules in automation:

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

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

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

Use Atlassian Intelligence to define words in the issue description

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

To use Atlassian Intelligence to define words:

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

Definitions are only available in the description in view mode.

Maximum cardinality limit on multi-value attributes in Assets

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

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

For this reason, we're introducing a maximum cardinality limit of 20,000 per object type attribute for Assets. Read more about recommended data structures for Assets.

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

Data limits for object schemas in Assets

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

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

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

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

Beta: Group alerts using Atlassian Intelligence

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

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

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

Read more about alert grouping

The team field in Jira issues now shows the team icon

Previously, selecting the team field in an issue would prompt a search displaying the singular "Person" icon. The correct "Team" icon now shows to indicate what should be selected for the field.

Jira: Import from ClickUp

Moving your work from ClickUp to Jira just got easier. Using the ClickUp importer, you can directly import projects into Jira.

Save the effort of manually moving data and ensure the project information is relevant and accurate.

To directly import your data using the ClickUp importer:

1. From the navigation bar, select Projects > Create project.
2. From the sidebar, go to More > select Import data.
3. Select Import to a new business project.
4. In the import from an app section, select ClickUp.

Blank request type creation: updated details screen

We've introduced a new screen for editing details when creating a new blank request type in Jira Service Management.

Previously if you selected Create request type, then Create blank, you saw a modal and followed a two-step process to update the request type's name, description, icon, issue type, and portal group(s).

We've replaced this with a screen that allows you to easily review and update the same information in a single view, alongside a preview of the request form.

To see what's changed:

• From your service project, go to Project settings, then Request types.
• Select Create request type, then Create blank.
• On the left of the screen, you'll have the option to edit the name, description and icon for the new request type. You'll also be able to select an issue type, and select (or create) the portal group(s) where you want the request form to appear.
• On the right of the screen, you'll see a preview of the form for the new request type. The blank request type will only contain a single Summary field as a placeholder so you can later customize the request form to meet your requirements.

If you choose to create a new request type by selecting Create request type, then Create from template, you'll use this same screen to review and update the request type's details.

Update the request types of issues using Atlassian Intelligence

We've released a new feature powered by Atlassian Intelligence that updates the request types for multiple issues at once. This is particularly useful when you receive requests by email and end up with a lot of issues with the Emailed request request type. By using the Atlassian Intelligence triage feature, you can easily update these issues to have more appropriate request types.

To update the request types of issues with Atlassian Intelligence:

1. Select issues in your queue.
2. Select Triage.
3. Review the suggestions and select the issues you want to update.
4. Select Apply.

Internal note visibility restrictions for Jira Service Management

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

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

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

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

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

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

Calendar view for new Jira Service Management projects

We’re excited to launch a new view of issues in Jira Service Management: calendar view! Like the board or your queues, the calendar is another way to view and manage your work in the way that works best for you and your team.

It’s a great way for team members to plan, track, and prioritize, and for team leads to see potential roadblocks before they cause delays. Read more about using the calendar to view your issues.

Create a new project, then select Calendar in your project navigation to check it out. You can schedule issues in the calendar by adding and filling out the Start date and Due date fields on an issue. Once those fields are filled, the issues will appear on your calendar so that you can view your work across the coming month and beyond.

At the moment, the calendar is only available in new Jira Service Management projects, but it will become available for your existing projects soon, alongside new and improved calendar features to help you and your team do their best work.

Minor UI updates to AI issue triage

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

Attach a form directly from the request type configuration page

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

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

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

Read more about adding forms to request types

Update the request type when moving issues

When you move or bulk move issues to different projects or issue types (or migrate an issue type out of a project), you can now select the new request type during the move. We're excited to release this much-requested update to make issue migration simpler in Jira Service Management.

Restrict request types in both company and team-managed service projects

You may have request types in your service project that only specific people should be able to raise. Now you can control who can and can't raise these requests in Jira Service Management in both company and team-managed service projects!

Give access to specific people and groups, and automatically restrict access to all others. If someone doesn’t have access to a request type, they won’t be able to raise that request as it won’t show up as an available option to them - even via search.

Read more about restricting request types

Create ideas for a group in the list view

Add new ideas to a group in your list views more easily with a new '+' button alongside each group in the list view. When you select Group by on a list, this new button appears, making it easy to add new ideas to specific groups.

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

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

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

Learn more about the GitHub for Jira app.

New granularity level for the timeline

We've increased the granularity displayed in the timeline to improve the overall experience.

Whether you have chosen quarters or months for your timeline, you can now resize cards between months and half months.

New summary layout in your timeline

In your timeline, you can now change the card layout to a summarized one. In this layout, you can only display one field.

1. In the timeline view, select the layout changer icon and click Summary.
2. Hover over the card to see all the details.
3. To select the field that will be shown in the summary layout, go to Fields, hover over a field, and select the star icon.

Remember you can display only one field in the summary card mode.

We've introduced time markers for your timeline.

You can now mark a specific date in your timeline.

In your discovery project, go to a timeline and click anywhere in the time header. The blue dot that appears marks a specific milestone. You can add a name, date, and even a color.

You can drag and drop a time mark, change the date, and create multiple markers.

Remember that these markers only apply to the timeline where you create them.

Update to system fields

Project admins can now hide system fields that aren’t in use in their Jira Product Discovery projects.

To hide system fields:

1. Go to Project settings > Fields.
2. Pick a system field of your choice and select the cog icon.
3. Select the eye icon to hide.

Track Atlas goals and projects along the discovery phase

With the new integration with Atlas, you can track Atlas goals and projects alongside every aspect of the discovery phase.

To get started with this change:

• You need to have an active Jira Product Discovery license.
• You can only connect to Atlas sites within the same organization as the current Jira Product Discovery site.
• You need to have at least one project in Jira Product Discovery.
• As explained below, you have to connect to Atlas via Jira Product Discovery.
• If you don’t have product access to Atlas on a site, you won’t see the site name in the integration menu.

New view permissions scheme to further restrict a view

View permissionss allow you to further restrict project permissions by giving project members view-only and edit access to JPD views. This allows JPD users to stage their conversations with the right audience at the right time.

Edit the access by selecting the lock icon next to Publish.

Learn about product and project access in our documentation

New decimal number support for number fields

You can now format number fields using decimal numbers for more flexible formatting options. This will allow you to have more flexible options for applying background colors to fields.

New filtering capability on columns in list view

In the list view, use the new filter option when you select a column to further filter the results shown in that column. This opens the filter panel so you can further drill down into the information for any particular column in the list view.

Automation: Filter audit log by date and time

Small change to the Automation audit log - we've updated the look and feel of the date picker to make it easier to use.

To check it out:

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

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.

Automation: Project created trigger

One for the Confluence automation fans! You can now trigger Confluence automation rules when a Jira project is created.

For example, you could create a rule where every time a Jira project is created, Confluence creates a corresponding space and pages.

To give this a try:

1. Navigate to Confluence automation
   • For space automation, go to Space settings > Automation
   • For global automation, go to Confluence administration > Automation
2. When creating or modifying a rule, select Project created in Jira as the trigger.

Admin settings for Confluence in Jira

Admins can now control the ability to create Confluence content in Jira.

We're adding settings to turn on and turn off options to create pages and whiteboards for sprint retrospectives, from the dropdown menu in issues, and from an issue's Confluence content section.

To use these settings, admins can select the wheel icon and find the Confluence page under the left menu bar's Integrations section.

Automatically get a personal space

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

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

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

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

Learn more about personal spaces

Transfer of page ownership between users

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

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

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

Learn more about page ownership and how it can be transferred

Control what you see in your products

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

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

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

Template suggestions in the page editor

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

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

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

Home has a new look

Jump into work with Confluence Home, now with an improved look and feel. This visual refresh includes layout and iconography updates.

Visit Home to see these changes.

Use Confluence databases to organize and connect work

Confluence databases will be generally available to everyone over the coming weeks. Use databases to structure, connect, and manage your work.

Organize information with structured fields, connect your work with real-time syncing across databases and pages, and visualize information using layouts and custom views.

Explore what's possible with Confluence databases and see how to get started.

Stay more informed about unread comments than ever before

We've added a small blue dot to the comments icon on the toolbar whenever there are unread comments. Thanks to this dot, it's now easier than ever to know if you have unread comments to address.

By selecting the icon when the blue dot is present, you'll be able to navigate through your unread comments as the topmost items in the comments panel.

Restore and reattach inline comments, even after deleting highlighted text

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

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

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

Configure and display labeled content with clarity and ease

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

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

Collaborate and turn ideas into action with Confluence whiteboards

Confluence whiteboards will be generally available to everyone over the coming weeks. Use whiteboards to collaborate and turn ideas into action, faster than ever before.

Whiteboards are great for collaborative activities, such as brainstorming ideas, running retrospectives, planning out and breaking down work for your team, prioritizing what’s coming next, creating diagrams and flowcharts, and more.

Take advantage of integrations with products like Jira. You’ll be able to turn sticky notes into Jira issues and create relationships between issues.

Compare plans and explore what’s possible with whiteboards.

Manage space access in bulk

Admins can now save a bunch of time and repetitive tasks by adding a single user or group to all spaces on a site (or remove them from all spaces) in one bulk action.

This can be done for literally all spaces on the site, for all spaces except personal spaces, or exclusively for all personal spaces.

Catch up quickly with page comments summary

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

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

Introducing content generation with richer context

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

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

Admins can now create automation rules for public links

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

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

Automatically build automation rules for public links

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

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

Request access to a space

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

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

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

Automatically build automation rules to assign guest users to a space

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

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

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

Confluence Page Verification

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

Improved collaboration with image and video comments

You can now add comments to images and videos in Confluence Cloud, making collaboration and adding context a breeze. ️

This update lets you add comments directly to images and videos on your pages. When viewing a page, hover over or focus on an image, and a new comment button will appear. While editing, select the image and use the new comment button in the toolbar.

Like text comments, you can easily add your thoughts and discussions. When a comment is added, a handy icon will appear in the corner of the image, letting you know there's a discussion brewing.

Just a heads up: Inline images can't be commented on yet, and each image or video can only have one comment thread.

Set the default space for new guests

Admins will now be able to choose a default space for all future guests directly from the Assign guest to a space interface. When assigning a guest to a space, admins will now see a checkbox that lets them use that space as the default space for guests.

Confluence admins navigate to Settings (wheel icon) and select Global Permissions.

1. Select the Guests tab.
2. Select one or more guests and select + Assign Space.
3. Select a space and then check the box next to Set as default space for guests.
4. Select Assign.

Get a direct path to the default space for guests

Admins will now be able to access the default guest space settings in Global permissions directly from the guest request access email. We’ve made it easier for admins to understand the benefits of setting a default space for guest accounts.

Emails sent to admins when a guest requests access will now include a link that takes the admin directly to the relevant settings page. The same link will also appear in the weekly summary of all guest accounts without space access.

Configure Confluence Cloud to send emails on behalf of your domain

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

Comment on whiteboards for further collaboration

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

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

Introducing Spaces report: Empower your space management

Unlock comprehensive space management with our new Spaces report feature. Export detailed CSV reports on space activity, creation, and more directly from Confluence. This feature is ideal for admins seeking insights into space usage, activity, and storage.

Key changes:

• Exportable CSV reports for product admins, detailing each space's key metrics.

• Reports include space key, name, type, status, creation date, last activity, and storage used.

• New Spaces report page under Data management for easy access and report management.

• Supports organization, site, and product admins across Standard, Premium, and Enterprise plans.

This feature also provides essential space management data previously unavailable in Confluence. It aids in identifying inactive spaces, managing storage, and enhancing external collaboration, significantly improving admin efficiency and decision-making.

Recommendation emails

What's new or different?

Introducing recommendation emails—a weekly list of recommended and popular content, relevant to the spaces that each Confluence user has access to.

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.

Prevent people from exporting content in specific spaces and projects

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

You can now use the data export rule to prevent people exporting content from particularly sensitive Confluence spaces and Jira projects. Previously, this was only available for policies that covered entire workspaces or classification levels).

The data export 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.

Introducing text highlighting

We are thrilled to announce the addition of text highlighting to our editor, a highly requested feature that enhances your content creation and collaboration experience. This new functionality allows you to easily highlight text, making important information stand out.

The ability to highlight text is easily accessed from the main editing toolbar, located right beside the text color option. Six highlight colors are available: grey, teal, lime, orange, magenta, and purple.

Highlighting can only be done by individuals with editing privileges for a page, unlike comments.

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

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

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

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

Embed your Jira dashboards in Confluence

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

Profile cards show in edit mode

Selecting an @mention while editing will now show the person's profile card.

Search directly from the content tree

Now you can filter items in the content tree by title, making it faster and easier to find what you're looking for.

Just select the magnifying glass below the Content header and start entering a keyword from the item's title.

Effortless content arrangement with drag-and-drop

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

What's new:

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

Fixed column widths for tables

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

How to use:

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

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

Cache key support for self-hosted runners

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

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.

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 your data, 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.