256MbTeam / Redmine-Scrumbler

Easy to use plugin for Redmine. It allows users to use the Scrum/Agile process in projects. Scrumbler have interactive dashboard with the ability to configure for each sprint. Plugin adds Scrum Points field in every issue in project. Scrumbler as possible using the standard redmine structure of projects.
GNU General Public License v2.0
112 stars 41 forks source link

Possible to filter by tracker type regarding if scrum points should be counted #45

Open snicke opened 12 years ago

snicke commented 12 years ago

This is a feature request (for our company, a very important one!)

Use case:

Problem with Scrumbler:

Solution: It would be great if one could choose what tracker types that Scrumbler should include in it sum up of the scrum points in, for instance, the sprint backlog but also in the product backlog. One could say that one solution is that we put a "?" in the Story scrum points field, but we would like to know the points on the story level (if we filter out just the stories for instance) even if we don't want to count them in the sum up of the sprint backlog for instance.

We now try to use Scrumbler in sharp, important projects in our company and this issue could be a deal breaker. Therefore, it would be greatly appreciated if you could add the above feature as soon as possible if you think it is relevant. We hope you do. By default, we guess that all tracker types should be counted in the scrump point sum up in the backlogs with the option to turn it of tracker type by tracker type.

Thank's for a great job so far!

zloydadka commented 12 years ago

that feature will be realized in 1.50

only root issues have scrum points and shown in backlog, sutasks added to issue description.

may be on next week we can make release.

snicke commented 12 years ago

Just tested version 1.50. I'm very sorry to say that that caused a lot of issues for us and I assume for many others as well and that is not what I suggested above:

  1. Subtasks cannot be moved individually on the dashboard (be in different statuses). We need that possibility!
  2. Nothing happens in the burndown chart when a subtask is put in closed status = we (scrum master) cannot follow sprint progress in an effective way. We get a (non-wanted) "step-function" in the burn down when the whole story is solved instead of (wanted) many small steps when each sub task is solved.
  3. We would like to be able to use issues with sub tasks in three levels (Motherstory->substories->subtasks) and choose on what level to count the scrum points in the sprint log, dashboard and burndown (subtask level in our case). This is not possible in 1.50 since non of our sub tasks are shown in scrumbler and we do not want to show the Mother stories.

A very simple solution where needs from many different persons could be met is to do the following:

In http:///scrumbler_settings/trackers and http:///scrumbler_sprints/20/settings/trackers today you have in the settings for trackers a column called "Use?". Here you could simply add a column and call it "Count?" and add a check box for each tracker. If checked, the tracker's scrum points are added to the sum of scrum points in the sprint log and dashboard etc. If not checked, it is not counted.

But we need to be able to move around all tasks (especially sub-tasks) into the sprint log and on the dashboard and get the progress of these moves directly in the burn down chart!

We really need this feature described here and just cannot use Scrumbler in our company and projects if it works as in 1.50. What do you say about our suggestion?

Thanks for a great effort!