I’m thinking of precise Redmine burdown chart, which is not so simple.
- It has to build burdown chart for a given sprint (Version in Redmine).
- It has to account issues added to Version and removed from during the sprint.
- It, after all, has to account for what is considered “closed” status, which might be one of non-stock, custom statuses.
There are couple of Redmine addons, but for now I’m precautious about installing them. They are:
- ScrumAlliance Burndown is outdated and unsupported for now;
- RedmineBacklogs looks very promising and tasty.
For now, I do it by hand. I put together a SQL query to get me the data:
select i.id, i.subject, i.estimated_hours, j.created_on, jd.value, s.name new_status, old_versions.name old_version, new_versions.name new_version from issues i inner join journals j on j.journalized_id = i.id and j.journalized_type = 'Issue' inner join journal_details jd on jd.journal_id = j.id inner join versions on i.fixed_version_id = versions.id left outer join issue_statuses s on s.id = jd.value left outer join versions old_versions on jd.prop_key = 'fixed_version_id' and jd.old_value = old_versions.id left outer join versions new_versions on jd.prop_key = 'fixed_version_id' and jd.value = new_versions.id where (versions.name = '1.0.8' or old_versions.name = '1.0.8' or new_versions.name = '1.0.8') and property = 'attr' and jd.prop_key in ('status_id', 'fixed_version_id') order by i.id, created_on