atlassian cloud changes Atlassian Cloud changes Jan 27 to Feb 3, 2020
By
💫 Jimi Wikman ·
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
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.
Claim accounts after verifying a domain
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.
Set your language and time zone for Jira and Confluence in your Atlassian account profile
Rather than individually setting your language and time zone in Jira and Confluence, these preferences will soon come from your Atlassian account profile. Visit your account preferences to update these settings. It may take up to 10 mins before your updated preferences are reflected in Jira and Confluence.
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.
Jira admins: We made a change to time tracking
Time tracking is a core feature of Jira Cloud products. We’ve looked into how people use this feature and found that the large majority of Jira Cloud sites never interact with the feature’s toggle or try to disable the feature. So, we removed its toggle in Jira’s system administration settings.
From now on, time tracking is always enabled in Jira Cloud products.
You can control whether the feature is used in your projects by:
Showing or hiding the Time tracking field in your classic projects' field configurations. Learn more about field configurations. Adding or removing the Time tracking field on your next-gen projects' issue types. Learn how to customize an issue’s fields in next-gen projects. New user profile cards
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).
Tame your site’s custom fields
See the number of custom fields on your site, so you know if they’re getting out of hand. We've introduced icons to illustrate each type of custom field so you can easily identify them. We’ve also grouped screens and contexts for each custom field into a single Screens and contexts column to make them easier to edit and make the page more readable. Head to Jira settings > Issues > Custom fields to check it out.
Click a field’s screens or contexts links to:
Edit its name and description. Associate it with screens. Create, edit, or delete contexts. Set or edit its default value. Learn more about custom fields.
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.
Having trouble with next-gen projects? Better help is here.
We improved our in-product help experience. Try the Help button in the navigation bar to see help articles related to your next-gen project or service desk.
Change Jira wallboards background color to black
This change is to fix the problem identified in the issue JRACLOUD-73231. Wallboard backgrounds are now black to improve the visibility of gadgets.
Portfolio for Jira - Team Offset Change
Portfolio has changed how it schedules work for teams to better reflect planning reality.
Previously, if one of the teams in the plan had an active sprint that had already started in the past, Portfolio would schedule work for that team in the past. However, just because that team had an active sprint that’s already started, Portfolio would go ahead and schedule work for other teams in the plan, even if these teams didn’t have an active sprint that’s started in the past.
We’ve changed this so work will no longer be scheduled for the other teams in the plan that don’t have an active sprint. Rather, Portfolio will now schedule work for these teams starting the next day.
Portfolio for Jira - Scheduling Team Sorting
When scheduling work, Portfolio now prioritizes teams that have associated issue sources over teams that don't. Also, teams without issue sources will only be considered if they have capacity to complete work earlier.
Portfolio for Jira - Scheduling with Adapted Sprint Dates
Previously, the capacity of the last day of a sprint would be fully allocated to the sprint itself. This makes a 2-week sprint on a board have 11 work days of capacity in Portfolio.
We've now improved capacity calculation so that the capacity of a sprint's last day will no longer be allocated to the sprint itself. A 2-week sprint will now have 10 work days of capacity.
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
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.
Next-gen: Create child issues on your roadmap
You can now add child issues directly on your roadmap. Just hover over an epic, click the + icon, and give your issue a name. Learn more about managing epics on the roadmap.
Jira Service Desk
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.
Use keyboard shortcuts in your queues
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 redesign
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.
Maintenance complete on the customer portal user profile page
We have just completed some maintenance on the customer portal user profile page.
We also introduced a new layout that is easier to use on mobile devices. Go team!
Easier configuration for the new issue view
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.
Global create can select request type and raise on behalf of
You can now create a request on behalf of your customers and set them as the reporter. Use the global create button ( + ), then select Raise this request on behalf of and add in your customer's email.
Automatically clear the value of a request's field when changing its status in your next-gen service desk
We improved our “Update a request field” workflow rule. Now, you can use the rule to clear your request’s fields when someone moves the request using a specific transition.
Confluence
Your editing experience just got an upgrade
The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more.
We're extending editing improvements to all pages on Android
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.
Convert legacy editor pages to the new editor
Our goal is to allow you to convert your pages from the legacy editor to the new editor without data loss and with little to no changes to the look and feel of the content, which is why you’ll have control over which pages get converted and when. You'll also have the option to preview any page before converting it. We want you to feel comfortable with the process. You'll also have the chance to restore a page to its previous, legacy editor version after conversion. Learn more
Annotate images in the new editor
Annotate images by adding text, inserting shapes and lines, using brushes, or adding a blur to a certain area.
Confluence Cloud recent pages drawer
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 team
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
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
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
Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more
Align and resize images in tables in the new editor
When images are inserted in table cells, you now have the ability to align and resize them.
Portfolio for Jira plan macro
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.
Improved expand element replaces the macro
Content creators just got a better way to control the way information is presented. The existing expand macro has been replaced with a quicker, easier way to include the expand functionality. Insert the improved expand element using /expand or by inserting the element from the editor's Insert toolbar.
Bitbucket
Bitbucket Cloud: App Management UI Refresh
The Connect App authorization screens have been updated to adopt the latest UI patterns documented in the Atlassian Design Guidelines.
New Code Review - Limit the amount of rendered diff content
Limits the amount of pull request content rendered in the diff and file tree to improve browser performance. Limits include the overall # of files and # of lines for the entire diff. Learn more
