#3597 Add stats charts to tracker - NEEDS SFTHEME, FORGE-CLASSIC

v1.0.0
closed
Jenny Steele
sf-4 (350)
Tracker
nobody
2015-08-20
2012-01-13
Jenny Steele
No

Log the number of tickets in each status by day and by milestone by day. Create charts that show ticket status over time and also a milestone burn down chart.

Implementation discussed at planning:

  • "port" the page like https://sourceforge.net/projects/allura/stats/tracker?dates=2011-11-20%20to%202012-01-20 to work in the tracker tool
    • that is, doing the exact same zarkov queries
    • it won't work for allura projects
    • but it will for migrated projects (test with migrating project1/3 on a sandbox - they should have zarkov data in SDS)
    • separate tickets will handle getting Allura projects' stats into zarkov in the right format
  • that part of the tool needs to check a config option to determine whether it's enabled or not. We need a new zarkov web service URL in the config anyway, so we can check to see if that key is set.
  • that'll cover day-by-day open/closed reports. Probably do burndown as a separate ticket?

Discussion

  • Jenny Steele - 2012-01-13
    • component: General --> Tracker
     

  • Dave Brondsema

    Dave Brondsema - 2012-01-20
    • milestone: forge-backlog --> forge-feb-03
     

  • Dave Brondsema

    Dave Brondsema - 2012-01-20
    • size: --> 4
     

  • Dave Brondsema

    Dave Brondsema - 2012-01-20
    • Description has changed:

    Diff:

    --- old 
+++ new 
@@ -1,1 +1,11 @@
 Log the number of tickets in each status by day and by milestone by day. Create charts that show ticket status over time and also a milestone burn down chart.
+
+Implementation discussed at planning:
+
+* "port" the page like https://sourceforge.net/projects/allura/stats/tracker?dates=2011-11-20%20to%202012-01-20 to work in the tracker tool
+    * that is, doing the exact same zarkov queries
+    * it won't work for allura projects
+    * but it will for migrated projects (test with migrating project1/3 on a sandbox - they should have zarkov data in SDS)
+    * separate tickets will handle getting Allura projects' stats into zarkov in the right format
+* that part of the tool needs to check a config option to determine whether it's enabled or not.  We need a new zarkov web service URL in the config anyway, so we can check to see if that key is set.
+* that'll cover day-by-day open/closed reports.  Probably do burndown as a separate ticket?
     

  • Jenny Steele - 2012-02-07
    • status: open --> code-review
    • qa: Dave Brondsema
    • milestone: forge-mar-02 --> forge-feb-17
     

  • Jenny Steele - 2012-02-07

    On allura, forge-classic, and sftheme js/3597. To test, do the following:

    1) Migrate an sfx project with tracker stats data like project1 to allura.
    2) Go to this page and confirm you don't see a chart: /p/project1/test-tracker/stats/
    3) Add the zarkov webservice host to the ini on your sandbox. There's a SOG ticket for this: https://trac.geek.net/trac/siteops/ticket/50177
    4) Reload /p/project1/test-tracker/stats/ and you should now see the chart.
    5) Go to a project without stats data like /p/test/tickets/stats/ and confirm there is no chart.

     

  • Kyle Adams - 2012-02-17
    • qa: Dave Brondsema --> Kyle Adams
     

  • Kyle Adams - 2012-02-21
    • status: code-review --> closed
     

  • Kyle Adams - 2012-02-21

    Looks good, merged to dev.

     

  • Kyle Adams - 2012-02-21
    • summary: Add stats charts to tracker --> Add stats charts to tracker - NEEDS SFTHEME, FORGE-CLASSIC
     

Log in to post a comment.