Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Jimi Wikman
    Jimi Wikman

    Atlassian Cloud changes Jan 6 to Jan 13, 2020

    Sign in to follow this  

    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 with the tag "atlassian cloud changes".

    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.png

    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.png

    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.png

    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 rolling out.png

    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.

    New user profile cards rolling out.png

    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 rolling out.png

    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.

    Advanced search (JQL): Search for content updated by a specific user

    Use the updatedBy() function to search for issues that were updated by a specific user, optionally within the specified time range. For example, if you want to find issues updated by John Smith between June and September 2018, enter issuekey IN updatedBy(jsmith, "2018/06/01", "2018/08/31"). Read more about the updatedBy() function.

    Search for and filter projects by their type with the "projectType" JQL field

    We added a new JQL field to search for and filter projects by their type. Type projectType to filter “software” (Jira Software) projects, “service_desk” (Jira Service Desk) projects, “business” (Jira Core) projects, or “ops” (Jira Ops) projects.


    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 rolling out.png

    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: Roadmap issue hierarchy rolling out.png

    You can now expand an epic on your roadmap to see its child issues and their statuses. Learn more about managing epics on the roadmap.

    Next-gen: Create child issues on your roadmap rolling out.png

    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.

    Next-gen: Environment system field in JSW

    Add Jira’s built-in Environment field to your issue types in next-gen projects. In your project, go to Project settings > Issue types and drag the Environment field into the Description section of the issue layout.

    Large backlogs load faster

    Big backlogs can take time to load, and teams usually work with a small chunk of the issues at a time. Knowing this and striving to make backlogs render faster, we've changed the default to display only 100 issues (90 from the top and 10 from the bottom) from your backlog. The remaining issues will be displayed if you click Show all issues.

    We've also introduced a number of backend changes that resulted in faster initial loading.


    Jira Service Desk

    Introducing multi-line fields to the issue view in next-gen projects  rolling out.pngnew this week.png

    You can now add multi-line fields to the issue view. These fields communicate long-form information to your team members and aren’t visible to your customers.

    To add multi-line fields, go to Project settings > Request types and add fields to the Description fields bucket.

    New issue view for Jira Service Desk  rolling out.png

    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.png

    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  rolling out.png

    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  rolling out.png

    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  rolling out.png

    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.

    Next-gen projects: Approve or decline requests  rolling out.png

    You can now add an approval stage to requests that should be approved before they’re resolved in next-gen projects. If a request has an approval stage, approvers can approve or decline the request from the issue view.

    Add an approval stage to a workflow by going to Project settings > Request types and then clicking Edit workflow. Learn more

    Global create can select request type and raise on behalf of  rolling out.png

    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.



    Your editing experience just got an upgrade  rolling out.png

    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  rolling out.png

    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  rolling out.png

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

    Confluence Cloud recent pages drawer  rolling out.png

    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  rolling out.png

    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.png

    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.png

    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.png

    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  rolling out.png

    When images are inserted in table cells, you now have the ability to align and resize them.

    Portfolio for Jira plan macro  rolling out.png

    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  rolling out.png

    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.



    New Code Review - Limit the amount of rendered diff content  rolling out.pngnew this week.png

    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

    Sign in to follow this  

    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By ©Jimi Wikman
      BigPicture 7 introducerar en av de bästa Program Boards för PI Planning med visuella beroende jag har sett. Det är bara en av de många nya features som BigPicture 7 presenterar och som vi kan se under våren 2019.
      BigPicture från SoftwarePlant har länge varit ett av de bästa alternativen till Jiras egna Portfolio for Jira och med BigPicture 7 så tycker jag att de tar klivet upp till en topp position för projekt portfolio plugins för Jira. Det är framförallt deras visuella board för program nivå som saknas i andra produkter, men det finns en hel del annat smått och gott också.

      BigPicture 6 hade en fantastisk översikt och även om man lägger till en ny vy så finns den gamla vyn kvar också. Personligen älskar jag den gamla vyn som för mig är en perfekt blandning av tidsplanering och översikt över det som utvecklas. Den nya vyn i BigPicture 7 är anpassad till SAFe.

      Scope Module ger en bra översikt och det enda som jag kan känna kan förbättras är själva trädstrukturen och listningen av issue types. Jag föredrar layouten som Portfolio for Jira har där issue types och trädstrukturen sitter ihop. Det ger för mig en enklare och tydligare översikt över strukturen och nedbrytningen.

      För mig så har BigPicture 7 den överlägset bästa översikten över resurser och kompetenser. Det är enkelt och lättöverskådligt att se vart det fattas kompetenser och resurser. Med funktionen att mappa in kompetenser i Jira ärendena direkt får du rätt översikt (nästan) alltid. Det gör också att det blir mer naturligt att bryta ner ärenden så det blir rätt typ av aktiviteter.

      Board 2.0

      BigPicture 7 kommer med en ny board, fast den följer samma fantastiska layout som i BigPicture 6. Nytt är att den nya boarden är anpassad för just PI Planning enligt SAFe standard. Det här är en vy som ofta efterfrågas och som saknas stort i Jira idag. Det här är för mig den stora säljpunkten för BigPicture 7 för den här funktionen är verkligen spot on som man säger.
      Gant Chart 2.0

      Alla älskar en bra Gant Chart och BigPicture har alltid haft en av de bästa för Jira. I BigPicture 7 så introducerar man två nya funktioner som efterfrågats av kunderna: Live Sync och Sandbox.
      Live sync är egentligen lite missvisande för det handlar om kollaborativ editing. Nu kan flera användare jobba samtidigt utan att riskera att förstöra något för de andra. Du behöver inte längre trycka på uppdatera och hoppas att ingen annan gjort något som ställer till det. Nu ser du allting när det händer. Ungefär som collaborative editing i Confluence med andra ord.
      Sandbox låter dig experimentera med din planering utan att påverka den aktiva planen. Du kan göra olika scenarion och sedan implementera den du gillade bäst när du så önskar. Det gör det möjligt att direkt se hur olika förändringar slår på olika områden utan att du behöver oroa dig för att det ska påverka den aktiva planeringen. Ett ovärderligt verktyg för att hantera oplanerade ändringar med andra ord.
      BigPicture 7 kommer under våren 2019 och senare under 2019 kommer BigPicture 7.5 som innehåller Portfolio Management Module som ger Full Safe i BigPicture. Du kan läsa mer om detta och detaljerna för BigPicture 7 på SoftwarePlants hemsida.
      Personligen tycker jag att detta är den största om mest intressanta uppdateringen bland Jira plugins hittils under 2018. BigPicture 7 ser ut att bli en stor hit under 2019 och jag kommer självklart att skriva mer om det så fort jag vet mer eller har haft möjlighet att prova på. Ganska troligt att BigPicture 7 kommer att bli ett ämne för Atlassian User Group Stockholm också under 2019.
      Vad tycker du om BigPicture 7 av vad du ser här och hur gillar du BigPicture 6 om du använt det?
    • By + MilosK
      Miloš is a calm and organized e-commerce developer skilled in Java (especially hybris) and web application development with a strong interest in software engineering, continuous delivery and automation. Miloš is social and quickly adaptive to a new environment or a role. His good analytical and critical thinking helps Miloš to adopt an objective view on a given task. Miloš is focused on details, eager to face new challenges and always strives to help the team with self-improvement and optimization.
    • By ©Jimi Wikman
      A Demo of Jira Align by Kevin Yao.
    • By ©Jimi Wikman
      Portfolio for Jira and it's third iteration that was released in April 2019 has some great features. In no less than 18 releases since the main release Portfolio for Jira has grown into a powerful tool to manage projects and programs in Jira. This is a summary of the biggest features released for Portfolio for Jira 3.0.
      Set a plan that reflects your reality
      One of the most difficult aspect of managing teams in Jira is to get a holistic overview. Using Portfolio for Jira this becomes much easier and in 3.0 it becomes even easier as you can adjust your plan by dragging and dropping issues to designate or reassign their parents, reorder them based on priority, and set timelines for their execution to generate a roadmap your teams can really get behind. All data is in real time so you can always get that holistic overview you need.

      Constantly evolve and respond to change
      With Portfolio for Jira 3.0 you can can visualize cross-project and cross-team dependencies to proactively navigate pitfalls and continually adapt plans, forging a clear path forward to help your team deliver on time. Get the data you need to adjust plans and drill down into the latest changes when ever you need to.


      Consistently communicate and share the best of your plan
      A variety of display options allow you to share updates with the right level of detail tailored to your audience and keep everyone on the same page, even as plans evolve. And because plans are open to everyone in the organization using Portfolio, individual team members can see how their work connects to bigger-picture initiatives, while management can see when work is forecasted to ship.

      Following the launch of 3.0, highly requested fields such as Priority and Parent are added to give you even better detail of the work. In addition to this you also will find a new field called progress that track the completed work based on estimates (days, hours, or story points) for all the descendants of a given issue. This is displayed based on both completed and partially completed issues for which time has been logged against the estimated workload.
      Five additional fields are available with Portfolio for Jira 3.0. These are Checkbox, Radio button, User picker (single user), URL (read-only), and Label. You can use these to further add data to your overview.

      Bulk actions
      Five bulk actions have been added to Portfolio for Jira 3.0. Fields that can now be manipulated in bulk include Target start, Target end, Assignee, Sprint, and Issue rank. Clean up your plan by removing or reranking issues, or set dates all in one go.

      With Portfolio for Jira 3.0 there are now filtering support for Jira standard fields Assignees, Sprints, Issue sources, and Issue types. There are also filtering for custom fields such as Single-select, Label, and Radio button, but it still in progress so expect this to be expanded in future updates. These new filter options makes it even easier to get the view you need.

      View settings
      With support for coloring, grouping, and general display of information in your plan you add meaningful context and a greater dimension to your data. This will make thins more clear as you track progress or share your plans with others.
      The new view settings now have the ability to roll up sprints on the timeline, new sorting capabilities (sort by Dates, Status, Sprint, Estimate, and Priority), and the new grouping options (group by Label, Release, Sprint).

      Portfolio for Jira plan Confluence macro
      In an effort to expand on the options for sharing Portfolio plans, in version 3.12 we announced the arrival of the “Portfolio for Jira plan” Confluence macro, which enables users to embed lightweight Portfolio for Jira plans directly within Confluence pages. It’s yet another way to keep everyone on the same page, even as plans evolve.

      Other notable improvements
      Impressions so far
      Portfolio for Jira is by far the most useful overview for day to day operational management of Jira projects. Where Jira align is useful for Portfolio management on a strategic level and Roadmaps for Jira Cloud give a different visual overview on a team level, Portfolio for Jira give the operational overview.
      The continued improvement of Portfolio for Jira 3.0 has continuously made this experience better and easier to work with. As we see more and more organizations start to implement SAFe into their way of working, Portfolio for Jira still is the best way to implement this on an operational level.
      If you have not tried Portfolio for Jira I strongly recommend that you give it a test run. It is an amazing addition to your Jira instance if you are serious about portfolio management on an operational level.
      More information on Portfolio for Jira can be found here:
      Portfolio for Jira | Atlassian
      WWW.ATLASSIAN.COM With Jira Software and Portfolio for Jira, you can combine your long-term planning and agile development to get visibility at...  
  • Create New...