Warning: Declaration of LJXP_Walker_Category_Checklist::start_lvl(&$output, $depth, $args) should be compatible with Walker::start_lvl(&$output, $depth = 0, $args = Array) in /home/victorsergienko/victorsergienko.com/wp-content/plugins/lj-xp/lj-xp-options.php on line 796

Warning: Declaration of LJXP_Walker_Category_Checklist::end_lvl(&$output, $depth, $args) should be compatible with Walker::end_lvl(&$output, $depth = 0, $args = Array) in /home/victorsergienko/victorsergienko.com/wp-content/plugins/lj-xp/lj-xp-options.php on line 796

Warning: Declaration of LJXP_Walker_Category_Checklist::start_el(&$output, $category, $depth, $args) should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in /home/victorsergienko/victorsergienko.com/wp-content/plugins/lj-xp/lj-xp-options.php on line 796

Warning: Declaration of LJXP_Walker_Category_Checklist::end_el(&$output, $category, $depth, $args) should be compatible with Walker::end_el(&$output, $object, $depth = 0, $args = Array) in /home/victorsergienko/victorsergienko.com/wp-content/plugins/lj-xp/lj-xp-options.php on line 796

Warning: Cannot modify header information - headers already sent by (output started at /home/victorsergienko/victorsergienko.com/wp-content/plugins/lj-xp/lj-xp-options.php:796) in /home/victorsergienko/victorsergienko.com/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 60
code name / Precise Redmine burndown chart
Skip to content

Precise Redmine burndown chart

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:

For now, I do it by hand. I put together a SQL query to get me the data:

  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

  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
  (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


  1. srilu wrote:

    Where should this snippet be inserted in Redmine code base.

    Posted on 12-Mar-12 at 17:45 | Permalink
  2. It’s not into Redmine, it’s a SQL query to Redmine database.
    Its result is to be further processed by hand.

    Posted on 23-Mar-12 at 20:24 | Permalink
  3. tourl.org wrote:

    A fleet enema works as a hyper-osmotic laxative that attracts
    in water into the gastrointestinal tract.

    Posted on 02-Aug-16 at 21:42 | Permalink
  4. Sam wrote:

    I do not know if it’s just me or if perhaps everybody else experiencing problems with your website.
    It appears as if some of the written text on your posts are running off the screen. Can someone else please provide feedback and let me
    know if this is happening to them too? This might be a problem with my internet browser because I’ve had this
    happen before. Thanks

    Posted on 27-Sep-16 at 07:15 | Permalink

Post a Comment

Your email is never published nor shared.