story/task board cost too much time to fetch stories/tasks when there is no current iteration

4 posts, 0 answers
  1. felix
    felix avatar
    2 posts
    Member since:
    Feb 2014

    Posted 10 Feb 2014 Link to this post

    hi.
    when i open story/task board, teampulse will detect the current iteration automatically and apply it as  filter ,  so it only show the stories/tasks of currently iteration, this bahavior is good , i love it.
    but when today is not in any existed iteration, there is no current iteration, and teampulse will select all of the existed iterations( all the iteration checkbox are checked on iteration filter panel), and try to fetch all stories/tasks in those iterations.
    this is bad, our project has created many iterations and more than thousands of stories/tasks, when i entered taskboard page today, it cost me almost two minutes waiting for the page show all tasks, the cursor is a rolling circle ,and i can not  click page to alter filter, if i click two much , the page will freeze and have no response, i have to wait for the page finishing the fetching and after the cursor becomes back to arrow, i change the iteration filter to my desired one.

    i wish to change this behavior, when there is no current iteration, do not select all iterations as filter for me automatically, but select no itererations in filter, then i can select my desire one.

    thanks
  2. Georgi
    Admin
    Georgi avatar
    20 posts

    Posted 10 Feb 2014 Link to this post

    This was fixed in the latest versions of TeamPulse. Since we introduced the HTML5 interface the filtering and sorting  is handled in another way so that your browser will not freeze or crash by the large amount of data.
  3. felix
    felix avatar
    2 posts
    Member since:
    Feb 2014

    Posted 12 Feb 2014 in reply to Georgi Link to this post

    thanks! but my company may be reluctant to upgrade teampulse to newest version :(
  4. Georgi
    Admin
    Georgi avatar
    20 posts

    Posted 12 Feb 2014 Link to this post

    If that's the case - I'm wondering if creating one very long iteration (for example - with the same duration as the project itself) could help you with that problem you have. That iteration won't have any items assigned to it and should be quite far into the future. So if it gets selected because it matches the "Current condition it won't have any data to display -> no freezing and crashes.

    Hope this helps.


Back to Top