Atlassian Cloud changes Aug 24 to Aug 31, 2020

These changes have recently been rolled out to Atlassian Cloud sites.

Changes labeled ROLLING OUT are being gradually rolled out and may not be on your site just yet.

Atlassian Cloud

Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management.

Email users with suggested account changes

ROLLING OUT

From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts.

Give your users a Trusted permission

ROLLING OUT

From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves.

Get more work done with improved navigation

ROLLING OUT

Our new, easy-to-use navigation enables you to change organizational contexts with a seamless experience between products and administration. Check out the new top navigation with better-defined categories at admin.atlassian.com. Read more at We’re launching improved navigation for admins.

Jira platform

Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product.

Faster advanced issue search link in quick search

ROLLING OUT NEW THIS WEEK

We’ve updated the Advanced issue search link in the quick search field to help you find what you need faster. We’ve changed the default query when you go from quick search to advanced search from all issues ordered by lastViewed to all issues ordered by created (date). This means not only that the initial list of issues should load faster, but you can also update your search query sooner.

Tips:

  • Select / on your keyboard to open quick search.
  • Select / followed by enter/return on your keyboard to go quickly to advanced issue search.

Custom Fields Filtering

ROLLING OUT NEW THIS WEEK

This update brings the ability to sort by custom fields to Advanced roadmaps on Cloud. Once they’re configured for your plan, you can use the following custom field types as filters:

  • single-choice select
  • multiple-choice select
  • checkbox
  • radio button
  • label

Visit Filtering Issues to learn more about filtering by custom fields.

Next-gen projects: Browse and search for issues in your project

ROLLING OUT

We’ve added issue browsing and search (also called the project issue navigator) to next-gen projects. When you enable the project issue navigator, choose Issues in your project’s sidebar to browse and filter the issues in your project.

In the issue navigator, you can search for and filter issues by status, assignee, reporter, type, and included text. We’ll include more search and filter options in future releases.

To enable the issue navigator in a next-gen project:

  1. Go to your project and choose to Project settings > Features
  2. Enable the toggle for the Issue navigator
  3. Click Back to project and choose Issues in the sidebar to get started

Next-gen: Epic panel in backlog

You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa.

Collapsed next-gen custom fields in advanced issue search

ROLLING OUT

We collapsed next-gen fields in the dropdown selection menus people use to search for issues across Jira. Selecting the right field to filter on isn’t a guessing game anymore. You get more accurate and meaningful search results. We also labelled the fields by their type. To try it out, select Search > Advanced search for issues, and use the +More dropdown to look for your fields.

Issue collector no longer matches the submitter's user session to make them the reporter

ROLLING OUT

We’ve adapted our issue collectors to the Chrome browser’s new cookie security features, but have had to change how they work. The issue collector no longer matches a submitter’s user session to make them the reporter. You can still match them by email address.

To improve issue security, project and issue keys are no longer displayed in the success message after submitting feedback on an issue collector (unless the project is open to anyone on the web).

Learn more about using the issue collector.

Track deployment information in Jira

ROLLING OUT

Get greater visibility of deployments by automatically tracking and displaying Git pipelines against the issues over a time scale. You can now visualize the progress of a work-item as it moves through your deployment pipeline. To use the Deployments feature, simply integrate Jira Software with Bitbucket Pipelines. Learn more about the Deployments feature.

Request approval from approvers associated with a service

ROLLING OUT

When configuring approvals for a workflow in the new IT service management template, admins can now allow approvers associated with a service to flag, review, and approve changes to reduce the risk of impacting service quality. Learn how to request approval from approvers associated with a service.

Next-gen projects: Suggested users in the Assignee and Reporter filters in the issue navigator

ROLLING OUT

Find what you’re looking for even faster with suggested users in the new project issue navigator. When you use the Assignee and Reporter filters, you’ll now get a list of suggested users based on the people you work with most.

Learn more about the project issue navigator.

Advanced Roadmaps for Jira - Sticky field name on collapsed column

ROLLING OUT

This feature allows users to make the field names of collapsed columns remain visible as they scroll down their roadmaps.

Notifications for bulk actions

ROLLING OUT

Users can now get email notifications when someone transitions or comments on multiple requests they’re involved with (watching, reporters etc). You get an email! You get an email! Everyone gets an email! Learn more about using bulk actions

New issue view: Add and use custom emojis

ROLLING OUT

Let your team’s personality shine with custom emojis. To check it out, go to an issue, select a description field or add a comment, click the emoji icon in the toolbar, and select + Add your own emoji. To use custom emojis, find them as usual in the toolbar of the editor or type : and start searching the emoji name.

Site admins can disable custom emojis for the entire site in admin settings.

Issue limits and exclusions for a more accurate roadmap

For a roadmap to be most effective, the issues it presents should accurately reflect your workload. To take a little pressure off you, and to increase load times, the roadmap only displays 300 epics and 3000 issues. To refine the issues, we exclude:

  • Issues that were marked as Done over a year ago.
  • Issues that were resolved with a due date that’s more than a year ago.

Learn more about issues on the roadmap for classic and next-gen projects.

Jira Software

We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects.

GitHub app on the Atlassian Marketplace

ROLLING OUT

We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet.

This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector.

Classic: The roadmap's here to guide your team towards every goal (beta)

ROLLING OUT

The roadmap takes your planning game up a notch. It encourages good habits (go on, add in a due date) and helps you connect dependent work in an easy-to-manage way.

The roadmap really flexes its muscles when it comes to visibility. Because the roadmap presents your team’s epics in one spot, everyone—stakeholders included—can see the big picture. This makes it easier to prioritize and share efforts, watch for scope creep, and get an insight into large pieces of work, ahead of time.

Also, the roadmap is in beta. Stick with us while we sort out the Confluence macro, real-time updates, and issue creation quirks. Learn more about setting up the roadmap for classic projects.

Kanban boards just got faster

ROLLING OUT

Is your team so productive, their 'Done' column is always overflowing? Too many issues on a board can slow it down and make you scroll way too much. To fix this, we’re bringing what we’ve codenamed “Fast Kanban”—a way to keep your board fresh and clean, and as quick as a flash.

The idea behind it is simple. The ‘Done’ column will now show only issues that have been updated (in any way) in the last 2 weeks, hiding the rest. Less noise on your board means happier teams. Any project admin can change the retention period, or choose to display all issues, if they prefer. Learn more

Where there’s an epic, there’s a way to change its color

ROLLING OUT

Spot a color clash in your backlog or board? In classic projects, you can now change the epic color when you see it. Wherever your epic shows up, so will all the color options.

Learn more about the epic issue type

Choose where to move issues from a deleted column

ROLLING OUT

Sometimes it’s nice to start fresh. If you decide a column isn’t worthy of your board any more, delete it, and choose another column to store any issues it contained. Those issues will then inherit the status of the new column.

Your board, however, always needs a done column. So, if you delete the done column, things work the other way around. The column you choose will inherit both the done issues and the done status. Magic.

Learn more about boards and columns in next-gen projects.

Roadmap: Right-click an epic to change its color

ROLLING OUT

Maybe the color combo isn’t quite right, or you’ve noticed multiple epics are the exact same shade of green.

Soothe your eyes and right-click the epic, directly on the roadmap, to choose a fresh color.

Learn about all the color options for classic and next-gen projects.

Jira Service Desk

New issue view for Jira Service Desk

ROLLING OUT

The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view.

Use keyboard shortcuts in your queues

ROLLING OUT

Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard!

Focused request types page and new portal groups page

ROLLING OUT

We’re revamping the Request types page so you can focus on editing and creating request types, and bringing your portal settings together so that you can manage your portal groups in one place. Plus, there's no more ‘hidden from portal' group - request types will be hidden from your portal by default.

Knowledge base settings refresh

ROLLING OUT

The Knowledge base settings page has been updated - we’ve made some layout adjustments to refresh the page. Go to Project settings > Knowledge base to check it out.

Confluence

Jira issue URLs are converted to smart links

ROLLING OUT

When you paste a Jira issue link into a Confluence page, the URL is converted to a smart link that displays the page icon and the page title. This works if the Jira and Confluence sites are linked or if they are both cloud versions.

Convert pages to use the new editor

ROLLING OUT

You can now convert your existing pages that were created using the legacy editor to use the new editing experience! Learn more

Advanced Roadmaps for Jira plan macro

ROLLING OUT

The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams.

See and interact with inline comments when editing a page

ROLLING OUT

✍️ To make life easier for page authors who need to implement feedback added as an inline comment, you can now see the inline comments when editing a page. This means that you can see the comments in context, reply to them, resolve them, and delete them. :celebrate:

A simpler way to create content

ROLLING OUT

Now you can create a new page with just one click. Browse or search for templates right in the editor or get straight to work on a blank page.

Sticky table headers won't scroll out of view

ROLLING OUT

Table headers will remain in view when scrolling down a table on a published page. This includes tables created in the new editor and those pages that were converted from the legacy editor to the new editor.

Easily find the slash command menu when editing a page or blog

ROLLING OUT

Finding the easiest way to do a thing quickly isn’t always easy to discover, so we’ve added some subtle hint text when you are editing a page or blog. This nudge will be there to help you remember how to get to the list of elements that can be inserted.

Always see the ability to add a new page comment

ROLLING OUT

As you scroll to the comments section of any Confluence page, the ability to quickly add a page comment stays stuck to the bottom of your window. Even while reading lengthy team discussions, it’s always simple to join in.

New permission: Admins can now let people delete their own content

ROLLING OUT

Space admins can now allow people to delete their own content, whether it be a page, a blog post, or an attachment. For any group or user that has the “Delete Own” permission checked, if they created the content, they can delete it. If they didn’t create it, they can’t delete it.

To delete any content they didn’t create, they still need to have the “Delete” permission checked for the respective content type.

By default, the “Delete Own” permission will be ON only for people in the groups “administrators” and “site-admins” in any new spaces created. It remain OFF by default for all other users, and will be OFF for all existing spaces.

The ability for people to delete their own comments is governed by the “Add” permission under Comments.

Improve the appearance of hyperlinks with Smart links and Smart cards

ROLLING OUT

You can use Smart links and Smart cards to make your links stand out while providing meaningful details that keep readers on your page. Learn more

We've hidden the Like button on archived pages

ROLLING OUT

When you archive a page, you’re signaling to your team that this page is outdated or otherwise no longer relevant to current work. Since no one should be paying attention to or engaging with these pages, we’ve hidden the Like button so no new likes can be added.

You’ll still be able to see all likes the page accrued up until it was archived.

Categories make it easier to find the right template

Being able to easily find a template that’s a perfect fit for your project can be exactly what you need to keep the creative momentum going. With categories that target roles, responsibilities, and concepts, you can quickly browse through the templates. Special categories group user-created templates, present third party templates from the Atlassian marketplace, and allow admins to promote certain templates.

Archive all nested pages in one action

ROLLING OUT

Page archiving enters its next phase with nested archiving. For any page you archive, if it has any nested pages, you’ll have the option to include all of them with the original page selected. Pages archived together will maintain their visual hierarchy in the archived pages list, to preserve the context in which they were organized in the page tree.

You’ll have the same option to include all nested pages when restoring any page in the archive back to the page tree.

You can use nested archiving on the premium plan.

New People menu dropdown in the navigation bar

The People menu in the new product navigation provides you with a quick way to see and get to the people and teams you work with most. You have the ability to create new teams from the menu and get to a directory of all people and teams. Learn more

Improvements to the people menu

ROLLING OUT

We’re gradually rolling out some tweaks to the People menu. The Invite your teammates button is now named Add people. You’ll find the button a little further up the menu.

When you add new users to Confluence from the Add People button, your site settings determine whether they’re invited or sent an access request.

Get a sense of how long it will take to read the contents of a page

ROLLING OUT

The estimated time it will take to read a page is shown at the top of each page. Read time is based on average reading speed of 265 WPM + 12 sec for the first image + 11 sec for second image and so on until the tenth image. Ten or more images each add 3 seconds to the read time.

Global app settings and functionality in one place (Android)

ROLLING OUT

We consolidated global app settings and functionality into one convenient place. You can now change settings and preferences for the app, quickly jump to another Atlassian app, and switch between Confluence sites — all from the new Account screen.

You can access the Account screen by tapping on your circular avatar in the top left of the app. Make sure you’re on the surface level of any of the four tabs along the bottom of the app: Your work, Spaces, Activity, or Notifications.

Recommending pages to archive

ROLLING OUT

We’ve added a notification email that’ll recommend archiving pages excluded by a bulk archiving action.

With the ability to archive a page and all of its nested pages (a whole branch of the page tree), sometimes not all pages in the branch can be included. This happens when the archiver either doesn’t have permission to view a nested page or doesn’t have permission to archive a nested page, which results in these pages being left behind in the page tree.

If you created any of these “left behind” pages, we’ll let you know in the email and give you a quick way to archive them!

Global app settings and functionality in one place (iOS)

ROLLING OUT

We consolidated global app settings and functionality into one convenient place. You can now change settings and preferences for the app, quickly jump to another Atlassian app, and switch between Confluence sites — all from the new Account screen.

You can access the Account screen by tapping on your circular avatar in the top left of the app. Make sure you’re on the surface level of any of the four tabs along the bottom of the app: Your work, Spaces, Activity, or Notifications.

Bitbucket

Manual Jira project link/unlink

ROLLING OUT NEW THIS WEEK

From now on, you’ll be able to manually link and unlink Jira projects from your repository. Learn more here.

Create issue on Jira issues tab

NEW THIS WEEK

This new feature allows you to quickly create a Jira issue against a project from the Jira issue tab.

Code Insights: Annotations in PR

ROLLING OUT NEW THIS WEEK

Follow up-to Code Insights, we are adding more direct ways to display annotations in the PR view diff. Learn more here.

Users can add a .gitignore file when creating a new repository

ROLLING OUT NEW THIS WEEK

You can now add a .gitignore file when creating a new repository, so common large file types (that don’t usually belong in a repository) will not be retrieved or displayed - meaning those files will not be added to the repository. By default, the ‘Include .gitignore’ option is set to ‘Yes’.

Bitbucket Pipelines: Enable git clone options at step level

ROLLING OUT

You can now enable git clone options at a step level. Check out the docs to learn more.

Automatically merge a pull request when all checks pass

ROLLING OUT

Sometimes it can take a while to get all the builds and reviews required by pull request (PR) merge checks, so the PR author has to keep checking back to ensure all the checks pass in order to merge their changes. Now in the new pull request experience, the PR author or an admin can enable this feature to queue up a pending merge to be triggered automatically once all the merge checks have passed.

Powered by Confluence and Scroll Viewport.