Why is my dashboard burn down not correct?

7 posts, 0 answers
  1. Rick
    Rick avatar
    1 posts
    Member since:
    Feb 2012

    Posted 17 Sep 2012 Link to this post

    Hi all,

    I'm currently in a sprint with 6 stories. 
    Total of 86 task and 15 are done.

    If i go to the dashboard and select the correct sprint it tells me that I only have 10 tasks and none are done.
    Can someone explain what I do wrong or what i should check to find the problem?
  2. Jordan
    Admin
    Jordan avatar
    123 posts

    Posted 19 Sep 2012 Link to this post

    Hi Rick,

    Is it possible that those tasks has been made done in the previous iteration and after that you changed the iteration of the story?

    We made that behavior because we want to show it work that has been done in previous iteration. 

     Greetings,

    Jordan
    the Telerik team
  3. Rick
    Rick avatar
    1 posts
    Member since:
    Feb 2012

    Posted 19 Sep 2012 Link to this post

    Hi Jordan,

    No we first added the stories to the itteration. Then used the new template functionality to add base steps. After that the team added more tasks and estimates before we started the sprint. 

    But we did had some syncronization problems for the sprint with TFS. Some how I ended up with 2 times the same itteration. I moved all the stories to the correct sprint and removed the other. This might have caused the problem but I'm not sure. 
    Is there a way that i can check the SQL database? Because somehow I need to fix the dashboard...

    Regards
  4. Kees
    Kees avatar
    3 posts
    Member since:
    Sep 2012

    Posted 20 Sep 2012 Link to this post

    Maybe stories have moved from on iteration to another, but  in general we have this problem.

    The tasks are open and connected to stories that are part of the sprint, but the number of tasks are not right as well as the estimate etc.
  5. Kees
    Kees avatar
    3 posts
    Member since:
    Sep 2012

    Posted 20 Sep 2012 Link to this post

    Jordan

    It is not a solution.

    Stories can move from sprint to another sprint (while open) with their tasks (while still open)

    But in the reporting it is not updated.. it just doesn't represent the truth.

    In a simple sample project with for example 3 sprints and 10 stories spread around 3 sprints with all 3 tasks you will see that once you move something .. the whole reporting is broken.

    Please solve it and release a hotfix.. so we can start using the reporting part .. which is now useless
  6. Jordan
    Admin
    Jordan avatar
    123 posts

    Posted 20 Sep 2012 Link to this post

    Hello Kees,

    You initial problem should be related to the changes you've made to fix the sync issue with the second iteration. Most probably the story and task iterations become out of sync.

    Can you execute the following script and tell us the result? 

    You lost your history because you've create a new iteration with the same name and you've deleted the original one. In our history we keep the id of previous iteration and even if the names match the data that we have is for the deleted iteration.

    -- Get your current iteation
    -- Replace 'Iteration 2' with 'AX2009 Member Portal V1.1' and ProjectID 27 with 26
     
    DECLARE @iteration int
    SET @iterationID = (SELECT TOP 1 IterationID FROM Iteration WHERE Name like 'Iteration 2' and ProjectID = 27)
    SELECT @iterationID
     
    -- Select the tasks that has different iterations
     
    DECLARE @tasks TABLE (id int)
     
    INSERT INTO @tasks(id)
    SELECT Task.TaskID
    FROM Task inner join Story ON Task.ParentID = Story.StoryID
    WHERE Task.ParentType = 'Story' and Task.IterationID != Story.IterationID and Story.IterationID = @iterationID
     
    SELECT * FROM @tasks
     
    UPDATE Task
    SET
        IterationID = @iterationID
    WHERE TaskID IN (SELECT id FROM @tasks)


    All the best,
    Jordan
    the Telerik team
  7. Kees
    Kees avatar
    3 posts
    Member since:
    Sep 2012

    Posted 21 Sep 2012 Link to this post

    Hi

    This eavening we sheduled to update the database after a backup has made and we can review the result then.

    Hopefully a more permanent solution will be available later.


Back to Top