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

    End of support for Confluence gadgets - four gadgets are being deprecated in May

    • Interresting 1
       (0 reviews)

    Atlassian is ending their support of four gadgets for Confluence Cloud at the end of May. The gadgets will still work after that if you are already using them, but you will not be able to add them into the legacy editor or the new editor using the macro browser, slash command, or a shortcut key. Three out of four gadgets are replaced with macros.

    Quote

    Gadgets were designed to allow you to display information dynamically from sources like iGoogle or Jira, for example, in Confluence. The first gadgets were introduced in the early versions of Confluence Server, and much of the technology they used is now obsolete. Since then we have also implemented a number of better ways to display dynamic information using macros and other integration points.

    The time has come for gadgets to fade away and be replaced by the more modern macros for Confluence Cloud. While the gadgets will still work on your confluence pages, you will no longer be able to add them to pages. That goes for legacy and new editor as well as for macro browser, slash command and shortcut. If you want similar functionality then there are macros suggested for all but the news gadget.

    Activity Stream gadget

    The Activity stream gadget shows a list of recently changed content in your site. Atlassian recommend using the Recently Updated macro as an alternative in Confluence. 

    Confluence Page gadget

    This gadget displays the contents of a Confluence page. Atlassian recommend using the Include Page macro as an alternative in Confluence.  

    Confluence Quick Nav gadget

    This gadget provides a search field that can be used to search for page titles in Confluence. Atlassian recommend using the Livesearch macro as an alternative in Confluence. 

    News gadget

    This gadget previously displayed blogs and other news from Atlassian. It has no suggested alternative.

     

    End of support means that Atlassian will no longer fix bugs for these gadgets. If your Confluence site is integrated with a Jira site, any Jira gadgets installed in Confluence ARE NOT IMPACTED by this change. You can continue to insert Jira gadgets into any Confluence page.


    • Interresting 1


    User Feedback

    Join the conversation

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

    Guest

  • 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
      The requests to get Portfolio for Jira for Cloud users have been loud and finally Atlassian released a Cloud version. They also made a very odd choice to rename Portfolio for Jira to Advanced Roadmaps and place it behind the Cloud Premium barrier.
      Portfolio for Jira has long been the better choice for Jira Server and Jira DC users. The features have been perfectly suited for managers to keep an overview over large programs and initiatives with relative ease. As such it has been the envy of Cloud users for years and it comes as no surprise that Atlassian would port this to Cloud given their focus on the cloud platform lately.
      Renaming Portfolio for Jira is also no surprise as it confuse managers with two portfolio products where the high level Portfolio tool Jira Align is the product Atlassian seem to want to focus on. Renaming it to Advanced Roadmaps is however a very strange choice as it is not a simple roadmap tool. It also make the naming confusion shift from Portfolio to Roadmaps as Cloud users have been using the limited Roadmaps feature for quite some time.
      The new Advanced Roadmaps is only available for Cloud Premium users. This makes sense as Atlassian want to push users into their new price model. Currently there is not much that would warrant double the price for Cloud Premium so Atlassian need something that is enticing enough for users to make the shift. Advanced Roadmaps could be one of those features, but they need more as Advanced Roadmaps cost $2.3/user and month at it's lowest level and Cloud Premium cost an additional $7/user and month.
      Feature wise Advanced Roadmaps is still great with the two main selling points of great overview and the ability to scale the issues with more levels. Here are some of the selling points from Atlassian:
      With the changes coming to Roadmaps where all projects will get them, and not just Next-Gen projects, combined with the promise that Advanced Roadmaps will somehow be connected to a more comprehensive whole this could be a pretty good thing for Cloud Premium users. Adding Advanced Roadmaps to Cloud Premium will now add the ability to scale issue types beyond the standard 3 levels, which is something people have asked for for a very long time.

      Will it be enough to warrant the high price tag for Cloud Premium? I doubt that as Advanced Roadmaps is only really useful when you pass a certain number of teams. Doubling the price tag will probably discourage most low to mid-range clients. The fact that you can only have a 7 day test version and that you need to setup a new cloud instance to even test this if you are on a regular cloud plan is also a problem. With more features added into Cloud Premium however I think more and more will make the shift over to that.
      Overall this is a good new addition and package it with the Cloud Premium offer will make it more accessible and therefore used, which is a good thing. It's a bit sad to see Atlassian being so aggressive in their way of forcing cloud users into their Premium tier that is making some old customers a bit annoyed, but I think it will be good in the long run.
×
×
  • Create New...