This is a repost from Atlassian's blog where the latest updates to the Atlassian cloud platform is posted. It is reposted here since the Atlassian blog does not have an RSS feed and so we can discuss the changes to the Atlassian Cloud architecture. You can follow these posts withe the tag "atlassian cloud changes".
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.
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.
Create roles to fine-tune permissions and access in your next-gen projects
Roles allow you to fine-tune how people access and interact with your project. In real life, people play different roles in your project work. Your team may have a dedicated Scrum master, or you may work with consultants or contractors.
In Jira, different roles may need limited access to the content of your team’s work. Or, you might want to limit what some people are able to do in your project. For example, you may want to allow only your team’s Scrum masters to plan and manage your upcoming sprints. Or, you might want to prevent a consultant from changing an issue’s status.
In next-gen projects, you can tweak the way people interact with your project by creating your own roles with specific project permissions. Then, when you add people to your project, you can assign them a role to ensure they interact the way you expect them to.
To try it out, go to Project settings > Access in your next-gen project (Project settings > Internal access in your next-gen service desk).
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).
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.
Find issues you've recently worked on
We’ve added a new Worked on tab to the Your work page. This tab lets you quickly find and resume work on issues you’ve updated recently. Head to Your work > Worked on to get started.
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.
Jira admins: Get more insights into your projects
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.
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 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.
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!
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!
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.
Ancestor filter on the new advanced search page
You now have an additional filter when using advanced search that lets you narrow the results to pages under the page you selected. This is great when you have a general idea of where the page is that you want, but you can’t remember exactly where.
As a start, Frontend will be be breaking down the contributors to 2 parts, first get the top 2 avatars and then on ‘load more’ will do get the all rest of contributors.
Current limitation: Frontend uses Atlaskit component Avatar groups to show the avatars in contributors, but it doesn’t support pagination right now. A improvement request has been made and once they support it, we can modify the page contributors to have true pagination.
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.
End of support for nested tables
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
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.
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.
Create a Jira issue from a pull request comment
You can now create a Jira issue from a pull request comment. This new feature also enables you to choose the project where you will create the issue.
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