• Atlassian Administration
• Jira platform
• Jira Software
• Jira Service Management
• Jira Work Management
• Jira Product Discovery
• Confluence
• Bitbucket
• 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

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

Control whether members use API tokens to authenticate

You can now control whether members can make API calls with a User API token into your organization’s products.

With this new API token setting, you can allow or block members from:

• Creating a new User API token to authenticate
• Using an existing User API token to authenticate

To try out the API token setting:

1. Log in to admin.atlassian.com.
2. Select an organization if you have more than one.
3. Select Security from the global navigation.
4. Select Authentication policies from the sidebar.
5. Select Settings.
6. Select User API tokens.

Keep track of activities for data security policies in the audit log

We’re now tracking activities for data security policies in the audit log.

Use the audit log to see key activities, like when a data security policy is created, activated, deactivated, and deleted. You can also see when rules have been added and removed from a data security policy.

We’ll be introducing new activities in the future to give you even more visibility over your data security policies.

Learn more about tracking activities from the audit log

To see audit log activities for all data security policies:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select the More actions icon (•••).
4. Select View audit log.

The audit log will show all tracked activities for every data security policy in your organization.

To see audit log activities for a particular 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 the policy.
4. Select the More actions icon (•••).
5. Select View audit log.

The audit log will show all tracked activities for your selected data security policy.

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.

Control third-party keyboards on mobile devices

You can now block third-party software keyboards on iOS devices. This prevents potential data leakage or unauthorized access to your organization’s Atlassian product data.

You can select block third-party keyboard on iOS from your mobile app policy.

To block third party keyboard on iOS:

1. Log in to admin.atlassian.com > Security
2. Select > Create Mobile app policy.
3. Select edit Mobile app policy.
4. Select block third-party keyboard on iOS.

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.

Get fresh insights about your organization

You can now manually refresh your organization’s insight charts. Additionally, we’ve added timestamps under each chart.

If you don’t refresh your charts, they’ll automatically refresh every 24 hours. Tell me more about organizational insights

To manually refresh a chart:

1. Go to admin.atlassian.com. Select your organization if you have one.
2. Select Security > Insights.
3. From a chart, select the refresh button at the bottom left.

Gain security insight with more charts

Get more insight into your users with four new charts. These charts allow you to see managed accounts and external users that have access to your organization, your products, and their security practices.

The new charts include domains with access to your products, users with access to your products, two-step verification for external users, and external user policy.

To access new charts:

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

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

Export accounts from domains faster

You can now directly export a list of all members in your domain to a CSV file from the Actions column. Previously you could only export accounts through Claim accounts.

When you download your CSV file, you’ll also be able to view if another organization has claimed the accounts or not.
How to export accounts from domains

To export accounts:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > Domains.
3. Select Export accounts from the Actions column.
4. Select Export from the confirmation screen to get the CSV emailed to you.

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.

JWM Clickup Importer

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

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.

See all of your virtual agent conversations in one place

Access a log of all virtual agent conversations using the new Conversations page!

To check it out, go to Virtual agent and then select Conversations from the navigation on the left. Use filters to narrow down conversations by things like customer satisfaction (CSAT) score, whether or not an intent was matched, whether or not a conversation was resolved or escalated – and more.

Open a conversation in Slack to get more insight into the virtual agent's performance, and jump straight to matched intents from the Conversations page to make improvements on the fly.

Read more about how you can use conversation data to improve your virtual agent's performance.

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 surfaces the fields you actually use. We’ll create a personalised 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 scrolling down to the Jira labs section. From there, you can use the toggle to opt in and out of the feature.

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.

Searching for issues just got faster in Jira Cloud

We’ve modernized, optimized, and redesigned the way you search for issues. With features like smart syntax highlighting and enhanced autocomplete, the new JQL editor lets you build powerful queries for accurate search results. Configure and reorder columns to see what’s most important to you. Explore the new issue search in Jira Cloud

Add status while creating an issue

You can now select the status of an issue while you're creating it. For example, you could make an issue with the "in progress" status.

When selecting the status of an issue while creating it, you'll only be able to select statuses that don't have screens, actions, rules, validations or conditions in your workflow.

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.

Update to the create issue mini window

We've updated the look and feel of the create issue mini window.

Next time you're creating an issue, you can use the icons on the top right of your issue to exit full screen and use the re-designed mini window. You can also click the background outside the issue you're creating to exit the full screen view.

With the mini window, you'll be able to create work in context and navigate your project without losing progress on your new issue.

Developers can now quickly determine what to work on next with automated suggestions

When you're in the middle of a sprint and you finish a task, it can be hard to know exactly what to do next. Automated suggestions from connected tools are specifically chosen for you based on work on your board. This will help you decide which tasks to do next and keep momentum. This is an alpha release available in team-managed projects.

1. Go to your Jira board and select your avatar.
2. What to work on panel will slide open with your customized suggestions. Hover over any of the suggestions to see tooltips with more information.
3. Select the call to action if you want to work on the suggestion.

Get better results by refining your search with more criteria

We’ve added support to fields like description, environment, epic name, Atlas goal, Atlas project, time in status CHART, and custom fields of the type paragraph, short text, and read-only. Additionally, we’ve added support to configure all fields as columns in the List view.

To get started with this change:

1. Go to your project's sidebar.
2. Select Issues.
3. Select More+ to use these fields.

Customize priorities for your projects

As a Jira admin, you can configure priorities that work best for projects so that your team can select the right priority for their issues. Learn more about priority schemes.

Custom navigation colors are now compatible with dark theme

If you've set a bright custom color for your navigation bar, we'll automatically modify it for anyone in your site using dark theme.

Work more securely with your collaborators in Jira Cloud

Keeping privacy and security in mind, the Browse projects permission lets users in a project see a list of recommended users for fields like mentions, reporter, watchers, custom user field, custom multi-user field, custom people fields, and approvers. Learn more about restricting global permissions to users and groups

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.

Issues and comments created from an unknown email will now use Default Reporter

Our Jira Incoming Emails component has had an update. When an email is received from an unknown email address, and the sender isn’t a Jira user, a new user will no longer be created. The person you selected in your settings as the Default Reporter will be used instead when creating an issue or comment from an email.

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.

Create a Confluence page while viewing a Jira issue

You can now create a new Confluence page while viewing a Jira issue.

People licensed on both Jira and Confluence have two ways to create a page. Access the Create menu dropdown either below the issue's title or in the Confluence content section.

The page you create will be linked to your issue, making it easier to work together.

Anyone with Confluence and Jira will see the new Create options on every issue. Add Confluence and connect it to Jira to activate this feature.

It’s easier to access Jira Product Discovery projects

People who do not have Jira Product Discovery but use Jira Software, Jira Work Management, and Jira Service Management will now see a recommendation for Jira Product Discovery in their ‘Projects’ menu.

They can access it when they click on ‘Projects’ in their menu. If they select the Jira Product Discovery recommendation they will proceed to sign up for a Free or Standard plan and create a new Jira Product Discovery project.

Only people with permission to create a project will see it, on any plan type (Free, Standard, Premium or Enterprise) and it can be dismissed or removed at any time. You can completely disable these types of recommendations at any time from admin.atlassian.com.

View and add apps to roles within Assets

A new column in the roles table within Assets now gives you the ability to view, add, or remove apps.

Apps have similar permissions as those granted to Users. Assets data-import apps will be added automatically to the object schema manager role when a new import is created for that app and schema. You can also add or remove it manually after you install the app.

We've also added some extra descriptors to the page to help explain how roles work within Assets in Jira Service Management, and separated each role into its own table for ease of visibility and use.

Editing your issues in issue navigator just got easier

Directly edit summary, labels, and due date fields in the issue navigator without the hassle of going into each issue.

To edit these fields:

1. Select Issues on the project sidebar.
2. In list view, select a summary, due date, or labels field and make changes.

Finish setting up your tools from the issue view

Jira site admins can now finish setting up code, deployment, and security tools by following a link from the issue view. If a 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.

To get started:

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

New ways to manage email notifications from Jira

We've moved notification preferences out of your Personal settings page into its own Notifications space where we can continually develop ways for you to take control of your Jira notifications.

We've also replaced the old notification configurations with 10 notification preference options, so you have even more control of what notifications you actually want to receive.

To see the change:
Select your profile and settings icon, then select Notifications.

New and improved reports

We've made your reports look better. They also have better performance and versatility in visualization of data.

Use Atlassian Intelligent 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.

Access designs from the release page in Jira

Designs linked to Jira issues within a version can now be found on the release page, giving your team live updates and greater visibility of their design work. Read more about linking designs to Jira issues

Filter issues by work category

We've added a new field to the issue navigator so you can filter issues by work category.

To use this new filter, from the issue navigator, select More, then Work category in the dropdown.

New "Entitlements" field

We've added a new custom field to go with the new Products and entitlements feature in Jira Service Management. The field allows agents to view customers' entitlements in their project to get additional context when working on issues.

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.

Updates to how you insert canned responses

We’ve now made it easier to insert canned responses. You can select Enter or double-click to easily insert the chosen response into the comment box.

Read more about inserting a canned response

Object schema limits for Assets in Jira Service Management

As part of ongoing work to improve performance and reliability, we have introduced a maximum limit of 100 object schemas for each individual Assets in Jira Service Management site. Read more about how much data you can store in Assets.

Receive notifications when you make changes to issues in Jira

We're bringing back the functionality that allows people to be notified about their own changes to issues in Jira.

From your profile avatar, select Notifications. Use the the toggle that allows you to Receive emails when you make changes to issues. Toggle it on to allow this type of email notification, or toggle it off to prevent this type of email notification.

Plans in Jira - Introducing the Calendar view!

View work in your plan on a calendar instead of a timeline.

As of right now, the calendar view is read-only, but you can add filters to show the work items you want to see.

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.

New Parent field in company-managed projects

We're improving the way you associate epics with your bugs, stories and tasks in Jira by replacing the existing Epic link and Parent link fields in company-managed projects with the Parent field, consistent with team-managed projects. Read more about these changes on the Community

With this release, we've introducing the following changes:
• the Parent field is now available when creating new schemes and layouts
• the existing Epic link and Parent link fields have been replaced with the Parent field in the issue view, and when creating new issues and workflow transitions
• the Add parent feature seen in team-managed projects has now been added to the company-managed issue view
• the parent JQL function now includes the functionality of the epic link, parent link and parentEpic functions

Advanced Roadmaps - New navigation

Advanced Roadmaps has a new look that makes it look and feel more like the rest of Jira Software.

To state it simply, the nav now lives on the left-hand side. This new layout opens Advanced Roadmaps up to a whole new world of designs and new features (whoops, not sure if I was supposed to say that 🤭).

Even though this is rollout to all users, we'd still love to hear your thoughts about how it effects your work, or your ideas for improvements. Use the Give feedback button which is still located in the upper right of your screen.

If you opted in the Early Access Program from last month, you won't notice a change. However, this layout is now the new default view for Advanced Roadmaps and can no longer be disabled.

Read more about these changes in our community post.

Connect your tools while creating a new project

We’ve updated the way you connect code and documentation tools when starting a new scrum or kanban project in Jira Software.

Depending on which tools are already connected to your site, you can quickly connect your team’s code repositories, security containers, and Confluence spaces.

To get started:

1. From the top menu, go to Projects > Create project.
2. Choose a project template, a project type, and enter a name and key for your new project.
3. From the the Connect your tools screen, connect your code repositories, security containers, and Confluence spaces.

You’ll see this screen and be able to connect your work if you have one of these tools connected to your site:

• Bitbucket
• GitHub
• Confluence
• Snyk
• JFrog
• Mend
• Lacework
• Stackhawk

Connect Google Drive in Project Pages

Project pages previously only connected to Confluence. Users can now connect and view Google Drive files from within Jira

Any updates made to Google Drive files within Jira are automatically synced, ensuring that all team members are working with the most up-to-date information.

The integration provides an option to search for and link existing Google Drive files to Jira issues, making it simple to associate relevant files with specific tasks.

To get started with connecting Google Drive to Jira Software:

If you’ve never used project pages before:

1. Select Connect Google Drive
2. Select sign in with Google
3. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
4. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project
5. Select connect shared drive

If you have Confluence connected to project pages:

1. Select the Add Google Drive tab
2. Select Connect Google Drive
3. Select sign in with Google
4. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
5. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project.
6. Select connect shared drive.

That’s it! Once you’ve connected a shared Google Drive to Jira, it will be synced to your Jira project.

Organize and track work against Compass software components

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

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

Learn more about Compass components

Switch to Compass components (project admins)

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

Read the full documentation

Link issues to Compass components

If you don't have Compass yet:

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

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

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

If you have Compass, and have software components:

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

Read the full documentation

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

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

To connect pending Bitbucket workspaces on the Code page:

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

To connect pending Bitbucket workspaces using the development dialog:

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

Read more about integrating Bitbucket with Jira

Move a mighty amount of issues from a completed sprint

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

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

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.

Move plans to trash instead of deleting them

When you delete a plan, it's now held in the trash for 60 days before being permanently deleted.

This differs from before when planners would select Delete, confirm their decision, and the plan would disappear like Andy Dufresne from Shawshank Prison.

Find out how to delete a plan using this new, less destructive manner

Link issues to connect work across teams and projects in Jira

We’ve introduced the ability to link issues directly on the board. You can now surface dependencies and related work to get a clearer picture of how work is progressing. Issues can be linked across different projects in Jira, which means that it’s easier than ever to keep software teams connected to the business, and vice versa.

Read the full documentation

To link issues directly on the board:

• Right-click on an issue or hover to select more actions (…).
• Select Link issue.
• Select a link type, then select the issues you want to link. If you want to link an issue that hasn’t been created yet, select Create linked issue.
• Select Link.

To show linked issues on the board:

• Select View settings in the top right of the board.
• Select the toggle to switch on Linked issues.

Parenting a team managed epic with a company-managed initiative is now possible in Plans

To help you better integrate work across project types, you can now assign a company-managed initiative as a parent to a team-managed epic. Configuring a hierarchy level above epic is only possible in Premium or Enterprise editions.

Create child issues for hierarchy level above Epic (+1)

Jira Premium users can create hierarchy levels above epic to track individual pieces of work to larger initiatives. Read more about hierarchy levels in our documentation.

With this change, Premium customers can now create child issues for issues in these additional hierarchy levels. For example, suppose your site includes a hierarchy level called Initiative that sits above Epic. You can now create an Epic while viewing an Initiative issue using the Create a child issue button. That new Epic will then be automatically associated with the Initiative via the Parent field.

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

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

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

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

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

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

Plans in Jira - Autoscheduler disabled by default in new plans

Newly created plans will no longer have the Auto-scheduler enabled by default. Plan owners can still enable it in the Plan settings if they want.

Object schema counter and limit info for Assets

Ever wondered exactly how many object schemas you have in Assets? Wonder no more!

We've added a schema counter to the Assets overview page (left of the Objects counter) so you can keep track. If you ever reach the maximum limit for object schemas, we've also added a tooltip and replaced the 'Create schema' button with a label (so you don't go ahead through all the effort of creating a new schema only to find out that you can't!).

Quickly create incidents from your Slack channels

It's now possible for you to create an incident directly from your Slack channels. Use the /jsmops create incident command in any Slack channel and you'll be able to fill out the incident details. When you create the incident, You can choose to link the incident to a new Slack channel or to an existing channel.

Once the incident is created, all the incident details, updates, and actions will be available and the affected services' responders will be automatically added to the channel.

Read how to connect Slack with Jira Service Management

Products and entitlements

We’ve added a new feature that allows you to add products and customer entitlements in your project.

An entitlement represents a customer's access to a product or service, and creating entitlements allows you to add and view important details related to that access. These details could include things like: support level, product tier, number of licenses, expiry date or any other information about their entitlement.

To get started, go to Project settings, then Features and enable Products and entitlements. This will add a new page to your project navigation called Products.

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

New project details page for company-managed service projects

We've redesigned the project details page for company-managed projects to match the clean, sleek look of our team-managed project details page. As part of this update, you can also enjoy more formatting options for the project description.

Introducing a new workflow editor in company-managed projects

We're building a new workflow editor for your company-managed projects!

If you're familiar with team-managed projects, you might be familiar with the new workflow editor - it's a faster, cleaner, more intuitive experience for creating and editing your workflows.

In our first release, we're making the new editor available for Jira Service Management projects so you can start using it right away, but we still have more work to do to bring across all the features from the old workflow editor.

While we continue building the new editor, you can switch between editors as needed using the Open in old editor or Open in new editor options. You can also select a default editor so that your workflows always open in the editor of your choice. Just select Change default editor and follow the steps to make your choice.

If you have feedback on your experience with the new editor, we'd love to hear it. Make use of the feedback options in the editor to let us know your thoughts.

Learn more about the new workflow editor.

Reports now available for Assets

Get a a comprehensive overview of your Assets performance, simplify your analysis process and gather valuable insights at a glance with the new reports dashboard for Assets in Jira Service Management.

Things to note:

• This functionality will disabled for customers who have signed HIPAA and have tagged Jira Service Management. We are working to enable it but this will take a few more days.

• Customers who have moved their Jira Service Management instance to the Switzerland Data Residency region will not have any data available in reports.

To get started with the reports for Assets dashboard:

• Go to Assets
• Select Reports (to the left of Configuration)

Improved search results in your help center

Your help center's search results will now also include links to external resources that you've added to your service projects. This means customers can find links to useful self-service articles and more from tools outside Jira Service Management in your help center, making their search experience more comprehensive and efficient.

Find out more about adding external resources to your service project.

Create new request types with ease in team-managed projects using request type templates

Recently made available in company-managed projects, we’re now bringing the time-saving benefits of the new request type templates to team-managed projects (TMPs).

Instead of creating a new request type from scratch, you’ll have the option to browse a library of templates designed for a range of different teams and use cases, and select one to quickly create a new request type that you can edit later.

These request type templates act as a starting point for Jira admins who are new to Jira Service Management, as well as those Jira admins who are looking to create consistency across multiple projects, or further customize their project to meet changing needs.

To create a new request type using a template:

• From the navigation on the left, select Project settings, then Request types.
• At the bottom of your list of request types, select Add request type, then select Create from template.
• Browse, search, and Preview the different templates.
• Select the template you want to use to create your new request type.
• Review and update the request type’s name, description, and icon, then select Save.

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.

Create request types using Atlassian Intelligence

We’ve bundled all your options under Create request type, so you can choose to either create from blank, from a template, or now using Atlassian Intelligence (AI) in the one place.

Select Create using AI to spend less time figuring out what kind of request types to create for your project, and instead get suggestions using Atlassian Intelligence.

Simply describe what type of work your team typically manages, and Atlassian Intelligence will provide you with a number of suggestions you can choose to create based on your prompt. Select a suggestion if you wish to create it, or choose to enter another prompt for more suggestions.

It’s faster and easier for users to try new products

When a user wants to try a new product from an Atlassian product (they are using Jira Software and see a prompt to try Confluence, for example), they typically have to send a request to their admin first. Previously this meant adding a personalized note to the request, before hitting ‘send'. Now, the user can hit ‘send’ on a request for Jira Service Management, Confluence or Jira Product Discovery without a personalized note, removing one step entirely.

When the admin receives the request (via notification or email), it has updated information about the requested product, and no personalized note.

This makes it faster and easier for users to request products, and admins to understand what the products do.

Updated read-only version of Workflows

We've updated the read-only version of the Workflows page in Project settings for project admins. The new page looks more modern, has a faster load time, and will allow us to make more changes in the future. Note that we've also removed the text preview functionality.

Use your existing Slack channel to collaborate on incidents

Previously, Jira Service Management helped your incident responders immediately create a new Slack channel to collaborate on an incident.

Now, you can even add an existing Slack channel to an incident, allowing you to link multiple incidents to the same Slack channel. This way, your team can easily manage multiple incidents and be notified of the latest activity through the same Slack channel.

How to add an existing channel to your incident

Go to your incident and select Add channel in the Slack field in Details. In the Create new or select existing channel option, select Select existing channel. Finally*,* select your Slack workspace and channel and select Add.

Read how to use chat and video tools to resolve incidents as a team

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.

Navigation group label change

We've updated the "Channels & people" group label in the project navigation to "Directory" to better accommodate optional features that appear in the navigation when enabled.

Connect Google Drive in Project Pages

Project pages previously only connected to Confluence. Users can now connect and view Google Drive files from within Jira

Any updates made to Google Drive files within Jira are automatically synced, ensuring that all team members are working with the most up-to-date information.

The integration provides an option to search for and link existing Google Drive files to Jira issues, making it simple to associate relevant files with specific tasks.

To get started with connecting Google Drive to Jira Software:

If you’ve never used project pages before:

1. Select Connect Google Drive
2. Select sign in with Google
3. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
4. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project
5. Select connect shared drive

If you have Confluence connected to project pages:

1. Select the Add Google Drive tab
2. Select Connect Google Drive
3. Select sign in with Google
4. Log into your Google and grant access to your shared drives in your account. Close this tab and return back to Jira.
5. Select the shared drive you want to connect from the dropdown. Your shared drive will be visible to anyone in your Jira project.
6. Select connect shared drive.

That’s it! Once you’ve connected a shared Google Drive to Jira, it will be synced to your Jira project.

Colourful categories

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

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

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 Work Management, Jira Software, 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

Keep your board's background when you import from Trello

Trello backgrounds are now imported into a project. Preserve your board's identity even when you're moving it over to Jira.

You can import Trello boards when you sign up, or when you create a new project from templates.

Adding whimsy to onboarding tutorial

Enjoy whimsical animations while learning Jira best practices.

Celebrate accomplishments

We added fun animations to celebrate finished tasks.

A confetti animation will appear when you change the status of a task to done

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.

Use AI to generate new content or improve existing content

Generate new content in your ideas descriptions and comments – brainstorm new content, summarize or shorten the content you already have, find action items, and improve your spelling and grammar.

Learn more about Atlassian intelligence.

Calculate delivery progress based on story points

With enhanced calculation options, the delivery progress can now better reflect the size of your linked delivery tickets in Jira Product Discovery. You can easily configure the field to display progress based either on the number of issues per status or on the number of issue story points per status.

Creators can configure the delivery progress field:

1. Click the Delivery progress field to open the Delivery tab, or select a specific idea and go to the Delivery tab.
2. On the Delivery tab, click the delivery progress bar, and then select Configure delivery progress.
3. From the dropdowns, choose the most suitable options to display the delivery progress:
   1. Default or Simple for the estimation type
   2. Issue count or Story points for the estimation values

Learn more details about the estimation rules and configuration options.

It’s faster and easier for users to try new products

When a user wants to try a new product from an Atlassian product (they are using Jira Software and see a prompt to try Confluence, for example), they typically have to send a request to their admin first. Previously this meant adding a personalized note to the request, before hitting ‘send'. Now, the user can hit ‘send’ on a request for Jira Service Management, Confluence or Jira Product Discovery without a personalized note, removing one step entirely.

When the admin receives the request (via notification or email), it has updated information about the requested product, and no personalized note.

This makes it faster and easier for users to request products, and admins to understand what the products do.

Use Confluence automation to create incident tickets in Jira Service Management

You can now create an incident ticket in Jira Service Management using a Confluence automation rule.

Full-screen image previews in edit mode

Get a closer look at your images while editing with the new full-screen preview feature. Simply select an image and select the new Preview button in the floating toolbar. The image will be displayed full-screen, allowing you to make informed editing decisions.

Confluence Premium: Even better content management

The space content manager now allows you to do even more. In this release, we’ve added a new filter option to view pages with deactivated owners, as well as some UI improvements to the existing experience. This allows space admins with Confluence Premium or Enterprise to view and update pages owned by deactivated users, with bulk action support for changing up to 100 pages at a time.

Visit a space and select the Content manager option from the sidebar

To filter pages, select the Filters button at the top of the table. From there, you can select to view Inactive pages, which can be further filtered by date, or the new Pages without active owners option, which can be filtered by deactivated account name.

Create and edit with greater context and control

The sidebar and top navigation are now available while editing a page. Now, you can orient wherever you are and navigate wherever you need to, whenever you need to, even while creating and/or updating content.

As usual, the sidebar can be collapsed and expanded as needed anytime.

Be more expressive with panels

In addition to the five preset panel options, you can customize panels by choosing one of the 20 background colors available.

Panels can have emojis, or you can remove the emoji to meet the needs of your content. The emojis available to you are the same set that you already use in Confluence; this includes custom emojis you and your teammates added.

1. Add a panel to a page by typing /custom panel or by selecting Custom panel from the insert menu.

2. Use the floating toolbar to choose a background color and pick an emoji if you want one.

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.

Confluence Premium: 20 new automation components

Confluence automation is adding 12 new trigger and 8 new action components.

Space, product, and site administrators can use components to build rules that automatically organize content and manage team workflows. Automation is available in Confluence Premium and Confluence Enterprise.

Learn more about creating automation rules

Follow-up questions for Smart Answers in Confluence Search

Smart Answers in Confluence Search now provides suggested follow-up questions along with the corresponding answers.

Table editing just got smoother with drag-and-drop

We're introducing the long-awaited drag-and-drop functionality for tables within Confluence Cloud. Now, you can quickly and intuitively reorganize rows and columns in your tables by simply dragging them to the desired location.

With the rollout of this feature, you’ll also get easy access to row and column actions in the new drag handle menus. Add, move, sort, and distribute widths straight from these menus.

This update, highly requested by users, will significantly improve your table editing experience, saving you time and effort.

Here's what's new:

• Effortless reordering: Drag and drop rows and columns anywhere within the table.
• Visual guidance: New drag handles and drop zones make it clear where you can place elements.
• Smooth navigation: Wide or long tables automatically scroll as you drag for ultimate control.
• Enhanced interface: Enjoy new menus, icons, and buttons for managing rows and columns.

Create a Confluence page while viewing a Jira issue

You can now create a new Confluence page while viewing a Jira issue.

People licensed on both Jira and Confluence have two ways to create a page. Access the Create menu dropdown either below the issue's title or in the Confluence content section.

The page you create will be linked to your issue, making it easier to work together.

Anyone with Confluence and Jira will see the new Create options on every issue. Add Confluence and connect it to Jira to activate this feature.

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.

Default data classification levels get migrated

When organization administrators migrate a space or Confluence instance, default data classification levels migrate as well.

This preserves related rules around creating, storing, managing, moving, or deleting page and blog data in each space — without space administrators needing to reset a default.

Learn more about data classification

Data classification is currently only available through the Atlassian Information Security Beta program. If you’re not part of the program, subscribe to our Cloud roadmap to be informed when this feature becomes generally available.

Product administration updates

Confluence administration has long contained more than settings. We made updates to reflect that and make everything easier to find.

When product admins select the gear icon in the top-right of Confluence navigation, they’ll see new hierarchy in the side navigation, distinguishing monitoring capability from premium admin tools from settings. The settings themselves are now collapsed into more manageable, expandable, buckets — and are searchable by keyword.

Confluence admins should continue to select the Confluence administration gear (formerly Settings) in the top-right of Confluence navigation.

Guests can receive and manage email notifications

With email notifications, guests can now get closer to the work happening in Confluence, stay in the know, and respond more quickly to matters that need their attention.

They can also fine-tune their email preferences to make sure they're only getting notified about what most matters to them.

Insert tables of any size with the new table size selector

No more one-size-fits-all tables! We've added a new Table size option to the editor toolbar. Just select the dropdown arrow next to the Table button to reveal the Table size selector. A grid will appear, letting you choose a table size, up to 10 rows by 10 columns.

It’s faster and easier for users to try new products

When a user wants to try a new product from an Atlassian product (they are using Jira Software and see a prompt to try Confluence, for example), they typically have to send a request to their admin first. Previously this meant adding a personalized note to the request, before hitting ‘send'. Now, the user can hit ‘send’ on a request for Jira Service Management, Confluence or Jira Product Discovery without a personalized note, removing one step entirely.

When the admin receives the request (via notification or email), it has updated information about the requested product, and no personalized note.

This makes it faster and easier for users to request products, and admins to understand what the products do.

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.

Team calendars: settings refresh

The configuration settings for team calendars in Confluence have a new streamlined and modern look.

Confluence administrators should:

• Select the wheel icon in the top-right corner to open Confluence administration.
• Find Settings in the left-hand navigation.
• Select Data management > Team calendars.

Catch up quickly with page comments summary

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

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

Admins can now create automation rules for public links

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

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

Bring all your work into Confluence

Streamline your workflow and enhance productivity by adding a Smart Link in the content tree. All you need is a URL to bring over a thousand supported products directly into a Confluence space. What can you do with a Smart Link in the content tree?

1. Select Create in the main navigation or + in the Content section of the space sidebar.
2. Select Smart Link.
3. Enter the URL of the link you want to add to Confluence.
4. Select Add Smart Link to finish.

Confluence Premium: Content manager in sidebar navigation

Space administrators with Confluence Premium or Enterprise will now find it a little easier to manage their content.

The content manager (formerly bulk archive) is now available as a link in the top section of the sidebar, alongside other key features like automation and analytics. Use it to filter for inactive pages and assess the state of content before applying actions like archive or delete to hundreds of selections at at time.

Learn more about the content manager

Sidebar links can be turned on or off by visiting Space Settings > Manage space > Edit sidebar.

Automatically build automation rules for public links

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

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

Automatically build automation rules to assign guest users to a space

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

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

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

Introducing CODEOWNERS

Code owners is a feature that helps teams automatically assign best-suited reviewers to Bitbucket pull requests and do so in a fast way, based on which files are in the PR changeset. The CODEOWNERS file resides in the code repository and describes which file patterns are owned by which teams. By doing this mapping of code paths to well-suited code owners, teams can have reviewers automatically assigned to PRs. This removes the mental load from the PR author in deciding whom to add to their PR, as well as reducing the time the author would have to spend doing that. Learn more about setting up and using code owners.

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.

Introducing 100MB file size limit

Starting on May 6, we will begin rolling out a 100MB file size limit for Git pushes to Bitbucket Cloud repositories. Learn more about the new file size limit and join in on the conversation via our community post.

Restrict who can add 3rd-party data sources to a workspace

To tighten security, organization and Analytics admins can now restrict the ability to add third-party data sources to only admins.

To change this setting:

1. Select Admin settings > Settings from the global navigation.
2. For Who can add third-party data sources, select either Anyone in the workspace or Organization and Analytics admins only.
3. Select Save.