• Atlassian Administration
• Jira platform
• Jira Software
• Jira Service Management
• Jira Work Management
• Jira Product Discovery
• Confluence
• Bitbucket
• Opsgenie

Enhanced security for webhooks

We’re pleased to announce an important security update for webhooks. Users now have the ability to secure webhooks with a new secret field. This enhancement applies to webhooks created through Jira Administration or via the REST API.

When a secret is added to a webhook, it is utilized to generate an HMAC (Hash-based Message Authentication Code) signature. This signature is then included in the request header, ensuring the integrity and authenticity of the webhook payload.

For a comprehensive guide on implementing and understanding this security feature, please refer to the Secure admin webhooks section in our docs.

Health checks for application tunnels

You can now check the connection of your application tunnels to make sure they're up and running. When you do, we run a set of health checks against the tunnels and update their status with the results.

We also added new statuses that correspond to the health checks and better describe the problems that you can encounter. This should help you investigate and troubleshoot any issues with your app tunnels.

To check the connections:

1. In admin.atlassian.com, select Settings > Application tunnels.

2. You'll see the connection status for each application tunnel. You can refresh them any time by selecting Check connections.

Learn more about statuses in application tunnels

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.

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.

Additional self-serve data residency move window options are available

When you request a data residency move, we gather information about your product, including the size of your product data. Previously, there were limited options to move data. We’re enhancing the data residency self-serve experience with new move window options across all tiers of plans.

Move windows indicate when your data residency move can be scheduled. We now offer three types of move windows:

Schedule move in the maintenance window

The move will take place during the maintenance window, and this option becomes available when the move can be safely carried out within a standard maintenance window. For this option, the estimated downtime for the data residency move is under 2 hours.

Schedule move within the next 48 hours

The move will be scheduled within the next 48 hours. This option becomes available when your estimated downtime is less than 20 hours. For example, when your estimated downtime is 19 hours, and you select this option, your move will be scheduled in the next 48 hours. We will inform you via email when the move is scheduled.

Schedule move in a 24-hour window

The move will start on the date and at the time of your choice. However, you will need to request your move at least three days in advance.

Support team will manage your move

Sometimes, we're unable to schedule data residency moves automatically. This could be due to a large amount of data or technical limitations. If we can't automatically schedule your data residency move, we will generate a support ticket after you submit your request, and our support team will help you schedule your move. You can access the support ticket on the data residency page.

To schedule a data residency move:

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 to select where you want to move the product. Select Next.
5. Review the information about your selected location, estimated downtime and the recommended option.
6. Select the recommended option or any other available option that you prefer. Select Next.

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

AMA - All things Atlassian Access

As threats become more sophisticated, your organization’s security posture must also adapt to ensure that your data and users stay protected.

Learn how Atlassian Access can help increase visibility and control across your Atlassian cloud products. Join us on 02/08 to ask the Atlassian Access product experts.

Submit your question

Learn more about Atlassian Access

Fixed incorrect uninstallation of Compass apps

We've fixed an issue that was causing Compass apps to be uninstalled incorrectly on the Connected Apps page. You will now see an Uninstall in Compass button that will link you to Compass where you can uninstall your apps correctly.

Enhanced security for webhooks

We’re pleased to announce an important security update for webhooks. Users now have the ability to secure webhooks with a new secret field. This enhancement applies to webhooks created through Jira Administration or via the REST API.

When a secret is added to a webhook, it is utilized to generate an HMAC (Hash-based Message Authentication Code) signature. This signature is then included in the request header, ensuring the integrity and authenticity of the webhook payload.

For a comprehensive guide on implementing and understanding this security feature, please refer to the Secure admin webhooks section in our docs.

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.

Inline edit to rename dashboard gadgets

We've made renaming gadgets a little faster. When you're editing a dashboard, you can now simply select a gadget's title to rename it. As a result of this change, we've also removed the "Rename" option from the "More actions" menu for gadgets.

To try it out:

1. Open a Jira dashboard that you can edit.
2. Select Edit.
3. Select the title of a gadget.
4. Rename as desired then select the checkmark to save your change.

Visual update to label validation messages

We've updated the appearance of validation messages when updating label fields in the Issue View. These messages will now appear in a raised box above the labels input.

Filter issues by organization

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

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

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.

Health checks for application tunnels

You can now check the connection of your application tunnels to make sure they're up and running. When you do, we run a set of health checks against the tunnels and update their status with the results.

We also added new statuses that correspond to the health checks and better describe the problems that you can encounter. This should help you investigate and troubleshoot any issues with your app tunnels.

To check the connections:

1. In admin.atlassian.com, select Settings > Application tunnels.

2. You'll see the connection status for each application tunnel. You can refresh them any time by selecting Check connections.

Learn more about statuses in application tunnels

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.

OAuth upgrade for Microsoft email servers

With Microsoft deprecating basic authentication, all Microsoft mail servers need to be reconfigured using OAuth. OAuth simplifies your sign in process and is more secure compared to basic authentication.

To configure your Microsoft mail server using OAuth:

1. In the Navigation bar, select Settings > System.
2. Select Incoming mail.
3. Select Add incoming mail server.
4. Give your mail server a name and description.
5. Select Sign in with Microsoft.
6. Select Add.

Learn more about how to configure your mail server.

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.

Early access program: 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.

Display issues in a table

We're rolling out improvements to how you display Jira issues in descriptions or comments. The new experience allows you to search for issues using filters, keywords or JQL*.* It also gives you the flexibility to add, remove, and reorder fields.

To insert Jira issues:

1. Type /jira and select Jira issues.
2. Search for issues with either:
   • Filters - Use filters to narrow down your search
   • Basic - Type in keywords to search for issues
   • JQL - Use Jira Query Language (JQL)
3. Select Insert issues.

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

To edit your table of Jira issues:

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

Add a linked sprint retrospective page for organizations that are new to Confluence

When you complete a sprint, you will now have the option to create a sprint retro in Confluence even if you don't currently have Confluence in your organization. Users who opt in will follow the sign-up flow and create a page that can be linked directly to a Jira issue.

Create new Confluence pages or Jira issues using /create

We've made it easier to create new Confluence pages or Jira issues while editing a description or comment.

To create a new Jira issue using /create:

1. From Jira descriptions or comments, type /create jira.
2. Select Create Jira issues.
3. Enter issue details then select Create.

To create a new Confluence page using /create:

1. From Jira descriptions or comments, type /create confluence.
2. Select Create Confluence page.
3. Enter page details then select Create.

More ways to customize your announcement banner!

Admins can customize and share important messages using the announcement banner with added formatting options such as bold, italic, and underlined rich text, bulleted and numbered lists, links, emojis, and background colors.

To create an announcement banner:

1. Select Settings (⚙) > System under Jira settings. 
2. From the sidebar, select Announcement banner. 
3. Write and format your message and select a color for your banner. 
4. Use the toggle options to show the banner and to enable end users to dismiss the message.
5. Set the banner visibility as Private or Public.
6. Select Publish now.

Control in-product notifications

You can now set preferences for in-product notifications in Jira. In-product notifications appear inside the notifications bell on the top navigation bar.

Go to Personal settings > Notifications to select your notification preferences.

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.

Assets import file size validation

As part of ongoing work to improve the performance and reliability of Assets in Jira Service Management, this change validates whether or not an uploaded import file exceeds the 250mb limit and lets the user know if so.

Search for issues faster from your team-managed projects

We’ve enabled issue navigator for team-managed projects.

Select Issues on the sidebar of your team-managed project to access features such as smart syntax highlighting and enhanced autocomplete. You can also configure columns and have easy access to the JQL editor, which can help you build complex searches using Jira Query Language (JQL). Read about searching for issues in a project

No longer including subtasks when calculating total issues in the backlog for company-managed projects

Subtasks will no longer be included when calculating the total issues that are displayed above each section in the backlog for company-managed projects.

If you filter out everything except subtasks in the backlog, the total issue count above each section will appear as 0.

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.

To link issues directly on the board:

1. Right-click on an issue or hover to select more actions (…).
2. Select Link issue.
3. In the modal, select a link type, then select the issues you’d like to link. If you’d like to link an issue that hasn’t been created yet, select Create linked issue.
4. Select Link.

To show linked issues on the board:

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

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.

Updates to how you create projects in Jira

Creating projects in Jira is now simpler with our new template library. Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works.

Additionally, we’ve renamed our project types (next-gen and classic) to make them clearer and more descriptive:

• Next-gen projects are now named team-managed projects. The functionality itself remains the same and continues to be ideal for independent teams who want to control their own working processes and practices in a self-contained space.

• Classic projects are now named  company-managed projects. Setup and maintained by Jira admins, company-managed projects remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow.

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

Change Atlas goals assignments from your plan

In December, we rolled out the ability to view Atlas goals on your plan. With the rollout of this feature, you can now change the value of the Atlas goal field in your plan to realign your work with different goals.

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.

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

Edit a completed sprint

Things change, so if you ever need to update name or goal of a completed sprint, you can.

From your Sprint report, go to More *...* > Edit sprint.

From your Timeline, select the sprint schedule bar, then More *...* > Edit sprint.

We’re making it easier for your team to access the products they need

Before, people who weren’t admins had to request to access Jira Product Discovery. This request was sent as an email to their admin who could then approve or deny the request.

Now, people who aren’t admins can try Jira Product Discovery without having to send a request to their admin. The admin(s) will get an email and notification when it happens.

This change is only available if someone is on a Free site and wants to try a Free product. Only one person can try Jira Product Discovery. They won’t have admin permissions.

This means it’s easier for people to access the Atlassian tools that they need, and try them out for free.

Admins can always go to admin.atlassian.com to edit user and product permissions.

Configure your timeline

Configuring your timeline is now more accessible, with screenreader and keyboard support and a modern experience to enable, disable, or schedule work on the timeline.

From your Board, go to More *...* > Configure board, and find Timeline in the menu*.*

Bug fix: Security settings for customer notifications requiring approval

We fixed a bug in the customer notifications page for company-managed project settings. Now, changes to the Security settings for notifications where approval is required will save correctly.

For those using the Free plan of Jira Service Management, we also made a small update to the position of the 'Save' button. You can now find the save button at the end of the 'Approval required' page, rather than under the Security settings heading.

Updates to how you create projects in Jira

Creating projects in Jira is now simpler with our new template library. Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works.

Additionally, we’ve renamed our project types (next-gen and classic) to make them clearer and more descriptive:

• Next-gen projects are now named team-managed projects. The functionality itself remains the same and continues to be ideal for independent teams who want to control their own working processes and practices in a self-contained space.

• Classic projects are now named  company-managed projects. Setup and maintained by Jira admins, company-managed projects remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow.

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

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 TMP 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 (TMP) projects.

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.

Get field suggestions using Atlassian Intelligence

Unsure what fields to add to your request forms in Jira Service Management? Now you can use Atlassian Intelligence (AI) to suggest fields based on what type of request you're creating.

Simply select Suggest fields when in the request form tab of a request type to try it out yourself. These suggestions could include a selection of existing fields you can add right away, plus suggestions for custom fields you can choose to create.

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.

Workflows now visible in request types settings

On the request types settings screen, the associated workflow for each request type is displayed in a new Workflow column, making it easier for admins to view and edit their request types' workflows.

From your service project's navigation on the left, select Project settings, then Request types. You'll see a list of the request types that exist in your project, along with their associated issue types, workflows, and portal groups.

Each workflow name acts as a link that allows:

• Jira admins to view and edit the workflow
• Project admins to view the workflow.

Any invalid workflows will be noted in place of the workflow name, and hovering over the 'Invalid workflow' text will reveal a tooltip with guidance on how to resolve the issue.

You can still manage your workflows by going to the More actions menu to the right of each request type, and choosing one of these options:

• View and edit workflow
• Replace with existing
• Replace using template

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.

Portal group is now a required field when creating a new request type from a template

When creating a new request type by selecting one of the templates from the request type template library, you'll need to either select the portal group where you'd like the request form to appear, or select the option to hide it.

This selection will ensure that the form appears in the correct place and can be easily found and used by help seekers. Alternatively, you can hide the form so that it cannot be seen anywhere in the portal.

Portal groups are used to organize request forms in your portal. 
Read more about portals and portal groups

To select the portal group where you'd like your new request form to appear:

• From your navigation on the left, select Project settings, then Request types.
• Select Create request type, then Create from template.
• Browse the template library, then Select the template you want to use.
• On the request type details screen, select an option from the Portal group field's dropdown list, then select Save. You'll have the option to select from any of the portal groups that exist in your project.

Enhanced custom field functionality for approvals configuration

As part of our continuous efforts to enhance project flexibility, custom fields with the correct field context can now be used during approvals configuration. This change allows you to tailor your approvals process more closely to fit your specific project needs.

Previously, users were limited to using fields with global contexts as approver sources when configuring approvals.

This update means that any custom fields linked to a project via a workflow can be used to set an approval step. To review or update the contexts for your custom field and associate it with a particular project:

• From the top navigation of your service project, select Settings, then Issues.
• From the navigation on the left, select Custom fields.
• Select the custom field you want to update, then select the Contexts tab.
• You'll see the context(s) applied to the custom field, and also have the option to Create, edit, or delete contexts.

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.

See all your attachments in one place

We’re introducing a new view so you can see any attachments added to issues in your project. This means you no longer need to search through issues to find a specific attachment.

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 see all the attachments in your project by selecting Attachments from the project view navigation.

From Attachments, you can download an attachment by hovering over it and selecting the download button that appears. You can delete an attachment by hovering over it and selecting the delete button, which removes it from Attachments and the issue it was attached to.

More background colors

We've added more colors to our background palette. Now you have a wider range of options to create your project's identity and overview.

Project background: select the option next to your project's name and choose a color.

Jira Work Management overviews: the new colors will appear on the creation screen.

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

Import data from Jira Software to Jira Work Management

Moving your work from a software project in Jira Software to a business project in Jira Work Management just got easier.

Use the importer to directly import your existing software project data into a new Jira Work Management business project. This helps save the effort of manually moving data and ensures the project information is relevant and accurate. Not to mention, your teams now get to work in the Jira that best fits their use case.

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.

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.

We’re making it easier for your team to access the products they need

Before, people who weren’t admins had to request to access Jira Product Discovery. This request was sent as an email to their admin who could then approve or deny the request.

Now, people who aren’t admins can try Jira Product Discovery without having to send a request to their admin. The admin(s) will get an email and notification when it happens.

This change is only available if someone is on a Free site and wants to try a Free product. Only one person can try Jira Product Discovery. They won’t have admin permissions.

This means it’s easier for people to access the Atlassian tools that they need, and try them out for free.

Admins can always go to admin.atlassian.com to edit user and product permissions.

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.

Switch display of any custom People fields

Up to this point, the People type custom fields displayed the users' avatars. In this new version, you can get more clarity on who these users are by changing the field option from showing an avatar to displaying a name.

To switch the display of avatars to people names:

1 Go to Fields and select a field of the type People.
2 Click Edit field.
3 Under Options, select Avatar only, then Full name with an avatar.

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.

More enhanced nesting arrives

We're excited to introduce more enhanced nesting capabilities in Confluence Cloud. This update empowers you to create structured and layered layouts that enhance readability and information flow.

Specifically, you can now:

• Nest media, code blocks, actions, dividers, and decisions within panels
• Nest lists (bullet and numbered), actions, code blocks, panels, quotes, horizontal rules, decisions, and notes within nested expands
• Nest actions within lists

Health checks for application tunnels

You can now check the connection of your application tunnels to make sure they're up and running. When you do, we run a set of health checks against the tunnels and update their status with the results.

We also added new statuses that correspond to the health checks and better describe the problems that you can encounter. This should help you investigate and troubleshoot any issues with your app tunnels.

To check the connections:

1. In admin.atlassian.com, select Settings > Application tunnels.

2. You'll see the connection status for each application tunnel. You can refresh them any time by selecting Check connections.

Learn more about statuses in application tunnels

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.

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.

Global app switcher changes for Confluence and Jira

We're working to bring Atlassian Organizations to the forefront for our users by including them in the Atlassian app switcher. As part of this work, we're adjusting a few elements to improve the overall usability of the app switcher. Please note that these changes will be rolled out slowly, so there may be differences in the app switcher between products.

What products will this change affect?

• Jira
• Confluence

Key changes:

• The switcher is now filtered by Organization > Product > Site (previously was Product > Site).
• Atlassian Start is no longer a standalone hyperlink, and instead will appear under Your Apps.
• Selecting on an app or product will now open it in a new tab.
• We’ll show you recommended apps under Recommended for your team. However, if you have all apps installed now, you’ll be shown the Discover section instead.
• To improve the speed of execution for the large majority of users, as custom links are only configurable for admins, custom links will no longer appear in the switcher.

Benefits:

• Create a more seamless flow when you switch between Atlassian products.
• Make it easier to identify which organization owns the products you’re using.
• Increase security by letting you know when you're leaving your current organization's workspace.
• Reduce noise when selecting an app - you’ll no longer see apps and sites associated with other organizations.

Join the conversation and give us early feedback

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

Reactions replace likes in Confluence home feed

You can now add, delete, and view reactions in the Confluence home feed, as well as see who reacted to content.

This will make it easier for users to collaborate and express themselves.

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.

Inline images now nestled in your words

Say goodbye to image placement limitations! We're thrilled to introduce inline image placement in the Confluence Cloud. Now, you can seamlessly integrate images within your text and headers for a more visually engaging and dynamic writing experience. No more clunky block-level images interrupting your flow – just natural integration of visuals directly into your content.

But the fun doesn't stop there! You can also switch between inline and block-level images at any time with a simple action. Want a stunning hero image? Make it block-level. Need to illustrate a specific point within your text? Toggle inline and embed it right where you need it.

This update is packed with additional features to enhance your image management:

Full control: Add borders, set alternative text, and link your images with ease.

Dynamic sizing: Images automatically adjust to fit your content, ensuring a smooth visual experience.

Streamlined layout options: Find all image layout tools conveniently grouped together in the image toolbar for a more efficient workflow.

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.

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.

Optimize performance with browser updates

The best Confluence Cloud experience happens when it’s viewed in a browser that is fully supported by our Atlassian team.

When you or another user open Confluence Cloud in an outdated browser, a banner now appears at the top with a reminder to upgrade.

See which browsers we currently support

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.

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.

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.

We’ve made it easier for you to set up and work with integrations

We’re introducing a new, streamlined integration framework offering an improved user experience. The framework is designed to simplify the installation and configuration of integrations while offering greater flexibility in the processes.

The initial setup and configuration steps are now more organized, with each having its own separate space. To keep things neat and tidy, the configuration page has been decluttered. You'll also find that advanced incoming rules have been integrated directly into the main configuration section, bringing everything together in one place. We've improved the readability of incoming and outgoing rules and the process of setting them up and editing them.

Learn more about the Opsgenie integration framework