Atlassian Cloud changes May 22 to May 29, 2023 | Atlassian Cloud (2023)

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

Take control of your domain’s user accounts

ROLLING OUT

We’re giving you more flexibility to manage user accounts for your domains. You’ll be able to control how and what specific user accounts you’d like to manage.

When you verify your domain, you can:

• Choose how to claim new users for a domain — automatically or manually

• Choose to claim all users or some new users for a domain

Learn how you currently verify a domain

More flexible product access for organization admins

ROLLING OUT

As part of our improvements to centralize your user management experience, we’re introducing changes to the organization admin role and site-admins group.

These changes only apply to new organizations you create (for example, when trialing a new product). We won’t change anything about how you have configured your existing site-admins group today.

Whenever you assign someone the organization admin role, they will no longer automatically get a product access role for every product in your organization. This means organization admins won’t count towards your bill unless you:

• explicitly assign them a role that gives product access (the user, user (agent) or product admin roles);

• put them into a group that assigns one of these roles; or

• add a product access role to the org-admins group.

To better align the site-admins group with these improvements, we’re also renaming it to org-admins.

To make someone an organization admin:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Directory > Users.
3. Find a user, then select their avatar or Show details.
4. From the3 dot icon at the top-left of the page, selectAssign organization role.
5. Select Assign role.

To assign product roles to an organization admin:

1. From the organization admin’s user details screen, select Grant access
2. Select one or more roles from the Product roles column.
3. SelectGrant access.

Prevent users from inviting anyone to your products

ROLLING OUT

We’re giving you the ability to prevent user invites for your products. You’ll have more control over who can invite people to your products and how they do it.

When you prevent user invites, existing users are unable to invite people through that product. Organization admins can still invite anyone and give product access from admin.atlassian.com.

To prevent user invites:

1. Go to admin.atlassian.com.
2. Select Products > User access settings > User invites.
3. Select the Don’t allow invites dropdown option for the product.

User counts helps you plan your Enterprise subscriptions capacity

ROLLING OUT

User counts shows you how many users you have in each product instance in an Enterprise plan. This tells you how many users you can still add, whether you’re nearing your user tier limit, or if you've exceeded your user tier limit.

To help plan your Enterprise subscriptions capacity you can:

• View User count growth trend - For each Enterprise product, view the number of unique users in each of the past 12 months, and how it changed from one month to the next.
• Receive email notifications - Choose to be notified when your user count reaches 80% of the user tier for that product.
• Export users - Export the list of users who are included in the user count for a product instance in your Enterprise plan.

To view the user counts for your Enterprise plans:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > User counts.
3. Select View to see the user counts for each individual product instance in an Enterprise plan.

From here you can see the growth trend, export your users, and opt out of getting email notifications when you reach 80% of the user tier limit.

Learn more about monitoring your user counts

Delegate the responsibility of managing users with our new admin role

ROLLING OUT

We’re giving you more flexibility to delegate administrative tasks to other people with the new user access admin role.

This new role allows you to assign specific people to manage product access for your organization’s users from admin.atlassian.com on a per product basis. This means you can have one person managing your users' access to Confluence and a different person for Jira.

User access admins have limited access to Atlassian Administration, so you can delegate tasks without granting full organization admin permissions. The user access admin role doesn’t give any product access, so users won’t count towards your bill (unless they’re assigned another role that gives product access).

Read more about the user access admin role

To assign someone the user access admin role:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Directory > Users.
3. Select a user.
4. Select Add products to view a list of products the user doesn’t have access to.
5. From the Product roles dropdown for a Product, select User access admin.
6. Select Grant.

If the user already has a role for the product, assign the role by selecting User access admin next to the product under Products.

You can also assign the user access admin role in the same way you assign any other product roles –by adding the user to a group that contains that product role or assigning the role when you invite a new user to your organization.

Data residency in Singapore

ROLLING OUT

We’re launching data residency in Singapore to allow you to control where your data is stored. It ensures compliance with data protection regulations and enhances data security.
Singapore marks the fifth region of our expansion, following Germany, the USA, Europe, and Australia.

We're adding Singapore to the list of supported locations in phases, we aim for it to be 100% rolled out to all of our customers by June 2023.

To schedule a data residency move for Singapore:

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, you can select Singapore as the location.

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

ROLLING OUT NEW THIS WEEK

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

.

Update to the create issue mini window

ROLLING OUT NEW THIS WEEK

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.

Bug fixes to team-managed issues in backlog

ROLLING OUT

This bug fix corrects unexpected behavior with issues in team-managed projects. Bug fix details:

• Team-managed epics and base-level issues on company-managed backlogs will render the same way as issues from company-managed projects.

• Team-managed base-level issues now show in the backlog (previously they were not included).

• Team-managed base-level issues are displayed in the same way as company-managed base-level issues. Previously, team-managed base level issues with a parent were displayed in the same way as subtasks.

Add status while creating an issue

ROLLING OUT

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

ROLLING OUT

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.

Preview smart links by hovering over them

ROLLING OUT

You no longer need to open another tab to see what’s behind a smart link! Now preview smart links, including links to other issues or Confluence pages, by just hovering over them. To try it out, go to an issue with a smart link and hover over it.

Issue view: Apps are moving to collapsible groups

ROLLING OUT

Marketplace vendors can put their apps in a collapsible group on the issue view. This means you can show or hide groups without obscuring other fields on the issue view. An app will only be in a group if a Marketplace vendor has put it there.

Use different accounts without logging on/off

We’re implementing site-scoped sessions for our users on Jira Software, Confluence, Jira Service Management, Jira Work Management, Jira Product Discovery, and Compass.

You can now use different accounts to access different sites at the same time, without needing to switch accounts or use different browsers.

For example, let’s say you have a personal Confluence site and a company Confluence site. With scoped sessions, you can use account A to access your personal Confluence site and account B to access your company Confluence site - at the same time, in the same browser.

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

ROLLING OUT

Jira admins making a new GitHub connection for a new organisation now need to install theGitHub 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.

Issue view: See the issue view’s top features

ROLLING OUT

We’re revamping the issue view’s tour to be clearer, more concise, and related to the Jira product you’re using. To try it out, go to an issue and select ··· > Take a tour.

Tip: Try the tour in both Jira Software Cloud and Jira Service Management Cloud to see the top features of different products.

Site Import: user migration options will no longer be available

ROLLING OUT

We’re discontinuing user migration options for Server to Cloud migrations using Site Import: Merge with existing cloud users and Overwrite existing cloud users. You'll need to use the Jira Cloud Migration Assistant to migrate users.

Learn how to migrate users and groups with Jira Cloud Migration Assistant

New 'Team' custom field in Jira

ROLLING OUT

Admins can now enable a new ‘Team’ custom field fromproject settings. This allows project users to assign Jira issues and tasks to Atlassian teams.

Read more about Atlassian teams in Jira

Made SLA time formats consistent with locality

ROLLING OUT

Previously, the date and time formatting for SLAs did not match the formatting of other displayed dates and times in Jira Service Management. SLA date and time formats will now display correctly based on each user's locality,

Replace workflow using a template

ROLLING OUT

We've introduced a new way to change the workflow of a request type. You can now replace the current workflow with a new workflow from the Request types screen. The workflow has the following statuses: TO DO, IN PROGRESS, PENDING, DONE. You can add more statuses to this workflow after adding it.

To replace a workflow of a request type with a new workflow:

1. Go to Project settings, then select Request types.
2. Next to the request type select More (•••).
3. Under Workflow, select Replace with new.

Add rich context for customers and organizations

ROLLING OUT

We are adding dedicated profile pages that contain detailed information for each organization and customer allowing your teams to easily create and modify queues and SLAs for their specific needs. Creating more informed JQL queries gives agents the flexibility and power to see important information and context where it’s needed.

Learn more about the customer service management feature

Batched notifications for custom ‘Email from’ names

ROLLING OUT

Jira notification emails that use a custom Email from name will now group updates into a single summary email, reducing the overall volume of emails that you will receive.

We’ve also updated the format of these email to be consistent with other Jira issue notification emails.

OAuth upgrade for Microsoft email servers

ROLLING OUT

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.

SLA success rate will be 100% for time periods when no issues are created

ROLLING OUT

Thanks to feedback from customers, we learned that the SLA success rate is currently reported as 0.0% for time periods when there are no issues created which isn't the expected result.

Now that we've fixed it, the SLA success rate for time periods when no issues are created will be reported as 100% instead of 0.0%.

Update your SLA's start, stop, and pause conditions based on an issue's due date field

ROLLING OUT

Add start, stop and pause conditions to your SLAs based on the due date field in your issues. Here's how the new conditions work.

Start and stop conditions:

• • Due Date: Set*: Start or stop an SLA when the due date is set for the first time.

• • Due Date: Cleared*: Start or stop an SLA when a due date value is cleared from the field.

• • Due Date: Changed*: Start or stop an SLA when the due date value is changed from one date to another.

Pause conditions:

• • Due Date: Set*: Pause an SLA when the due date is set for the first time.

• • Due Date: Not Set*: Pause an SLA when there is no due date for the issue.

You'll find these new conditions when editing your SLA conditions in Project settings > SLAs.

Jira automation: Get input from users when a Manual automation is triggered

More changes to Manual trigger rules in Jira automation. When configuring a Manual rule, you now have the option to request input from users before the rule runs.

This allows you to configure input fields, which will pop up when a user triggers the rule. These input fields can also be mandatory, and you can reference the user’s input with smart values in other components of your rule.

To give this a try:

1. Configure an automation rule.
   • For project automation, go to Project settings > Automation
   • For global automation go to Jira settings > Global automation
2. Select Manual trigger.
3. Select the Prompt for input when this rule is triggered checkbox.

New categories in request types "more options" menu

ROLLING OUT

We've added categories to the 'more options' menu for each request type on the Request types screen. The update makes it easier to find the option you need. The categories are: "Request type", "Workflow" and "Portal group".

Team-managed projects: Improved version panel

ROLLING OUT NEW THIS WEEK

We’ve revamped the version panel to show you more important details while planning work in the backlog. You can now track the number of issues in each version, as well as your team’s progress for estimated tasks. Versions with at least one issue will now show a progress bar to indicate the number of issues in each status category (To Do, In Progress, Done).

To open the version panel in the backlog, select the version filter, then switch on the toggle. View a version’s details by selecting the chevron (>) next to the version name.

Changes to epic fields in company-managed projects

ROLLING OUT NEW THIS WEEK

We've made changes to epics on your board and backlog to more closely align epics across company-managed and team-managed projects.

Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color.

These updates will also apply to the Epic link field in the issue view. Learn more about these changes

Move data between sites with cloud-to-cloud migration

ROLLING OUT

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

ROLLING OUT

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 namedteam-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 towork with other teamsacross many projects in a standard way, such as sharing a workflow.

Advanced Roadmaps - Sample Plan

ROLLING OUT

Advanced Roadmaps can do so many different things that it's hard to describe it succinctly. It's easier to show you.

With this update, you can create a sample plan using simulated data. Then you can manipulate that data to learn how Advanced Roadmaps lays out your project and helps you plan.

To create your sample plan, select Create sample plan from the Plans dropdown menu.

View and triage security vulnerabilities in Jira

ROLLING OUT

We’re really excited to announce the rollout of the new security feature in Jira Software Cloud.

The security feature pulls in data from connected security tools to create a holistic view of vulnerabilities impacting your product.

Our first supported security tool is Snyk, and we’ll add support for more security tools soon.

The security feature helps your team embrace a culture of DevSecOps, and turn unexpected vulnerabilities into manageable, efficient work.

Get started with security:

If you have set up a code management tool on a project, Security will automatically appear in the list of features.

Or, turn it on manually:

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

We’re gradually rolling out the security feature over the next few weeks. If you don’t see it yet, check back again soon.

Advanced Roadmaps - New navigation

ROLLING OUT

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.

Team-managed projects: Add a comment when flagging issues

ROLLING OUT

When you flag an issue, this tells your team that it’s important and needs attention. In case your teammates need more context, we’ve added the ability to add a comment when adding or removing flags.

Previously, this feature was only available on company-managed projects.

Right-click on an issue in your board or backlog, and selectAdd flag. Enter any details you'd like your team to be aware of, then select Confirm.

Dynamic issue type names at the Epic level

ROLLING OUT

If, in your site, an administrator has renamed the issue type formally known as Epic to something else (such as Features), that name now appears elsewhere in product. You'll see this change on the project backlog, timeline, and "Epic" reports.

In the image below, we've renamed the epic issue type in our project to Steve. As you can see, that new name now populates on our backlog's epic panel.

Introducing drivers and contributors for releases

ROLLING OUT

We’ve added two roles to the releases feature in Jira Software Cloud: drivers and contributors.

Drivers

A driver is someone in your team that’s responsible for coordinating the release from start to finish. For example, they might make sure all issues are on track, related work has been completed, or remind stakeholders to give an approval.

The driver must have admin permissions for the project. By default, we’ll use the person that created the release as the driver, but you can change it at any time.

Contributors

Contributors are people who need to complete related work for the release. We’ll automatically add contributors based on people who have issues assigned to them from the related work section.

All the key release info

We’ve added drivers and contributors to a new section in the top-right of your release pages, along with the release’s status and timelines. All the important details are ready at a glance.

Get started

To check out the new changes:

1. From your project sidebar, select Releases.
2. Select a release from the list.

The new section will be in the top-right of the screen. You’ll also notice some updates when creating a new release.

We’re rolling this feature out over the next few weeks. If you don’t see it yet, check back again soon.

We now migrate Jira Service Management customer accounts along with the users and groups in your migration.

ROLLING OUT

We now migrate all active and inactive Jira Service Management customer accounts as part of your migration. Even if Jira Service Management is on a Free plan, there is no limit on the number of customer accounts you can migrate.

Your source and destination site must have the same Jira products. To migrate Jira Service Management customer accounts, add Jira Service Management on the destination site to reduce the chances of migration failure.

If you don’t want to use a product after migrating, use a free plan, or start a 7-day trial for that product. You can remove the product after completing your migration.Learn how to add a new product to your organization

Quickly create pages for retros at the end of your sprint

ROLLING OUT

Lots of agile teams run a retrospective (also called a retro) when a sprint’s over, and keep notes on the discussions and actions.

In team-managed projects, this is now even easier with a handy link to create a retro page in Confluence when you complete a sprint.

Once your retro page is published, it will be linked to your sprint and posted in the sprint’s burndown chart. That makes it easy for your team to find it when it’s time for your retro session.

Learn more about running a retrospective

To get started with a retro page in Confluence:

1. From either the board or the backlog in your team-managed project, select Complete Sprint.
2. Tick the checkbox to Create a retrospective page for this sprint, then select Complete sprint.
3. Choose a Confluence space or parent page to publish the retro page in, then select Create page.

That’s it! Once you’ve updated the template and published it, it will be linked to that sprint’s burndown chart.

Hide empty attributes in Assets for Jira Service Management

ROLLING OUT NEW THIS WEEK

You can now simplify your view of Assets in Jira Service Management by hiding empty attributes in the object view menu.

Each object type can be configured to either show or hide empty attributes, and Assets will remember the settings for each user.

To get started with this change:

1. Select Assets in the top-nav.
2. Select an object schema.
3. Select an object type where you'd like to hide the empty attributes from view.
4. Select the more icon (...) in the object view menu and select Hide empty attributes.

To show the empty attributes again, repeat the steps above and select Show empty attributes in the menu.

Improved editing for attributes with large numbers of values

ROLLING OUT NEW THIS WEEK

It’s now easier to edit and view attributes with large numbers of values in Assets in Jira Service Management.

When more than twenty values are present in a single attribute, the list will collapse into a button listing the total number of values. Select the button, and it will open up into a details panel that allows for easy viewing and editing of the attribute.

Import secured data from a URL into Assets in Jira Service Management

ROLLING OUT NEW THIS WEEK

You can now import secured data from a URL into Assets in Jira Service Management using a bearer token. This solution will support self-hosted files where bearer authentication has been implemented.

Learn more about importing data from a URL into Assets in Jira Service Management.

New template categories for Jira Service Management templates

NEW THIS WEEK

When creating a new service project, you need to select a template from the project template selection screen. The categories on the left filter the available templates to help you find the one that's best suited for your team. You'll now see three new template categories for Jira Service Management templates: Analytics, Facilities, and IT.

Updates to how you create projects in Jira

ROLLING OUT

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 namedteam-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 towork with other teamsacross many projects in a standard way, such as sharing a workflow.

Simplified object schema configuration and streamlined importing

ROLLING OUT

Configuring an object schema is now streamlined and simplified. When configuring an object schema, you can create new reference types and statuses by selecting Create a reference or Create a status.

We’ve also simplified how imports are created. To create a new import, select Create import, select your import type, and then select Create. Object types and attributes will be automatically created for you.

On the other hand, if you’d like to create object types and attributes manually, you can turn off Automatically create object types and attributes and map your object types and attributes yourself.

Finally, Process Results has been moved into the Imports tab, where you can see the history of your completed imports by selecting View history.

Learn more about importing objects into Jira Service Management.

Quickstart onboarding added to business templates

ROLLING OUT

We've added the Quickstart onboarding panel to all of our project templates with instructions for key tasks to help you get set up in your new Jira Service Management project.

Get step-by-step instructions for:

• customizing request types
• reviewing request channels
• reviewing customer notifications
• inviting team members

Updated project creation experience

ROLLING OUT

We've simplified the process of creating new projects to make it easier to get started. When you select a project template, you will now go straight to the screen where you can add your project's details instead of viewing the details for the template. You can still view the details of the template by selecting See details.

We've also redesigned the form and put some of the more advanced settings in an accordion.

For company-managed projects, these settings include:

• Project key (auto-generated using your project name)
• "Use settings from an existing project"

For team-managed projects, these settings include:

• Access settings (set to private by default)
• Default language (set to the site language by default)
• Project key (auto-generated using your project name)

Respond to your customers quickly with canned responses

ROLLING OUT

You can now create predefined responses and insert them in the issue view while replying to your customers. These responses are useful when you want to answer common questions repeatedly. Agents and project admins can create personal responses and save time from manually typing or copy-pasting similar replies over and again. In addition, admins can also create shared responses and all the agents in their project can reuse them.

Know what request types include a form when creating issues from the global navigation

ROLLING OUT

You'll now be informed if a request type includes a form when creating issues using Create in the global navigation of Jira Service Management. Know what fields are shown in the portal on request types including forms so your team can create issues using any or all of the same fields as your customers. Learn more about creating issues using the global navigation bar.

We now migrate Jira Service Management customer accounts along with the users and groups in your migration.

ROLLING OUT

We now migrate all active and inactive Jira Service Management customer accounts as part of your migration. Even if Jira Service Management is on a Free plan, there is no limit on the number of customer accounts you can migrate.

Your source and destination site must have the same Jira products. To migrate Jira Service Management customer accounts, add Jira Service Management on the destination site to reduce the chances of migration failure.

If you don’t want to use a product after migrating, use a free plan, or start a 7-day trial for that product. You can remove the product after completing your migration.Learn how to add a new product to your organization

Enable notifications for Jira Service Management customers only

ROLLING OUT

You can now enable notifications for Jira Service Management customers while notifications are disabled for other Jira products.

Go to the cog icon on the top right of your screen, then select System > Outgoing mail.

When outgoing mail is disabled, you'll be able to see the option to turn on mail for Jira Service Management only.

If you have compliance and privacy needs, we recommend also turning on safe notifications for Jira Service Management.

Changes to epic fields in company-managed projects

ROLLING OUT NEW THIS WEEK

We've made changes to epics on your board and backlog to more closely align epics across company-managed and team-managed projects.

Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color.

These updates will also apply to the Epic link field in the issue view. Learn more about these changes

Get an aggregated view of multiple business projects

ROLLING OUT

Overviews are collections of projects that help you get a high-level and aggregated view of work spanning multiple business projects.

We know that it's uncommon for many business teams to be working on only one project, and it can be hard to stay on top of your work when it's spread across multiple projects. Now you can create an overview to get a holistic view of your or your team's work.

Overviews is a cross-project planning feature for Jira Work Management that’s only available for:

• Jira Service Management Cloud Premium and Enterprise licenses
• Jira Software Cloud Premium and Enterprise licenses

There are a few reasons you may want to create an overview:

• To get an aggregated view of work spanning multiple Jira Work Management projects
• To understand dependencies between work that’s happening in separate business projects
• To get visibility over your teams' workload and to make sure that work is equally and correctly distributed across your team to ensure your projects are properly resourced
• To get a holistic view of how work is being prioritized, the status of all items, and the different types of work.

Learn more about managing project overviews

Jira Work Management - Confluence linked page in list view

ROLLING OUT

You can now add a new column to show the Confluence pages that are linked to a specific item in Jira Work Management. Not only that, but you can link, unlink, or view the Confluence page directly from the list view.

Add mentioned links to list view

ROLLING OUT

You’ll automatically be able to view mentioned pages in the issue view in Jira Work Management. This means not only will you see any linked Confluence pages but also those pages where the issue has been mentioned.

Deleting a mentioned page won’t remove the mention of the issue but simply remove it from your issue view in Jira Work Management.

Preview smart links by hovering over them

ROLLING OUT

You no longer need to open another tab to see what’s behind a smart link! Now preview smart links, including links to other issues or Confluence pages, by just hovering over them. To try it out, go to an issue with a smart link and hover over it.

Use different accounts without logging on/off

We’re implementing site-scoped sessions for our users on Jira Software, Confluence, Jira Service Management, Jira Work Management, Jira Product Discovery, and Compass.

You can now use different accounts to access different sites at the same time, without needing to switch accounts or use different browsers.

For example, let’s say you have a personal Confluence site and a company Confluence site. With scoped sessions, you can use account A to access your personal Confluence site and account B to access your company Confluence site - at the same time, in the same browser.

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

ROLLING OUT

Jira admins making a new GitHub connection for a new organisation now need to install theGitHub 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.

Express yourself with reactions

ROLLING OUT

Reactions are aninteractive, lightweight way to express yourself on content in Confluence. Now, instead of being able to only like or comment on a page, you and your teammates can choose from dozens of emoji reactions (including custom ones).

At the bottom of a page or blog post, choose an existing reaction, or select the "Add a reaction" icon to add your own. You can also react from the activity feed.

Improved PDF export

ROLLING OUT

We've improved the way Confluence Cloud exports to PDF so that the exported PDF more accurately matches what the Confluence page actually looks like. For example, tables, mentions, dates, and other elements will all render the same way they do on the Confluence page.

Be more expressive with panels

ROLLING OUT

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

ROLLING OUT

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

Sort resolved comments by recency

ROLLING OUT

You can now sort resolved inline comments by newest and oldest order. By default comments will be sorted newest first.

Indent and outdent content easier from the toolbar

ROLLING OUT

The editing toolbar now includes indentation buttons, making indenting and outdenting content easier for those unfamiliar with the existing tab and shift + tab keyboard shortcuts.

You can use the buttons to indent the following content:

• Top-level paragraphs and headings
• Bullet lists
• Numbered lists
• Task lists

Learn more about indenting content in Confluence Cloud

Copy content with ease via the floating toolbar

ROLLING OUT

We’ve updated the floating toolbar experience within the editor. The floating toolbar now includes a copy button, which makes copying page elements easier than ever!

You can use the button to copy the following content:

• Tables
• Panels
• Expands
• Media (images & video)
• Links
• Layouts
• Code snippets
• Extensions and Macros (like the Table of Contents)

Space creation refresh

ROLLING OUT

The new space creation experience shows what a space will look like while you’re creating it so that you can choose the right space for you and your team. Space keys and space icons will be automatically generated for you and can be customized.

In addition, each space template has been improved with better, more relevant information and sample content.

From the top navigation, select Spaces and then Create a new space.

Add space shortcuts faster than before

ROLLING OUT

There is now a quicker and more streamlined way to add space shortcuts.

1. Under Shortcuts in the left navigation of a space, select + (Add shortcut).
2. Search or paste the link you want to add (or choose from recently viewed).
3. (Optional) Edit the text you want to display for the shortcut.
4. Select Enter.

Connections Panel for supported macros and tables

ROLLING OUT

We are adding a Manage Connections button to the Table toolbar for tables and macros that support referentiality. This lets users connect a table as a data source to a macro such as a pivot table or a data visualization. In addition to our native macros, this feature will also support the development of Connect macros that will introduce more functionality.

For more, please see our Community post.

To try out the basic functions:

1. Create a table and add data.
2. Click the table to show the floating toolbar.
3. Click the Manage connected data button.
4. Set your data source and macro options in the right-side panel.
5. Edit the data and watch your macro update in real time.

Use different accounts without logging on/off

We’re implementing site-scoped sessions for our users on Jira Software, Confluence, Jira Service Management, Jira Work Management, Jira Product Discovery, and Compass.

You can now use different accounts to access different sites at the same time, without needing to switch accounts or use different browsers.

For example, let’s say you have a personal Confluence site and a company Confluence site. With scoped sessions, you can use account A to access your personal Confluence site and account B to access your company Confluence site - at the same time, in the same browser.

Introducing the newly upgraded Daily Digest

ROLLING OUT

The Daily Digest email, an overview of updates on the pages and blogs that matter to you, has a fresh new look.

The Daily Digest now offers a richer, more detailed snapshot of updates about new page or blog creation, and comments, reactions, and edits to pages and blogs that you watch and/or collaborate on. You can now opt to review a page’s version history directly from the email.

Updates about new comments and reactions across your workflow will appear in the digest in tandem with individual notification emails that are sent out separately.

In May 2023, we plan to stop sending individual emails about newly created pages to users who subscribe to the daily digest. Our goal is to help cut down on inbox overwhelm. However, if you’d prefer to keep receiving individual alerts about newly created pages, along with the digest, you’ll be able to mark that preference in your email settings.

Pick the product theme that works best for you

ROLLING OUT

You can personalize the way Confluence looks to best suit your needs. The options include Light, Dark, System, or Original (the current default Confluence theme).

To check if you have access to themes:

1. Select your avatar at the top right of the global navigation bar.
2. Select Theme.
3. Choose your preferred theme.

Upgraded email notifications for Confluence

ROLLING OUT

Confluence page and blog email notifications have been updated to be more reliable and visually improved.

Notifications about comments, reactions, and content edits are batched into 10-minute intervals for easier understanding of what’s changed.

Bitbucket Pipelines variable description

ROLLING OUT NEW THIS WEEK

Now you can add a variable description for your Bitbucket Pipeline by configuring the 'description' field for the variable in the bitbucket-pipelines.yml file. The variable description you have provided is displayed under the variable in the Run Pipeline dialog. Now your teammates don't need to go back and forth to the Readme in order to get this information.

Syntax highlighting is now available

ROLLING OUT

We are incrementally releasing a beta version of syntax highlighting for your diffs. Once this feature is available, you can enable Syntax highlighting in Bitbucket Labs, by going directly to this feature in Labs: Go to Labs. You can also access Bitbucket Labs via the Settings dropdown menu and enable the feature there. Thank you to all of you for your input on this feature and your patience as we've worked to get it implemented in Bitbucket Cloud. For more detailed information about syntax highlighting, refer to our community post.

Use different accounts without logging on/off

We’re implementing site-scoped sessions for our users on Jira Software, Confluence, Jira Service Management, Jira Work Management, Jira Product Discovery, and Compass.

You can now use different accounts to access different sites at the same time, without needing to switch accounts or use different browsers.

For example, let’s say you have a personal Confluence site and a company Confluence site. With scoped sessions, you can use account A to access your personal Confluence site and account B to access your company Confluence site - at the same time, in the same browser.