Skip Navigation LinksHome / Announcements / Forums / TFS Work Item Manager and Project Dashboard: TFS Project Dashboard > Remaining Work Trend

Not answered Remaining Work Trend

  • James Jewart Posted on Mar 12, 2010
    What does this reflect? Hours? Work Items? Can you give some insite?

    Thanks
    Reply
  • Joel Joel Posted on Mar 15, 2010
    Hello James,

    The numbers in this chart represent the values entered in certain fields, depending on the process template being used.  If you're using the Scrum template, the values come from the "Work Remaining" field (Conchango.TeamSystem.Scrum.WorkRemaining) otherwise the values come from the "Remaining Work" field (Microsoft.VSTS.Scheduling.RemainingWork.  Both of these fields are just numeric fields so you're free to use them however you want.  You can put hours, days, story points, etc. in the fields and the chart use those values to calculate the remaining work trend.

    Regards,
    Joel

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
    Reply
  • James Jewart Posted on Mar 15, 2010
    Thanks Joel
    Reply
  • Pieter Versteijnen Posted on Jun 28, 2010
    Joel, when I open the Project Dashboard I get an error on the Remaining work trend.

    Error:
    Query (1, 495) The member '[Scrum_v3_WorkRemaining]' was not found in the cube when the string, [Measures].[Scrum_v3_WorkRemaining], was parsed.

    We work with the Conchango v2 template. Is it possible to change the field the query is using?

    Thanks,

    Pieter
    Reply
  • Joel Joel Posted on Jun 29, 2010
    Hello Pieter,

    Did you install the Conchango v2 template on a TFS 2010 server?  If this is the case, then unfortunately there isn't much we can do at this point (barring code changes) as that was not a situation we anticipated.  We assumed that those running TFS 2010 would use the v3 template and those on TFS 2008 would use the v2 template.  If you are using TFS 2008 then the dashboard should have known to use a different query that works with the v2 template.  Can you answer a couple questions for me?

    1. Which version of TFS are you using?
    2. Which version of the Work Item Manager are you using (version number)?

    Regards,
    Joel
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Reply
  • Pieter Versteijnen Posted on Jun 30, 2010
    Joel,

    We installed the Scrum v2 template on a TFS2008 server. Later we upgraded the TFS2008 server to a TFS2010 server. This is not supported by the Scrum v2 template and we are running into more issues here. I just wonderd if it was possible to alter the query in a config file or something.

    Reading your reaction I guess it is not possible, so I have to accept I wont have a remaining work graph.

    WIM v1.1.0.13397

    Thanks,

    Pieter
    Reply
  • deimon Posted on Aug 30, 2010
    I get the same message: Query (1, 495) The member '[Scrum_v3_WorkRemaining]' was not found in the cube when the string, [Measures].[Scrum_v3_WorkRemaining], was parsed.

    I am running MSF for agile template. Visual Studio 2010.
    Reply
  • Joel Joel Posted on Aug 31, 2010
    Hi Mattias,

    If you are using the MSF for Agile template, have you made any customizations to the work item types?  For instance, have you added a Sprint Backlog Item or Product Backlog Item work item? 

    The reason I ask is that the presence of either of those work item types is how the dashboard determines whether to use a "Scrum" warehouse query for the remaining work trend or a regular query.  The scrum query uses the 'Scrum_v3_WorkRemaining' field and the default one uses 'Microsoft_VSTS_Scheduling_RemainingWork'

    Regards,
    Joel
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Reply
  • deimon Posted on Sep 1, 2010
    Hi,

    Thanks for you response. You are right I have actually changed the Scenarion work item type name to Product Backlog Item. What will happen if I call it for instance Product Backlog Task. Will it use 'Microsoft_VSTS_Scheduling_RemainingWork' then?

    Regards
    Mattias
    Reply
  • Joel Joel Posted on Sep 1, 2010
    Hello Mattias,

    Yes, you are correct.  If you dont' have a work item type in your project named "Product Backlog Item" or "Sprint Backlog Item" then the query will use 'Microsoft_VSTS_Scheduling_RemainingWork' instead.  However, from your perspective, I would be hesitant to change my process template just to work around a bug in our tool.

    Regards,
    Joel
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Reply
  • Patrick Posted on Jun 4, 2012
    Can you provide more details on this response. I am using the scrum template (ms scrum template 1.0 on TFS2010) and have work items with remaining work field populated. However I cannot reconcile the values shown on the dashboard's remain work trend with the sum of the remaining work field values or with the TFS burn down reports. What work item type's are being included in dashboard's widget for Remaining Work Trend.

    I also have similar questions related to the Bug History (last 10 days) widget. What is the y-axis stacked axis counting?
    Reply
  • Joel Joel Posted on Jun 11, 2012
    The remaining work trend chart uses data from the TFS analysis services data warehouse to show how the sum of the values in the work remaining field changes over time.  The x-axis contains days and the y-axis contains the sum of the work remaining on that day.  The work item types it includes depends on the process template used to create your project.  In your case, since you're using the MS Scrum template, it doesn't actually filter out any work item types but since only the Task work item type has a work remaining field, it is essentially only considering tasks.

    As for the Bug History chart, the x-axis contains days and the y-axis contains the number of bugs in each state on that day.  Unfortunately, this widget is always scoped to the entire project and does not consider iterations.  This behavior can cause the value of the chart to diminish over time as it can eventually get too much data to be useful.

    Regards,
    Joel
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

    Reply
  • Patrick Posted on Jun 11, 2012
    Hi Joel,
    Still trying to diagnose why our Remaining Work Trend chart is coming blank today (the start of our June 11, 2012 sprint 14). I turned off all other dashboard widgets except for Remaining Work Trend via the dashboard's configuration settings. Then I turned SQL Server profiler to trace the query being used against the TFS analysis service. I see the following MDX query is executed. And when I run this query it is coming back with a value of 209 (which is the correct value for remaining work.

     Sidenote: Interestingly, this query from the dashboard is emitting a query that filter's on the current dates of 2012-06-11 through 2012-06-24. This would indicate to me that this query is indeed filtering to the current iteration. This is odd because my testing last week clearly showed that it was totalling all open tasks.

    But more importantly getting our dashboard's Remaining Work widget working again is most important. Any thoughts? Thanks Patrick

    SELECT

    NON EMPTY [Work Item].[System_State] on COLUMNS,

    NON

     

    EMPTY CrossJoin( [Team Project].[Team Project Hierarchy].&[{539e50ef-3343-4615-b134-3639e5ade962}], [Work Item].[System_WorkItemType] ,

    Filter

    ([Date].[Date].Members, ([Date].[Date].CurrentMember.MemberValue>=CDate("2012-06-11")

    AND

    [Date].[Date].CurrentMember.MemberValue<CDate("2012-06-24"))) ) ON ROWS from [Team System]

    WHERE ([Measures].[Microsoft_VSTS_Scheduling_RemainingWork])


    Reply
  • Patrick Posted on Jun 11, 2012
    Hi Joel,
    I uncovered an additional detail. When I go into iterations and change sprint 14 to be 2012-06-10 through 2012-06-23 (backed it up one day), then the Mdx query emitted from the dashboard is the following. And that now results in two days results coming back (each day is a full totalling of all tasks remaining time independent of which iteration they exist under. So that ties in with your response). However it appears that the Dashboard needs to have two days of data in order to render a Remain Work chart of Actual vs Trend.

    Is there any place (undocumented) that I can modify the mdx query being used for the dashboard widget? Or is the query hardcoded into the dashboard binary? Thanks Patrick

    SELECT

     

    NON EMPTY [Work Item].[System_State] on COLUMNS,

    NON EMPTY CrossJoin( [Team Project].[Team Project Hierarchy].&[{539e50ef-3343-4615-b134-3639e5ade962}],

    [Work Item].[System_WorkItemType] ,

    Filter([Date].[Date].Members, ([Date].[Date].CurrentMember.MemberValue>=CDate("2012-06-10")

    AND [Date].[Date].CurrentMember.MemberValue<CDate("2012-06-23"))) )

    ON ROWS from [Team System] WHERE ([Measures].[Microsoft_VSTS_Scheduling_RemainingWork])


    Reply
  • Joel Joel Posted on Jun 15, 2012
    Hi Patrick,

    Unfortunately there is no way to modify the MDX query used by the dashboard.  Also, the remaining work trend chart will always be useless on day one of a sprint because there's no way to calculate a trend without having at least two points/days of data to work with.  Also, since we don't show dots on the graph for the actual values for each day, the graph ends up looking empty.

    Regards,
    Joel
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

    Reply
Back to Top
Skip Navigation LinksHome / Announcements / Forums / TFS Work Item Manager and Project Dashboard: TFS Project Dashboard > Remaining Work Trend