Atlassian Cloud changes Mar 25 to Apr 1, 2019
These changes have recently been rolled out to Atlassian Cloud sites.
Anything with a 
is new this week.
Changes with a 
are steadily rolling 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.
New design for the self signup page
We're rolling out updated user management pages with a new, cleaner design. Functionality remains unchanged, they're just nicer to use! Read about managing product access for your users.
Email users with suggested account changes
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
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.
Pay with PayPal
You can now add Paypal as your method of payment.
When you're adding your billing details to your organization or site, you'll see the option to Pay with PayPal on the Payment method screen.
Update to IP ranges used by Atlassian outbound proxy
Updates to our infrastructure have added more IPs to the range of official Atlassian IPs. If you configure any IP whitelists for Atlassian sites or applications, you should update those lists now.
You can track the list of all Atlassian IPs at ip-ranges.atlassian.com
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.
New issue view: Full-page issue view for business projects
The simplicity and consistency of the new issue view, which we've already released to boards (and backlogs for Jira Software), is here for the full-page issue view. Use the quick-add buttons to add attachments and subtasks, or link issues, in a flash, and edit everything you see inline.
Removing anchors and the lorem ipsum macro from content in the new issue view
We're making some under-the-hood changes to improve rich text content— mainly descriptions and comments—in the new issue view. As part of this process, we've decided to remove anchors and the lorem ipsum macro from rich text fields. This means that any existing links to anchors in Jira content will no longer work.
As content in Jira is usually in smaller chunks, we believe this is the right decision to simplify the editing experience, and lets us keep moving forward with other content enhancements. If you have feedback to share on this, reach out to us on the Atlassian Community.
Filter issues in your project's issues list
We've added a text filter above the issues list in your project to help you find the issue you're looking for more quickly. In a project, go to Issues and filters and add a search term in the filter field above the list of issues.
Required encoding of some characters for Jira Cloud REST APIs
As part of our continued focus on the security of our Cloud platform, and our recent Tomcat update, we're introducing changes that'll require the encoding of some characters used in REST API calls. Read the change notice for more information and relevant dates.
Assign a default value for your next-gen project fields
Automatically fill in fields with a default value when someone creates an issue in your next-gen project. To give a field a default value, go to Project settings > Issue types and select the fields you want to update.
New issue view: See work log entries
See the amount of time spent and each work log entry in the new issue view. Click the Comments drop-down menu and choose Work log to get started. Coming soon: Edit and delete work log entries.
New issue view: Confluence page links
See Confluence pages an issue is mentioned on in the new issue view.
Coming soon: Add a link to a page with the Confluence page quick-add button underneath the issue summary.
You need a Confluence site linked to your Jira site to use this feature. Haven't tried Confluence yet? Try it free to see how it can help your team collaborate more effectively, and ship projects faster.
Removal of Jira legacy mode from time tracking
We've removed the option to enable Jira legacy mode in time tracking settings. This change won't affect most of you, but you can find out more in the announcement blog post.
Jira Software
We're rolling out next-gen and incident management projects. By default, any Jira Software licensed user can create their own next-gen project, and any Jira Ops licensed user can create their own incident management project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen and incident management projects with the new Create independent projects global permission. Read more about next-gen projects.
New issue view for Jira Software
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). We're rolling this out gradually, so you may not see it on your site just yet. Take a look at the documentation for more info and watch the page to be updated when we release new features.
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.
New issue view: full-page issue view for software projects
The new Jira issue view, which we already released for boards and the backlog, is now here for the full-page issue view. Quickly add attachments and subtasks, link issues, and click to edit any field you see. Check out this page for more info.
To turn off the new issue view for now, go to your avatar > Personal settings and toggle the switch for the New Jira issue view.
Next-gen projects: Create new issues anywhere on the backlog
You can now create an issue anywhere on the backlog of your next-gen project, including at the top, at the bottom, or between any two issues.
Jira Service Desk
Meet the new help center
We have exciting things happening in the help center. Check out our blog to learn what's coming!
Customize how work flows in your next-gen projects
Control how your team's work flows in your next-gen project. You can define exactly how tasks move from to-do to completed by adding statuses along the way. Give people instruction of how work should progress by adding transitions or pathways between your statuses. And, power up your project's workflow by adding rules to automate repetitive actions you'd make when moving issues.
Try it out in your project settings. Go to Project settings > Request types. On your issue type settings, click the Edit workflow button.
New issue view for Jira Service Desk
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.
Confluence
Atlassian profile and people directory
We're bringing the new Atlassian profile to Confluence. Soon you'll have a single profile for all the Atlassian products you use on your site, including Jira, Confluence, and Bitbucket. To do this, we've consolidated the information in your Atlassian account and your Confluence profile and removed or replaced redundant fields. We've also moved the profile tab out of Settings and into the menu you access from your avatar.
Finally, we've deprecated the Confluence people directory and replaced it with a one that works across all your Atlassian products. You can access the new people directory via the App Switcher.
Blogs are getting the first round of editing improvements
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.
All collaborators now get credited as page authors
The person who starts a page isn't necessarily the same person who finishes it, and if more than one person have been working on something together, we think they all deserve credit for what they created. That's why we're changing the byline on Confluence pages so that they now include all the collaborators, not just the person who first created them.
Meeting notes are getting a makeover
We're continuing to work on improving your editing experience, and next in line for an upgrade is meeting notes. In addition to being faster and more reliable, your new meeting notes are also responsive, optimized for readability, and have advanced tables. Some macros are still temporarily missing as we rebuild them, but you can check the list and find more details on all of these changes from our docs site.
Drag and drop for quick and easy space reorganization
Move a single page or reorganize an entire space - directly through the space sidebar, using drag and drop.
Click and hold a page in the space sidebar to pick it up, drag it to a new location in the page tree, and drop it to move it there.
Teams have arrived in Confluence retrospectives!
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.
Bitbucket
Only allow admins and specific branches to deploy
We've heard that people would like some more control over who is allowed to deploy to their environments. With this in mind, Premium plan customers can now restrict deployments to admins, or to specific branches. These settings can be configured individually for each deployment environment. Learn more