Atlassian Cloud changes Jun 15 to Jun 22, 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.

Claim accounts after verifying a domain

ROLLING OUT

To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain.

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.

Next-gen: Check a request's field before allowing agents to transition it

ROLLING OUT NEW THIS WEEK

In your request type’s workflow, you can add a rule to automatically check the value of your request’s fields before allowing agents to transition the issue. This workflow rule can help make sure your team dots all the i’s and crosses all the t’s before closing out your customer’s request.

For example, you can check to see if a service team member has checked a Verified checkbox before allowing notifying your development team of problems with your software. See more details and examples on how to use this rule.

To try out the Check a request’s field rule:

  1. If not already there, navigate to your next-gen service desk.
  2. From the sidebar, select Project settings > Request types.
  3. From the sidebar, select the request type whose workflow you want to add the rule to.
  4. Select Edit workflow. The workflow editor appears.
  5. From the toolbar, select Rule.
  6. Select Check a request field and click Select.
  7. Choose the transition to add the rule too.
  8. Select the field you want to check, and complete some details about how you want to evaluate the field.
  9. Click Add.

Jira admins: Get more insights into your projects

NEW THIS WEEK

We’ve added a Last Issue Update column to the Jira Settings > Projects page. This column displays the most recent date when someone updated an issue—just to give you an idea of what’s going on with the projects.

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

Improved navigation in Jira Cloud

ROLLING OUT

We’ve created an improved navigation experience that always appears at the top of the screen, with clearly labeled buttons and menus to help you search, create, and resume your work. Find out more about our improved navigation experience and when you can try it out.

We’ve started the process of moving everyone over to our improved navigation experience. Read more about the process and timing.

Trash for Jira Software and Jira Core projects

ROLLING OUT

Accidentally deleting a project causes irrevocable data loss. We heard your concerns and we’ve changed the way you can delete your projects. To provide a safety net each time you delete a project, we’ve introduced a trash for projects. As Jira admins and project owners, you’ll have to move your projects to trash before you can permanently delete them. Projects remain in trash for 60 days after which they are permanently deleted.

Only Jira admins can access trash. From the trash, Jira admins can:

  • Restore a project that was moved to trash
  • Permanently delete a project
  • View when a project was moved to trash
  • View the user who moved the project to trash
  • View when a project will be permanently deleted

Learn more about moving projects to trash.

New issue view: Individual scrollable sections

ROLLING OUT

When viewing an issue with two columns, where the issue details fields are displayed on the right and the content is on the left—usually in full page, on a board, or in issue search—each section is individually scrollable. Why is this important? It means you can view the issue status and other fields at the top of the right column even when you’ve scrolled through a long description on the left; or see the description when you’ve scrolled through a long list of issue fields in the right column.

This is a small change, but we think it’ll make it easier to work with issues with lots of fields. We have more changes coming to help you work with busy issues. Find out more about the new issue view.

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.



Bug fix: Use the current page's JQL query for bulk operations

ROLLING OUT

This change addresses a bug described in JRACLOUD-39420, where running JQL searches in multiple tabs then starting a bulk edit could result in the wrong list of issues being passed to the bulk editor. Now, the bulk editor will use the JQL from the page where you initiate the bulk edit in most cases*.

Read more about advanced searching with Jira Query Language (JQL).

*This relies on adding the JQL query as a URL parameter. Some browsers limit the length of URLs, which means for some complex queries Jira will fall back to the most recent stored query.

Improved issue search in classic projects

ROLLING OUT COMING SOON

Find your work fast with new search filters and an improved issues list in the project issue navigator. You can now filter the list of issues by assignee, reporter, status, and type, to help you find exactly what you need. Pre-defined filters are still in the sidebar, but this change means you can start with a pre-defined filter—like Open issues—then use the new filters for an even more specific search.

A couple of other changes to note:

Rather than Issues and filters, the navigation item in the project sidebar is now Issues. We believe issues are what you’re looking for when you use the issue navigator, so “issues” is more descriptive.

We’ve also changed the default view in the issue navigator to All issues, ordered from newest to oldest (by created date). Many of you told us that you wanted to quickly find new issues, so this should help out. Because that’s now the default, we’ve removed the Created recently filter. When you arrive in the issue navigator, or you choose All issues, you get recently created issues anyway.

Learn more about searching for issues in Jira.

Automation for Jira: Create automation rules from the board

ROLLING OUT

We’ve added a new Automation button above your board, allowing you to quickly create project automation rules without leaving the board.

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.


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.

Jira Software Premium: Archive your projects

NEW THIS WEEK

Stay organized by archiving your inactive projects. Jira admins and project admins can archive projects along with all related issues, components, and attachments. To archive a project, go to the projects directory and then click ••• to select Archive. Learn more about archiving a project.

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.

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


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!

Jira Service Desk link multiple incidents to a major incident

Connect all related incidents quickly and easily by linking several incidents to a single major incident in one go. Simply tick the checkbox beside each incident in the queue then click link.

Confluence

Your editing experience just got an upgrade

ROLLING OUT

The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more.

End of support for nested tables

ROLLING OUT

As we work on creating a more stable editing experience, we will no longer support nested tables - that is, a table within a list, block quotes, or another table. Existing nested tables will not be affected, you simply won't be able to create new nested tables.

We're extending editing improvements to all pages on Android

ROLLING OUT

The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site.

Enhance your images when using the new editor

ROLLING OUT

Annotate images by adding text, inserting shapes and lines, using brushes, or adding a blur to a certain area.

Share pages directly with your team

ROLLING OUT

It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more

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

Confluence navigation just got better

ROLLING OUT

Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. 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.

New locations for attachments and lock icons on pages

ROLLING OUT

A couple of page icons have new locations.

We’ve moved the lock icon on a published page next to the Share button to strengthen the relationship between the two (you can’t successfully share a page with someone who doesn’t have permission to view it) and to align with the lock’s location on a page in edit mode.

Lastly, you can now find the attachments icon in the more actions menu (•••).

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.

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.

Date element improvements in the new editor

ROLLING OUT

It’s now possible for you to type in the date when adding the Date element to a page in the new editor. This reduces the need to click through the calendar to find a date you want, which also makes this action more accessible for all people.

Find and replace text in the new editor

When editing a page, blog, or template, you can use the find and replace action to make the necessary changes.

Matches are highlighted on the page. You can step through the results one by one, replace the matching text strings one by one, or replace all matching strings at once. Find and replace works only within the current page.


Bitbucket

Transition Jira issues during pull requests merge

NEW THIS WEEK

From now on, you can transition a Jira issues status from a pull request when you merge it.

Two-step verification account recovery

NEW THIS WEEK

Users can now self-serve their Bitbucket account recovery if they forget or misplace the two-step verification credentials and emergency recovery codes. For more information on two-step verification, check out the Two-step verification help doc for Bitbucket Cloud.

In-product signup for Atlassian products

ROLLING OUT

You can now sign up for other products from within Bitbucket via the product switcher. The Atlassian product switcher will display a list of products that you haven’t signed up to yet.

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.

Powered by Confluence and Scroll Viewport.