Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-5345

Add GreenHopper gadgets to the dashboard that tie to the Rapid Board

XMLWordPrintable

    • Hide
      Atlassian Status as at June 30th 2014

      Thanks for following this issue. This story covers a number of issues regarding gadgets in JIRA Agile.

      Since this issue was raised we have delivered many of the requests including:

      • GHS-6467 Sprint Burndown gadget
      • GHS-5113 Project Progress gadget delivered as Sprint Health gadget
      • GHS-6466 Days Remaining gadget also integrated in the Sprint Health gadget (GHS-5113)

      Remaining issues include:

      • GHS-5662 Cumulative Flow Chart gadget
      • GHS-6469 Summary statistics gadget like the info page of the Agile gadget
      • GHS-10691Create Version Report Gadget

      In order for us to track the remaining requests and understand the demand for each of them please vote or comment on the individual issues. I have now resolved this issue as tracked elsewhere.

      If your requirements are not covered by the above, or in an existing story in this project, please add a comment below. Your feedback on these issues is welcomed.

      Kind regards,
      Martin Jopson
      JIRA Agile

      Show
      Atlassian Status as at June 30th 2014 Thanks for following this issue. This story covers a number of issues regarding gadgets in JIRA Agile. Since this issue was raised we have delivered many of the requests including: GHS-6467 Sprint Burndown gadget GHS-5113 Project Progress gadget delivered as Sprint Health gadget GHS-6466 Days Remaining gadget also integrated in the Sprint Health gadget ( GHS-5113 ) Remaining issues include: GHS-5662 Cumulative Flow Chart gadget GHS-6469 Summary statistics gadget like the info page of the Agile gadget GHS-10691 Create Version Report Gadget In order for us to track the remaining requests and understand the demand for each of them please vote or comment on the individual issues. I have now resolved this issue as tracked elsewhere. If your requirements are not covered by the above, or in an existing story in this project, please add a comment below. Your feedback on these issues is welcomed. Kind regards, Martin Jopson JIRA Agile

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Is it possible to add GreenHopper burndown chart gadgets that tie to the Rapid Board?

            [JSWCLOUD-5345] Add GreenHopper gadgets to the dashboard that tie to the Rapid Board

            cesposito added a comment -

            This is a pain point for our organization, and enough of one that I've been asked to start investigating alternate tools. Can you give me an idea of when this could/would be addressed?

            cesposito added a comment - This is a pain point for our organization, and enough of one that I've been asked to start investigating alternate tools. Can you give me an idea of when this could/would be addressed?

            Michelle Parsons added a comment -

            I particularly would like JIRA Dashboard gadgets for the Version and Velocity reports, and the ability to add these gadgets to a Confluence page.

            Michelle Parsons added a comment - I particularly would like JIRA Dashboard gadgets for the Version and Velocity reports, and the ability to add these gadgets to a Confluence page.

            Kam added a comment -

            The fix version for this ticket is set to none. Are Atlassian able to provide an update as which release this ticket will link to, and if when the expected release of these gadgets will be?

            Kam added a comment - The fix version for this ticket is set to none. Are Atlassian able to provide an update as which release this ticket will link to, and if when the expected release of these gadgets will be?

            Peter Callies added a comment -

            Would love to see a gadget for the version report.

            Peter Callies added a comment - Would love to see a gadget for the version report.

            Tom Kotecki (Inactive) added a comment -

            ukjbrown,

            This is a bug that we intend to fix soon, you can follow it here: https://jira.atlassian.com/browse/GHS-8319

            Tom

            Tom Kotecki (Inactive) added a comment - ukjbrown, This is a bug that we intend to fix soon, you can follow it here: https://jira.atlassian.com/browse/GHS-8319 Tom

            Jamie added a comment -

            The new gadgets in GreenHopper 6.1.6 are no good as Wallboard gadgets - they add padding to the bottom of the gadget that is about the same size as the gadget. OK if you only want one gadget per column, useless if you want to stack gadgets.

            Jamie added a comment - The new gadgets in GreenHopper 6.1.6 are no good as Wallboard gadgets - they add padding to the bottom of the gadget that is about the same size as the gadget. OK if you only want one gadget per column, useless if you want to stack gadgets.

            Ellen Feaheny [AppFusions] added a comment -

            Like!

            Ellen Feaheny [AppFusions] added a comment - Like!

            Tom Kotecki (Inactive) added a comment -

            Hi All,

            We wanted to provide an update on this issue - both the Burndown (GHS-6467) and Days Remaining (GHS-6466) gadgets have now been implemented and are shipping with GreenHopper 6.1.6.

            Regards

            Tom Kotecki
            Product Manager, GreenHopper

            Tom Kotecki (Inactive) added a comment - Hi All, We wanted to provide an update on this issue - both the Burndown ( GHS-6467 ) and Days Remaining ( GHS-6466 ) gadgets have now been implemented and are shipping with GreenHopper 6.1.6. Regards Tom Kotecki Product Manager, GreenHopper

            Eric Dalquist added a comment - - edited

            This would be great to get fixed but in the mean time we've come up with this as a solution: https://github.com/UW-Madison-DoIT/wallboard

            We just have that html file on the computer we use as a wallboard and have it setup with various jira and external tool dashboards.

            Note this is based on Jeff Lamb's earlier post.

            Eric Dalquist added a comment - - edited This would be great to get fixed but in the mean time we've come up with this as a solution: https://github.com/UW-Madison-DoIT/wallboard We just have that html file on the computer we use as a wallboard and have it setup with various jira and external tool dashboards. Note this is based on Jeff Lamb's earlier post.

            Deleted Account (Inactive) added a comment -

            Not being able to put a burn down gadget on a wallboard is a major issue for us. The burn down chart is the key visual indicator of project progress.
            When will this be fixed??

            Deleted Account (Inactive) added a comment - Not being able to put a burn down gadget on a wallboard is a major issue for us. The burn down chart is the key visual indicator of project progress. When will this be fixed??

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment -

            I just wonder: how can Atlassian read all of this and live with it? Does GH team have the same culture? Have they heard about "Don't f##$k the customer" thing?

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment - I just wonder: how can Atlassian read all of this and live with it? Does GH team have the same culture? Have they heard about "Don't f##$k the customer" thing?

            Andreas Plattner added a comment -

            @Celine Courcy I'm not sure what you're printing (I assume the Rapid Board report page), but we currently work around this by adding a classic board sprint in parallel - alternatively setting the fix version will do the job as well. This allows you to add the classic agile gadgets to any dashboard again

            Andreas Plattner added a comment - @Celine Courcy I'm not sure what you're printing (I assume the Rapid Board report page), but we currently work around this by adding a classic board sprint in parallel - alternatively setting the fix version will do the job as well. This allows you to add the classic agile gadgets to any dashboard again

            Celine Courcy added a comment -

            The lack of dashboard gadgets for the rapid boards is a real shame. We have recently migrated from the classic boards to the rapid ones and found numerous features are not available. We managed to find work-arounds for most of them, but this one will require us to manually print this information every day and stick it on the wall (mostly interested in the sprint burn-down charts) to make them visible to all. Sigh.

            Celine Courcy added a comment - The lack of dashboard gadgets for the rapid boards is a real shame. We have recently migrated from the classic boards to the rapid ones and found numerous features are not available. We managed to find work-arounds for most of them, but this one will require us to manually print this information every day and stick it on the wall (mostly interested in the sprint burn-down charts) to make them visible to all. Sigh.

            MattS added a comment -

            The lack of gadgets is preventing new JIRA and GH customers from using the new boards. This is a blocker for them.

            MattS added a comment - The lack of gadgets is preventing new JIRA and GH customers from using the new boards. This is a blocker for them.

            John Fisher added a comment -

            Really surprising to me that classic boards were deprecated without a dashboard solution.

            John Fisher added a comment - Really surprising to me that classic boards were deprecated without a dashboard solution.

            Lars Corneliussen added a comment -

            Jeah! Agile. Done, Done!
            So bad!

            Rapid board is great, but wallboards become a blamage.

            Lars Corneliussen added a comment - Jeah! Agile. Done, Done! So bad! Rapid board is great, but wallboards become a blamage.

            Jeff Lamb added a comment -

            I've written a single standalone webpage that uses jquery and javascript to create a "wallboard" in lieu of GHS-5345 and GHS-6467 being completed. One major hiccup I had was jira was running on port 8080 and this was hosted on port 80 (same server). You get cross domain scripting violations in the JS error console. To resolve this, I used the jira docs for apache to proxy http://my.server/jira to point to http://my.server:8080.

            Go ahead and modify removeExcess() to your own liking to remove page elements that clutter your display. The existing ones should work for the burndown chart report, the work rapid board and the Cumulative Flow Diagram report. I tried to modify the the CSS to make it dark like existing wallboards, but canvas elements are always white, so guess we'll have to wait for the real fix.

            Have fun!

            <html lang="en">
<head>
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.0/jquery.min.js" type="text/javascript"></script>
<title>Wallboard</title>
<style type="text/css">
body, html { margin: 0; padding: 0; width: 100%; height: 100%; overflow: hidden; }
iframe { border: none; }
</style>
<script type="text/javascript">
var Dash = {
    nextIndex: 0,
    currentActiveIframeIndex: 0,
    
    iframes: ['displayArea1', 'displayArea2'],
    
    dashboards: [
        {url: "http://path.to.jira/secure/RapidBoard.jspa?rapidView=4&view=reporting&chart=cumulativeFlowDiagram&swimlane=4&column=10&column=11&column=12&quickFilter=23&from=2013-01-08&to=2013-01-24", time: 10},
        {url: "http://path.to.jira/secure/RapidBoard.jspa?rapidView=4", time: 10},
        {url: "http://path.to.jira/secure/RapidBoard.jspa?rapidView=4&view=reporting&chart=burndownChart&sprint=2", time: 10}
    ],

    setup: function() {
        // Preload next page, as it takes time to load the dynamic data
        Dash.preloadNextPage();
        setTimeout(Dash.display, 2001);
    },
    
    display: function()
    {
        var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1;
        var dashboard = Dash.dashboards[Dash.nextIndex];
        
        // swap iframe visibility
        $('#'+Dash.iframes[Dash.currentActiveIframeIndex]).fadeOut(800, function (){
            $('#'+Dash.iframes[preloadIframeIndex]).fadeIn(800);
        });        
        
        // swap current active iframe
        Dash.currentActiveIframeIndex = preloadIframeIndex;
        
        // Delay for the specified amount of time before swapping to a different dashbaord display
        setTimeout(Dash.display, dashboard.time * 1000);
        
        // Preload next page, as it takes time to load the dynamic data
        setTimeout(Dash.preloadNextPage, 2000);
        
    },
    
    preloadNextPage: function()
    {
        var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1;
        var iframeToPreload = frames[Dash.iframes[preloadIframeIndex]];
        var dashboard = Dash.dashboards[Dash.nextIndex];
        
        // Start page load on hidden iframe
        $('#'+Dash.iframes[preloadIframeIndex]).attr("src", dashboard.url)
        // Cycle to next entry in dashboards array
        Dash.nextIndex = (Dash.nextIndex + 1) % Dash.dashboards.length;
        // Delay to allow the page to load, then strip out unnecessary menus, etc
        setTimeout(Dash.removeExcess, 2000);        
    },
    
    removeExcess: function()
    {
        var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1;
        var iframeToPreload = frames[Dash.iframes[preloadIframeIndex]];
        
        // Remove any excess information from the page
        $('#header', iframeToPreload.document).hide();
        $('.ghx-feedback', iframeToPreload.document).hide();
        $('.aui-dd-link', iframeToPreload.document).hide();
        $('#announcement-banner', iframeToPreload.document).hide();
        $('#ghx-operations', iframeToPreload.document).hide();
        $('#ghx-chart-data', iframeToPreload.document).hide();
        $('#ghx-chart-overview-group', iframeToPreload.document).hide();
    }
};

window.onload = Dash.setup;
</script>
</head>
<body>
<iframe id="displayArea1" width="100%" height="100%"></iframe>
<iframe id="displayArea2" width="100%" height="100%"></iframe>
</body>
</html>

            Jeff Lamb added a comment - I've written a single standalone webpage that uses jquery and javascript to create a "wallboard" in lieu of GHS-5345 and GHS-6467 being completed. One major hiccup I had was jira was running on port 8080 and this was hosted on port 80 (same server). You get cross domain scripting violations in the JS error console. To resolve this, I used the jira docs for apache to proxy http://my.server/jira to point to http://my.server:8080 . Go ahead and modify removeExcess() to your own liking to remove page elements that clutter your display. The existing ones should work for the burndown chart report, the work rapid board and the Cumulative Flow Diagram report. I tried to modify the the CSS to make it dark like existing wallboards, but canvas elements are always white, so guess we'll have to wait for the real fix. Have fun! <html lang= "en" > <head> <script src= " //ajax.googleapis.com/ajax/libs/jquery/1.8.0/jquery.min.js" type= "text/javascript" ></script> <title>Wallboard</title> <style type= "text/css" > body, html { margin: 0; padding: 0; width: 100%; height: 100%; overflow: hidden; } iframe { border: none; } </style> <script type= "text/javascript" > var Dash = { nextIndex: 0, currentActiveIframeIndex: 0, iframes: [ 'displayArea1' , 'displayArea2' ], dashboards: [ {url: "http: //path.to.jira/secure/RapidBoard.jspa?rapidView=4&view=reporting&chart=cumulativeFlowDiagram&swimlane=4&column=10&column=11&column=12&quickFilter=23&from=2013-01-08&to=2013-01-24" , time: 10}, {url: "http: //path.to.jira/secure/RapidBoard.jspa?rapidView=4" , time: 10}, {url: "http: //path.to.jira/secure/RapidBoard.jspa?rapidView=4&view=reporting&chart=burndownChart&sprint=2" , time: 10} ], setup: function() { // Preload next page, as it takes time to load the dynamic data Dash.preloadNextPage(); setTimeout(Dash.display, 2001); }, display: function() { var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1; var dashboard = Dash.dashboards[Dash.nextIndex]; // swap iframe visibility $( '#' +Dash.iframes[Dash.currentActiveIframeIndex]).fadeOut(800, function (){ $( '#' +Dash.iframes[preloadIframeIndex]).fadeIn(800); }); // swap current active iframe Dash.currentActiveIframeIndex = preloadIframeIndex; // Delay for the specified amount of time before swapping to a different dashbaord display setTimeout(Dash.display, dashboard.time * 1000); // Preload next page, as it takes time to load the dynamic data setTimeout(Dash.preloadNextPage, 2000); }, preloadNextPage: function() { var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1; var iframeToPreload = frames[Dash.iframes[preloadIframeIndex]]; var dashboard = Dash.dashboards[Dash.nextIndex]; // Start page load on hidden iframe $( '#' +Dash.iframes[preloadIframeIndex]).attr( "src" , dashboard.url) // Cycle to next entry in dashboards array Dash.nextIndex = (Dash.nextIndex + 1) % Dash.dashboards.length; // Delay to allow the page to load, then strip out unnecessary menus, etc setTimeout(Dash.removeExcess, 2000); }, removeExcess: function() { var preloadIframeIndex = Dash.currentActiveIframeIndex ? 0 : 1; var iframeToPreload = frames[Dash.iframes[preloadIframeIndex]]; // Remove any excess information from the page $( '#header' , iframeToPreload.document).hide(); $( '.ghx-feedback' , iframeToPreload.document).hide(); $( '.aui-dd-link' , iframeToPreload.document).hide(); $( '#announcement-banner' , iframeToPreload.document).hide(); $( '#ghx-operations' , iframeToPreload.document).hide(); $( '#ghx-chart-data' , iframeToPreload.document).hide(); $( '#ghx-chart-overview-group' , iframeToPreload.document).hide(); } }; window.onload = Dash.setup; </script> </head> <body> <iframe id= "displayArea1" width= "100%" height= "100%" ></iframe> <iframe id= "displayArea2" width= "100%" height= "100%" ></iframe> </body> </html>

            Alex Kempkens added a comment -

            Dear Shaun,

            May be you could reevaluate your guess what is "greatest value to your customers". As a customer I can tell you that "aspects of this story within the next 12 months" is unacceptable and either will cause people in our company to ask for different tools or developers going to develop it themselves. In both cases we start to care less about your value estimations.

            • Alex

            Alex Kempkens added a comment - Dear Shaun, May be you could reevaluate your guess what is "greatest value to your customers". As a customer I can tell you that "aspects of this story within the next 12 months" is unacceptable and either will cause people in our company to ask for different tools or developers going to develop it themselves. In both cases we start to care less about your value estimations. Alex

            Shaun Clowes (Inactive) added a comment -

            Hi Everyone,

            Thanks so much for your votes and comments on this feature request, we wanted to provide an update on the status.

            We know there are features missing from the new Scrum and Kanban boards. We plan to deliver the gadget based burndown (GHS-6467), project progress (GHS-5113) and days remaining (GHS-6466) aspects of this story within the next 12 months.

            Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!

            Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed.

            Cheers,
            Shaun Clowes
            GreenHopper Product Manager

            Shaun Clowes (Inactive) added a comment - Hi Everyone, Thanks so much for your votes and comments on this feature request, we wanted to provide an update on the status. We know there are features missing from the new Scrum and Kanban boards. We plan to deliver the gadget based burndown ( GHS-6467 ), project progress ( GHS-5113 ) and days remaining ( GHS-6466 ) aspects of this story within the next 12 months. Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you! Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed. Cheers, Shaun Clowes GreenHopper Product Manager

            Christopher Lohman added a comment -

            Vote from me. Gadgets are far more useful than reports. Reports are not "agile"; they take too long. I essentially want to setup a business intelligence dashboard using gadgets which reference data stored within Jira, Crucible, Fisheye. Burn down is absolutely critical. I want each user to see their own burn down gadget on their dashboard. I want leads to have a quick view of burn down for the iteration just for the past 24 hours; for all users in the iteration.

            What I really want is for Atlassian to give us better "foundation" gadgets that we can customize for any function. Instead of a gadget specifically for burndown charts, develop a chart gadget that can cover every type of chart that one would find in Microsoft Excel. Allow the chart to use multiple filters as data sources and then I'll build my own burn-down gadget.

            Christopher Lohman added a comment - Vote from me. Gadgets are far more useful than reports. Reports are not "agile"; they take too long. I essentially want to setup a business intelligence dashboard using gadgets which reference data stored within Jira, Crucible, Fisheye. Burn down is absolutely critical. I want each user to see their own burn down gadget on their dashboard. I want leads to have a quick view of burn down for the iteration just for the past 24 hours; for all users in the iteration. What I really want is for Atlassian to give us better "foundation" gadgets that we can customize for any function. Instead of a gadget specifically for burndown charts, develop a chart gadget that can cover every type of chart that one would find in Microsoft Excel. Allow the chart to use multiple filters as data sources and then I'll build my own burn-down gadget.

            Yuen-Chi Lian added a comment -

            We do version-less (or some called it "One Track") development here. The classic gadgets are useless to us as they enforces versioning.

            I'm voting for this issue.

            Yuen-Chi Lian added a comment - We do version-less (or some called it "One Track") development here. The classic gadgets are useless to us as they enforces versioning. I'm voting for this issue.

            Sara Taillon added a comment -

            I've been a huge fan of Atlassian products for a very long time and have used them at my past 3 companies. My current company recently moved from an in-house issue tracking system to Jira with Greenhopper for all of our company's development projects. So far there has been overwhelming excitement and positive feedback about the switch. However, the lack of dashboard gadgets really makes it hard for executives to get as excited about Jira/GreenHopper as I know they will eventually be. We need gadgets to be implemented for the new rapid boards before the enthusiasm wanes and we're forced to build a bunch of custom reports that would ultimately be underwhelming to execs and management.

            Sara Taillon added a comment - I've been a huge fan of Atlassian products for a very long time and have used them at my past 3 companies. My current company recently moved from an in-house issue tracking system to Jira with Greenhopper for all of our company's development projects. So far there has been overwhelming excitement and positive feedback about the switch. However, the lack of dashboard gadgets really makes it hard for executives to get as excited about Jira/GreenHopper as I know they will eventually be. We need gadgets to be implemented for the new rapid boards before the enthusiasm wanes and we're forced to build a bunch of custom reports that would ultimately be underwhelming to execs and management.

            rainer mueck added a comment - - edited

            NOTE TO ALL SUPPORTERS OF THIS REQUEST

            Stefan Kalhofer (SAP), Stefan Höhn (CSC) and myself (Software AG) will be having a phone conference with Nicholas Muldoon from Atlassian on Thursday.

            If you wish to influence a change, TAKE YOUR CHANCE NOW in supporting us.

            Please express yourself with respectable comments and votes on GHS-6754 (As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements) and related issues.

            Many thanks in advance.

            Rainer Mueck

            Update:

            The meeting took place on 29-Nov-2012. There are no concrete results yet, but there will be a follow-up meeting in one week. So please stay tuned for more updates to come.

            rainer mueck added a comment - - edited NOTE TO ALL SUPPORTERS OF THIS REQUEST Stefan Kalhofer (SAP), Stefan Höhn (CSC) and myself (Software AG) will be having a phone conference with Nicholas Muldoon from Atlassian on Thursday. If you wish to influence a change, TAKE YOUR CHANCE NOW in supporting us. Please express yourself with respectable comments and votes on GHS-6754 (As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements) and related issues. Many thanks in advance. Rainer Mueck Update: The meeting took place on 29-Nov-2012. There are no concrete results yet, but there will be a follow-up meeting in one week. So please stay tuned for more updates to come.

            César García Sáez added a comment -

            Hi,

            @Shaun Clowes as an OnDemand user, I'm stuck into the last version available. I really enjoy using the boards but I'm discovering some nasty issues. I just subscribed for the Greenhopper module, and I was planning to use all announced features but then I discovered there are RapidBoards (the ones I'm using by default) and old Classic Boards. All the nice wallboard gadgets suddenly are unsupported on RapidBoards and my useful wallboard seems more like a a proof of concept that anything usaable with current release.

            Please fix this ASAP.

            César García Sáez added a comment - Hi, @Shaun Clowes as an OnDemand user, I'm stuck into the last version available. I really enjoy using the boards but I'm discovering some nasty issues. I just subscribed for the Greenhopper module, and I was planning to use all announced features but then I discovered there are RapidBoards (the ones I'm using by default) and old Classic Boards. All the nice wallboard gadgets suddenly are unsupported on RapidBoards and my useful wallboard seems more like a a proof of concept that anything usaable with current release. Please fix this ASAP.

            dominick destasio added a comment -

            Seriously guys, you need to fix this.

            dominick destasio added a comment - Seriously guys, you need to fix this.

            Dan Burzynski added a comment -

            All this voting on issues business is really wearing me down. It doesn't seem to result in anything getting done (For fun, have a peek at https://jira.atlassian.com/browse/JRA-1549 which has 600+ votes and has been open since 2003). I wish that Atlassian would introduce account managers (like every other tech supplier that I deal with) so that at least I have the illusion that someone's listening.

            Dan Burzynski added a comment - All this voting on issues business is really wearing me down. It doesn't seem to result in anything getting done (For fun, have a peek at https://jira.atlassian.com/browse/JRA-1549 which has 600+ votes and has been open since 2003). I wish that Atlassian would introduce account managers (like every other tech supplier that I deal with) so that at least I have the illusion that someone's listening.

            Adrian Hall added a comment -

            Hi Shaun,

            When I came back to check on the status of this ticket I was presented by a great glossy, soundtracked video advert. It shows how seamlessly the new filters can be integrated with the new boards and how great they are at working with gadgets on dashboards.

            Unfortunately, this is of course fiction but if even your own advertising / marketing team know of its importance then hopefully it will get some attention soon.

            Oh by the way, if you pass by them can you give them a nudge and ask them to vote on this issue please :o)

            Thanks.

            Adrian Hall added a comment - Hi Shaun, When I came back to check on the status of this ticket I was presented by a great glossy, soundtracked video advert. It shows how seamlessly the new filters can be integrated with the new boards and how great they are at working with gadgets on dashboards. Unfortunately, this is of course fiction but if even your own advertising / marketing team know of its importance then hopefully it will get some attention soon. Oh by the way, if you pass by them can you give them a nudge and ask them to vote on this issue please :o) Thanks.

            Alex D. added a comment -

            We are trying to display multiple greenhopper burndown charts on our jira dashboard so we can have a visual of the progress of multiple feature-sets. Correct me if i'm wrong, but there is no way to display multiple burndown lines on the same chart in greenhopper. There is also no way to filter issues from a sprint on a burndown so it displays differently. Will this functionality be possible in a future version of greenhopper?

            And also, approximately when will a gadget be released for our dashboards that show greenhopper burndowns? Is it even confirmed to be released?

            Alex D. added a comment - We are trying to display multiple greenhopper burndown charts on our jira dashboard so we can have a visual of the progress of multiple feature-sets. Correct me if i'm wrong, but there is no way to display multiple burndown lines on the same chart in greenhopper. There is also no way to filter issues from a sprint on a burndown so it displays differently. Will this functionality be possible in a future version of greenhopper? And also, approximately when will a gadget be released for our dashboards that show greenhopper burndowns? Is it even confirmed to be released?

            Gustavo Narea added a comment - - edited

            @Shaun: Scrum Rapid Boards without burndown chart gadgets is a bad joke that gets worse as you consider the workarounds. Period.

            If your customers are telling you that there are worse things than this, then you must be in a hopeless situation.

            But thanks for the update anyway.

            Gustavo Narea added a comment - - edited @Shaun: Scrum Rapid Boards without burndown chart gadgets is a bad joke that gets worse as you consider the workarounds. Period. If your customers are telling you that there are worse things than this, then you must be in a hopeless situation. But thanks for the update anyway.

            Paul Alexander added a comment -

            Lack of Classic Chart Board functionality is a huge problem...This should be priority 0 for Atlassian. The replacement charts on the new Board's Report tab are not great. In fact, if you expect to get a "story point burn down chart", you first need to setup the versions on the Classic Board side and add the "Story Point" statistic (Statistics button on the right side and choose that value from the dropdown and add it). And to top it off, there are no gadgets available on a dashboard to support us. What are we supposed to do? I'm trying to empower my teams to estimate well, create Jira stories with story points, and meet two-week sprint goals of an established number of points...but there is little help to offer my team leads to guide them.
            BTW, there is a bug on the Classic Chart Board that will yield incorrect story point burndown, so with these now defunct, we're really forced to move off now. I've been holding off taking the leap, but frankly really need the great support the new Boards offer that allows grouping issues that cross systems(projects) and offering the views various folks need via their own Board.
            Keep up the good work, but please hurry!

            Paul Alexander added a comment - Lack of Classic Chart Board functionality is a huge problem...This should be priority 0 for Atlassian. The replacement charts on the new Board's Report tab are not great. In fact, if you expect to get a "story point burn down chart", you first need to setup the versions on the Classic Board side and add the "Story Point" statistic (Statistics button on the right side and choose that value from the dropdown and add it). And to top it off, there are no gadgets available on a dashboard to support us. What are we supposed to do? I'm trying to empower my teams to estimate well, create Jira stories with story points, and meet two-week sprint goals of an established number of points...but there is little help to offer my team leads to guide them. BTW, there is a bug on the Classic Chart Board that will yield incorrect story point burndown, so with these now defunct, we're really forced to move off now. I've been holding off taking the leap, but frankly really need the great support the new Boards offer that allows grouping issues that cross systems(projects) and offering the views various folks need via their own Board. Keep up the good work, but please hurry!

            Shaun Clowes (Inactive) added a comment -

            Hi All,

            I'm sorry to reiterate, but please, if you feel that the new boards do not meet your needs please continue using the Classic Boards. As you can see, we are completely reinventing GreenHopper, this will take us time but be worth it in the end. Of course, this also means that everything must be rewritten, so we need to prioritize what we are doing. Even though these gadgets are very important to watchers of this issue, they are not the most important based on overall feedback from all customers. We have released over 20 new versions of GreenHopper in the past year, so I hope you see the very fast progress we are making, we hope to introduce the features you need as quickly as possible.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi All, I'm sorry to reiterate, but please, if you feel that the new boards do not meet your needs please continue using the Classic Boards. As you can see, we are completely reinventing GreenHopper, this will take us time but be worth it in the end. Of course, this also means that everything must be rewritten, so we need to prioritize what we are doing. Even though these gadgets are very important to watchers of this issue, they are not the most important based on overall feedback from all customers. We have released over 20 new versions of GreenHopper in the past year, so I hope you see the very fast progress we are making, we hope to introduce the features you need as quickly as possible. Thanks, Shaun

            Londa Caine added a comment -

            Having Rapid Board based wallboard gadgets is a critical piece for full adoption of the sprint/rapid board features in our Scrum environment. Easily visible burndown charts must be created outside of Jira, which is a step backwards from the classic functionality previously available.

            Londa Caine added a comment - Having Rapid Board based wallboard gadgets is a critical piece for full adoption of the sprint/rapid board features in our Scrum environment. Easily visible burndown charts must be created outside of Jira, which is a step backwards from the classic functionality previously available.

            Michael Blake added a comment -

            We exclusively use the rapid boards but need to know the hourly burndown along with the story point burndown. We use ranking by story points. It would be nice to have a report in greenhopper that shows the remaining hours per user so that our release managers can re-balance the work in each sprint before it is too late to not get the work done.

            Michael Blake added a comment - We exclusively use the rapid boards but need to know the hourly burndown along with the story point burndown. We use ranking by story points. It would be nice to have a report in greenhopper that shows the remaining hours per user so that our release managers can re-balance the work in each sprint before it is too late to not get the work done.

            Mark DeMichele added a comment -

            This is somewhat related but my team makes every use of Jira' Version Workload Report from the project page. We use this during iteration planning meetings and during the iteration. The way our team works is we load up individual users per iteration. This screen allows us to check each users workload at the start of an iteration and during. We really need some kind of functionality like this. Basically, time remaining per user for a given iteration, or in this case sprint.

            Mark DeMichele added a comment - This is somewhat related but my team makes every use of Jira' Version Workload Report from the project page. We use this during iteration planning meetings and during the iteration. The way our team works is we load up individual users per iteration. This screen allows us to check each users workload at the start of an iteration and during. We really need some kind of functionality like this. Basically, time remaining per user for a given iteration, or in this case sprint.

            Stefan Höhn added a comment -

            Chris, you are absolutely right. I actually opened a similar reqest in August but I wasn't heard.

            Stefan Höhn added a comment - Chris, you are absolutely right. I actually opened a similar reqest in August but I wasn't heard.

            Chris Tooley added a comment -

            Shaun, I don't think anyone really believes that Atlassian isn't committed to delivering critical features. I think there are a large group of us that have come to rely on things that just aren't available from the Boards. Currently, I cannot upgrade past the 5.X releases because there are too many things missing in the Boards. We'd love to use the new features of the Boards in 6.X, but we can't because the Classic boards become a lot harder to train around, especially for a company as large as ours.

            As a workaround I've submitted GHS-6475 to get us back to where we were previously. It's not a solution the problem presented here, or any of the additional problems you've listed, but at least we're not in worse shape than we were in with 5.10.

            Chris Tooley added a comment - Shaun, I don't think anyone really believes that Atlassian isn't committed to delivering critical features. I think there are a large group of us that have come to rely on things that just aren't available from the Boards. Currently, I cannot upgrade past the 5.X releases because there are too many things missing in the Boards. We'd love to use the new features of the Boards in 6.X, but we can't because the Classic boards become a lot harder to train around, especially for a company as large as ours. As a workaround I've submitted GHS-6475 to get us back to where we were previously. It's not a solution the problem presented here, or any of the additional problems you've listed, but at least we're not in worse shape than we were in with 5.10.

            Dan Burzynski added a comment -

            Adding my 2 cents to this... We've been left feeling that we're going to have to shoe-horn our development process into the way in which GreenHopper wants us to work and not the way that works for us. As our development team grew and then split into groups and grew again, the Classic way of doing things allowed us to use the it in different ways (the only gripe I had with Classic was the atomicity of the sprint and the release all done using the Fix Version(s)). The Rapid Board feels so much more restrictive. I still can't upgrade to it here without major losses of functionality that we've come to rely on. It's a shame really. I hope that this is not a model for future developments. I'd hate to switch us over the the Rapid Board only to find that in a few years some new system appears and we have to go through the same process again.

            Dan Burzynski added a comment - Adding my 2 cents to this... We've been left feeling that we're going to have to shoe-horn our development process into the way in which GreenHopper wants us to work and not the way that works for us. As our development team grew and then split into groups and grew again, the Classic way of doing things allowed us to use the it in different ways (the only gripe I had with Classic was the atomicity of the sprint and the release all done using the Fix Version(s)). The Rapid Board feels so much more restrictive. I still can't upgrade to it here without major losses of functionality that we've come to rely on. It's a shame really. I hope that this is not a model for future developments. I'd hate to switch us over the the Rapid Board only to find that in a few years some new system appears and we have to go through the same process again.

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment -

            I don't want to get into GreenHopper's strategy, amount of people or other things that are not related to the GH features or user needs. Nevertheless I fully support Stefan's comment in the remaining areas. Migration strategy, sprint management and planning as well as missed features - Stefan described a situation pretty well.
            It's the feeling related to opening the new area for customers but not fulfilling the requirements for a minimum viable content.

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment - I don't want to get into GreenHopper's strategy, amount of people or other things that are not related to the GH features or user needs. Nevertheless I fully support Stefan's comment in the remaining areas. Migration strategy, sprint management and planning as well as missed features - Stefan described a situation pretty well. It's the feeling related to opening the new area for customers but not fulfilling the requirements for a minimum viable content.

            Stefan Höhn added a comment -

            Shaun, I can completely second Karen's thought. Don't take that personally but I think you do not have the necessary amount of people to really drive this. My personal feeling is that you have a strategy to move to a new implementation of Greenhopper BUT instead of first implementing what had been there, you first add new things. Even though it disturbs your current customers it does attract new ones, which is probably why you go that way. Using the new rapid board together with the classic board does not work. For example you can only work on the classic chart board and sprints if sprints are versions but then you have to manage sprints twice differently. Release planning with the board is currently a nightmare because you have to go back forth between the classic and rapid board. There is also no migration path when you come from a running project. You would completely loose your release burndown. Finally the agile gadget which is the main topic here is not uptodate. I know most of this is off topic to this issue here but I needed to support Karen Geiger as you were saying "we do the best we can". Given the huge customer base you have, I would think you should dedicate more resources into Greenhopper's development!

            Agile IS about transparency. If I don't have all the charts, the tool is actually losing most of my time savers!

            cheers,
            Stefan

            Stefan Höhn added a comment - Shaun, I can completely second Karen's thought. Don't take that personally but I think you do not have the necessary amount of people to really drive this. My personal feeling is that you have a strategy to move to a new implementation of Greenhopper BUT instead of first implementing what had been there, you first add new things. Even though it disturbs your current customers it does attract new ones, which is probably why you go that way. Using the new rapid board together with the classic board does not work. For example you can only work on the classic chart board and sprints if sprints are versions but then you have to manage sprints twice differently. Release planning with the board is currently a nightmare because you have to go back forth between the classic and rapid board. There is also no migration path when you come from a running project. You would completely loose your release burndown. Finally the agile gadget which is the main topic here is not uptodate. I know most of this is off topic to this issue here but I needed to support Karen Geiger as you were saying "we do the best we can". Given the huge customer base you have, I would think you should dedicate more resources into Greenhopper's development! Agile IS about transparency. If I don't have all the charts, the tool is actually losing most of my time savers! cheers, Stefan

            Shaun Clowes (Inactive) added a comment -

            Hi karenpcheng, All,

            It's a shame to hear that you think we're not focused on delivering critical features, we absolutely listen to feedback and deliver features as fast as we can. At the moment we're focused on Epics and Detail View configuration which are definitely the most requested items in the new boards. Unfortunately this means that we don't have any immediate plans to address gadgets. You can feel free to stick with the Classic Boards if this is a showstopper for you, we will definitely not remove them in the foreseeable future and have no intention of removing them until we can show the majority of users have migrated.

            In any case, I'd like to track the requests for gadgets in a more fine grained manner so we can understand exactly which gadgets people care most about (obviously we'd need to implement them individually). To that end can we please move conversations (and votes) to the following issues:

            GHS-5662 - Cumulative Flow Chart gadget
            GHS-5113 - Project progress gadget
            GHS-6464 - Card view gadget
            GHS-6466 - Days remaining gadget
            GHS-6467 - Burndown gadget
            GHS-6469 - Summary statistics gadget like the info page of the Agile gadget

            Thank you.

            Cheers,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi karenpcheng , All, It's a shame to hear that you think we're not focused on delivering critical features, we absolutely listen to feedback and deliver features as fast as we can. At the moment we're focused on Epics and Detail View configuration which are definitely the most requested items in the new boards. Unfortunately this means that we don't have any immediate plans to address gadgets. You can feel free to stick with the Classic Boards if this is a showstopper for you, we will definitely not remove them in the foreseeable future and have no intention of removing them until we can show the majority of users have migrated. In any case, I'd like to track the requests for gadgets in a more fine grained manner so we can understand exactly which gadgets people care most about (obviously we'd need to implement them individually). To that end can we please move conversations (and votes) to the following issues: GHS-5662 - Cumulative Flow Chart gadget GHS-5113 - Project progress gadget GHS-6464 - Card view gadget GHS-6466 - Days remaining gadget GHS-6467 - Burndown gadget GHS-6469 - Summary statistics gadget like the info page of the Agile gadget Thank you. Cheers, Shaun

            Karen Geiger added a comment -

            We are reluctantly moving to the new Rapid Boards because of the inevitability of the Classic Boards going away. I understand that these are two separate code bases so there is no guarantee of parity. However, in all my dealings with Atlassian I get the sense that there is no priority placed on making sure critical features of the Classic Boards are developed in the Rapid Board. We have many Scrum Teams in our organization and it is critical to have a dashboard showing all the burndowns across the teams. As others have mentioned, transparency is critical in an Agile development shop. Please consider this request!

            Karen Geiger added a comment - We are reluctantly moving to the new Rapid Boards because of the inevitability of the Classic Boards going away. I understand that these are two separate code bases so there is no guarantee of parity. However, in all my dealings with Atlassian I get the sense that there is no priority placed on making sure critical features of the Classic Boards are developed in the Rapid Board. We have many Scrum Teams in our organization and it is critical to have a dashboard showing all the burndowns across the teams. As others have mentioned, transparency is critical in an Agile development shop. Please consider this request!

            Stefan Höhn added a comment -

            I agree on that. How can it be minor if 65 people have voted for it?

            =Stefan=

            Stefan Höhn added a comment - I agree on that. How can it be minor if 65 people have voted for it? =Stefan=

            Adrian Hall added a comment -

            Hi Guys,

            I have been using and recommending your products for years (so good job) and I just signed up to give my +1 to this. I wish I had seen this before setting my projects up in this latest on-demand version. This is really a partial product until these are in place. Not happy about this being logged as Minor. I know that you don't publish roadmaps but is this on any kind of nearby horizon or off in the distant lands of 'potential enhancements' somewhere?

            I am really thinking of rolling back to classic view if this is nowhere near.

            Thanks.

            Adrian Hall added a comment - Hi Guys, I have been using and recommending your products for years (so good job) and I just signed up to give my +1 to this. I wish I had seen this before setting my projects up in this latest on-demand version. This is really a partial product until these are in place. Not happy about this being logged as Minor. I know that you don't publish roadmaps but is this on any kind of nearby horizon or off in the distant lands of 'potential enhancements' somewhere? I am really thinking of rolling back to classic view if this is nowhere near. Thanks.

            BlueKai Support added a comment -

            Not only is this an important feature to report Engineering progress, but the documentation leaves out this critical information.

            No where in https://studio.plugins.atlassian.com/wiki/display/WALLBOARD/Wallboards+101, does it mention that Burndown charts are not available in Rapid Boards.

            If you want users to read your documentation, it must be accurate.

            BlueKai Support added a comment - Not only is this an important feature to report Engineering progress, but the documentation leaves out this critical information. No where in https://studio.plugins.atlassian.com/wiki/display/WALLBOARD/Wallboards+101 , does it mention that Burndown charts are not available in Rapid Boards. If you want users to read your documentation, it must be accurate.

            Jasper Verdooren added a comment -

            This is an importanrt feature to me as well, as well as many of my customers. Please make these widgets then also available in Confluence. Thanks!

            Jasper Verdooren added a comment - This is an importanrt feature to me as well, as well as many of my customers. Please make these widgets then also available in Confluence. Thanks!

            Brady Kimball added a comment -

            This is very important as my R&D group expressed progress to executive stakeholders through existing gadgets. We are in a precarious situation until this is addressed. Thank you for your consideration!

            Brady Kimball added a comment - This is very important as my R&D group expressed progress to executive stakeholders through existing gadgets. We are in a precarious situation until this is addressed. Thank you for your consideration!

            Bill Warshaw added a comment -

            Agreed. Need Wallboard gadgets for:

            Sprint Days Remaining
            Sprint Hours Burndown

            We have a large TV setup as a wallboard, and have taken a big step backwards with the new Scrum Boards not supporting key information.

            Bill Warshaw added a comment - Agreed. Need Wallboard gadgets for: Sprint Days Remaining Sprint Hours Burndown We have a large TV setup as a wallboard, and have taken a big step backwards with the new Scrum Boards not supporting key information.

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment -

            I would like to see a gadget for "sprint days left". With the Rapid Board, a sprint is no longer directly related to a version, but gadgets remain connected to the versions.

            Bartosz Rakowski [RAKS Sp. z o.o.] added a comment - I would like to see a gadget for "sprint days left". With the Rapid Board, a sprint is no longer directly related to a version, but gadgets remain connected to the versions.

            Michelle Plank added a comment -

            We have being using the gadgets with classic boards which we use daily on TV screens for the wider business . Now we are in the process of migrating to rapid boards but lose this functionality. Please address this

            Michelle Plank added a comment - We have being using the gadgets with classic boards which we use daily on TV screens for the wider business . Now we are in the process of migrating to rapid boards but lose this functionality. Please address this

            Neil Padgen added a comment -

            Most of the Dashboard plugins for GreenHopper seem to be geared towards the Classic Boards. We are using a Rapid Board but need to share information such as burndown charts with anonymous users.

            One of the guiding principles of Scrum is transparency. Without being able to share our boards and burndown charts we're not being as transparent as we would like.

            Neil Padgen added a comment - Most of the Dashboard plugins for GreenHopper seem to be geared towards the Classic Boards. We are using a Rapid Board but need to share information such as burndown charts with anonymous users. One of the guiding principles of Scrum is transparency. Without being able to share our boards and burndown charts we're not being as transparent as we would like.

            Donncha Daly added a comment -

            I agree with the previous comments. The widgets are essential tools and formed a considerable part of our decision process
            to go with JIRA. Having them effectively removed due to the move to RapidBoard has severely hampered us. I would urge you to address this very soon.

            Donncha Daly added a comment - I agree with the previous comments. The widgets are essential tools and formed a considerable part of our decision process to go with JIRA. Having them effectively removed due to the move to RapidBoard has severely hampered us. I would urge you to address this very soon.

            Edwin Stol added a comment -

            We are considering creating our own plug-in for this; i can't find it on a short-term roadmap of Atlassian (hence, the public jira backlog).

            Edwin Stol added a comment - We are considering creating our own plug-in for this; i can't find it on a short-term roadmap of Atlassian (hence, the public jira backlog).

              gfranck Gabriele Franck
              rluispereiramartins RicardoA
              Votes:
              275 Vote for this issue
              Watchers:
              198 Start watching this issue

                Created:
                Updated:
                Resolved: