Atlassian Cloud changes Nov 4 to Nov 11, 2019
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.
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 changesROLLING 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 permissionROLLING 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 domainROLLING 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.
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.
New user profile cardsROLLING OUT
When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it).
New issue view: Rich user profile cardsROLLING OUT
Get to know your team even faster. Our new user profile card provides more user information and a link to the user’s profile (if you have permission to see it). You’ll see it when you hover over someone’s name in user-picker fields (assignee, reporter, and other custom fields) and in issue activity feeds (comments, history, and the work log).
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.
New issue view for Jira SoftwareROLLING OUT
Get a consistent view and edit experience with our new issue view for Jira Software. Click an issue to see its details, edit any field with a click, and add content with the quick-add buttons (under the issue summary). Take a look at the documentation for more info.
We're adding new features and refining the design all the time, so click Give feedback on the issue view to let us know what you think.
GitHub app on the Atlassian MarketplaceROLLING 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.
Jira Service Desk
Issues with the customer organizations field now use the organization name instead of ID when exporting to CSVROLLING OUT NEW THIS WEEK
When exporting Jira issues to CSV from the Jira Issue Navigator, the Custom field (Organizations) now contains the name of the organizations linked to the issue. The field previously contained the organization ID, which was not valuable for exports used for reporting.
As part of this change, a CSV import can now match organizations by both their ID and their name. No changes are needed if you use CSV export files for import.
Maintenance complete on the Request and Approvals pagesROLLING OUT NEW THIS WEEK
We've completed some maintenance to the customer portal, you may notice some cosmetic updates to the Request and Approvals pages.
New issue view for Jira Service DeskROLLING 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 queuesROLLING 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!
Customer portal request details page redesignROLLING OUT
We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes.
Easier configuration for the new issue viewROLLING OUT
If you have the new issue view, you can now easily configure how your issue view looks for each request type.
From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes.
Improved interface for your customer portal settingsROLLING OUT
We’ve given the customer portal page in your project settings a visual overhaul. Settings are under suitable headings, text sizes are aligned, and overall, the page has a cleaner interface. Don’t worry, we haven’t removed any functionality.
To see the new design in a classic project, go to Project settings > Portal settings.
To see the new design in a next-gen project, go to Project settings > Channels > Customer portal.
Portfolio for Jira plan macroROLLING OUT NEW THIS WEEK
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.
Blogs are getting the first round of editing improvementsROLLING OUT
If you've ever thought 'I wish it was easier to read blogs on mobile.... or on other devices', then this change is for you. Blogs are getting fixed-width layouts to improve readability across all devices. We're making a bunch of other updates to improve editing reliability and clean up your editing experience, so some macros may be temporarily unavailable while they're under maintenance. You can read more about these changes on our docs site.
Teams have arrived in Confluence retrospectives!ROLLING OUT
Instead of having to individually add each member of your team to a retrospective, Confluence now lets you assign people to Teams, so you can bulk add everyone at once.
Use the retrospective template to see Teams in action. You can edit Teams through the retrospective-creation process, and add or edit other attendees for each retrospective you create.
We're extending editing improvements to all pages on AndroidROLLING 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.
Confluence Cloud recent pages drawerROLLING OUT
We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft.
Share pages directly with your teamROLLING 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
Retarget stacked Pull RequestsROLLING OUT NEW THIS WEEK
Bitbucket will retarget the dependent pull requests to the branch that you're merging into, before closing the branch of the pull request you're merging. Previously, if there were dependent pull requests, you needed to update them manually with the new target branch. You will now see a checkbox with a link to the affected pull requests that will be retargeted.