Log message:
ruby-jirametrics: update to 2.7.3. Changes:

- Fixed an exception when two scrum projects had overlapping names like
  myproject and really_myproject. Our matcher wasn't precise enough and
  was matching where it shouldn't have.

Log message:
ruby-jirametrics: update to 2.7.1. Changes:

- Removed duplication in the data quality report
- Improved wording
- Removed unneeded code
- Updated URL's to point at JiraMetrics.org

Log message:
ruby-jirametrics: update to 2.7. Changes:

- Fixed misleading usage information when running jirametrics with
  no options.
- Fixed deprecated warning that would display if an unknown option was
  given to jirametrics
- Added info command from terminal for debugging purposes. If you are
  trying to figure out why the tool has calculated something in one way
  then this will dump out information about that particular issue that
  might be helpful. Usage jirametrics info ABC-123 where ABC-123 is the
  issue you want information on.
- Experimental: Trying out a way to visualize flow efficiency. I'm not
  convinced this is the right way yet but I'm making it public so I can
  get feedback. This may change. Add flow_efficiency_scatterplot to your
  configuration. If you want to try this from standard_project then
  specify the option show_experimental_charts: true.
- Fix: discard_changes_before was always intended to work either as an
  option under project or under html_report but there were cases where
  it was broken in the former case.
- Fix: There are legitimate cases where the calculated start and end
  times for an issue are exactly the same. Consider
  in_or_right_of_column where Done is legitimately to the right of that.
  In this case, we now pretend that the issue never started, which in
  almost every case will be the expected result anyway. In the cases
  where that isn't true, our configuration is probably wrong anyway.
- Deprecated: CycletimeConfig.started_time(Issue) and
  CycletimeConfig.stopped_time(Issue), which are now replaced with a
  single method that returns both:
  CycletimeConfig.started_stopped_times(Issue). This was necessary to
  fix the bug above, where started and stopped are the same.
- Added another quality check. It now checks for subtasks that aren't
  closed when the main issue is closed. This likely indicates that the
  issue is still in progress, despite what the status says.

Log message:
ruby-jirametrics: update to 2.6. Changes:

- When a status can't be found, it now just dumps a warning, rather than
  blowing up. This has been a source of frustration
  for many people just starting out with the tool so we're trying to get
  some more reasonable default behaviour.
- There is a new `Issue.flow_efficiency_numbers` method that is a first
  step towards visualizing flow efficiency. Note that none of the charts
  currently make use of this.
- By default, we assume that `flagged` means blocked but not all teams use
  the flag for that purpose. Added new setting to change that behaviour:
  `settings['flagged_means_blocked'] = false`.

Log message:
ruby-jirametrics: update to 2.5. Changes:

* Better error messages in the case where
  `settings['customfield_parent_links']` does not point to the
  correct field.
* Fixed exceptions when loading a scrum board that has no sprints.
* Added `no_earlier_than` option in `download` block. This is helpful
  when there were some big changes in the way we worked and we want to
  ignore all data before a specific date. This can be used together with
  `rolling_date_count` or by itself.
* `standard_project` now accepts `rolling_date_count` and
  `no_earlier_than` options.
* `expedited_priority_names` has been deprecated on the board block. Now
  set it through `settings['expedited_priority_names']`
* Provided more reasonable defaults for `DependencyChart`. Everything is
  still configurable if you don't like the defaults.
  * Less noisy in terms of console output.
  * Now excludes any link where both ends are already closed.
  * Now excludes `cloned by` that everyone was manually excluding anyway.
  * Now properly uses the calculated `done` rather than looking at status category.
  * `standard_project` and `aggregated_projects` now build on the new defaults.
* More reasonable defaults in settings. As above, these can be
  overridden if you don't like the defaults.
  * `"blocked_link_text"` now defaults to `["is blocked by"]`
  * `expedited_priority_names` now defaults to `['Critical', 'Highest']`

Log message:
ruby-jirametrics: update to 2.4. Changes:

- The unit tests have never worked reliably on JRuby due to
  differences between JRuby and MRI (what we develop on). Fixed all
  the inconsistencies so that unit tests now work reliably on both MRI
  and JRuby.
- Fixed bug where blocked and stalled were not being reported correctly
  in some cases.
- In the (rare) case that jira redirects to a different URL, follow
  those redirects.

Log message:
ruby-jirametrics: update to 2.3. Changes:

- Renamed story_point_accuracy_chart to estimate_accuracy_chart to more
  accurately capture what it does; it's not just story points. The old
  name will continue to work for now but has been deprecated and you'll
  get a warning.
- Explicitly force all files to be loaded in UTF-8 to fix bug #27
  happening on JRuby.

Log message:
Remove extra @pkgdir from PLIST

This problem is fixed by revision 1.54 of lang/ruby/gem.mk.

Log message:
Add ruby-jirametrics: Export Jira data and generate reports

Jira collects and maintains all kinds of useful data about your
workflow. Unfortunately it does a horrible job of exposing that in any
meaningful way. This project addresses that gap by giving you a way to
pull that data out of Jira and either dumping it into CSV files that
you can then manipulate yourself or by creating an HTML report with
key findings.