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

    Atlassian Cloud changes Jan 20 to Jan 27, 2020

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

    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.

    See location details in the audit log  new this week¨.png

    The audit log has a new Location column that displays the IP address where the activity took place. Read more about audit logging.

    Email users with suggested account changes  rolling out icon.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 icon.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 icon.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 icon.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 icon.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 icon.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.

    Having trouble with next-gen projects? Better help is here.  rolling out icon.png

    We improved our in-product help experience. Try the (question)Help button in the navigation bar to see help articles related to your next-gen project or service desk.

    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.

    Portfolio for Jira - Scheduling Team Sorting  rolling out icon.png

    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.

     

    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.

    Enforce CSFR protection on Agile 2.0 mutations new this week¨.png

    If a user attempts to perform any JSW create/update action with a stale Xsrf token, they will be presented with an error flag with a message:

    Our session has expired
    Refresh the page and try again

    GitHub app on the Atlassian Marketplace  rolling out icon.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

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

     

    Jira Service Desk

    Automatically clear the value of a request's field when changing its status in your next-gen service desk rolling out icon.png new this week¨.png

    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.

    New issue view for Jira Service Desk  rolling out icon.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 icon.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 icon.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 icon.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 icon.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.

    Global create can select request type and raise on behalf of  rolling out icon.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.

     

    Confluence

    Convert legacy editor pages to the new editor rolling out icon.png new this week¨.png

    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

    Your editing experience just got an upgrade  rolling out icon.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 icon.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 icon.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 icon.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 icon.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 icon.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 icon.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 icon.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 icon.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 icon.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 icon.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.

     

    Bitbucket

    New Code Review - Limit the amount of rendered diff content rolling out icon.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

    Edited by Jimi Wikman




    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.

    Guest
    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
      Atlassian and Mindville announced on thursday that Atlassian has acquired Mindville.  This means that Atlassian acquire Mindville's asset and configuration management product Insight, which strengthen their psoition against competitors like ServiceNow.
      The CEO of Mindville Tommy Nordahl is well known to us in Stockholm who have participated in the Atlassian Usergroup events that I ran for two years. For many he is Riada, the company he started many years ago as the Atlassian company number one in Stockholm (and sweden?). Lately he has focused more on the asset and configuration managament product Insight and I am not surprised that Atlassian now have aquired it.
      Atlassian and ServiceNow are both gearing up for a battle. Since ServiceNow are strong in the asset and configuration management it makes sense that Atlassian want to stregthen their portfolio in their area.  With more than 1700 customers already and Atlassian now adding resources I think we will see the cloud adaptation speed up a lot.
      If you have not looked at Insight before, then I suggest you do. Not only is it looking great and is easy to work with, it is also powerful and a very useful addition to your support organization. Using Insight alongside Jira Service Desk and Confluence is probably the most powerful way to manage incidents in your organization. The fact that you can directly connect it to your development and opertions team who already work in Jira make it even more powerful.
       
       
      I just want to say congratulation to Tommy and his amazing team for this accomplishment. To Atlassian I can only say good job on this acquisition. It will take you another step closer to being the natural choice for mid sized and large organizations, just as you already are the natural choice for small companies and all development teams today.
    • By ©Jimi Wikman
      I was the team lead for the front end development team doing the redesign of all H&M brands on the new Hybris platform.

      Working with H&M we needed to build a new way of working within Accenture as we had 3 companies that had never worked together before: Fjord, Brightstep and Accenture Italy. I built a completely new delivery workflow from design to frontend and then to backend in Jira and Confluence. In total I spent over 500 hours building and training the teams with great result. This was extra difficult due to the fact that we built design for 6 brands and one was under NDA and not open to Fjord for one of the projects.

      We also built a pattern library so we could work according to atomic design for both development and design. This was accompanied by a delivery pipeline to the backend team for a very smooth development process.
    • By ©Jimi Wikman
      My assignment was to review and build a new work process with JIRA & Confluence as tools for the development efforts at Axfood. Based on the SAFE agile process with practical experience in making projects actually become a reality I built a process that was custom made for Axfood and their specific challenges.
    • By ©Jimi Wikman
      Going over requirements and making time estimations and technical solutions for the front end part of the project.
    • By ©Jimi Wikman
      Jira tool manager with the task of stabilizing the system and setting up work processes for all teams within H&M. Responsible for several projects including cloud initiatives and coordination with other systems such as ServiceNow. Heavily involved in designing the build processes (requirements, development, design, deploy and test) for the process office. Responsible for the design and implementation of SAFe in Jira and the build processes. Responsible for a small team of Atlassian experts. Supported 400+ teams with Jira questions and training of work processes.
×
×
  • Create New...