head	1.25;
access;
symbols
	pkgsrc-2026Q1:1.25.0.2
	pkgsrc-2026Q1-base:1.25
	pkgsrc-2025Q4:1.24.0.2
	pkgsrc-2025Q4-base:1.24
	pkgsrc-2025Q3:1.19.0.2
	pkgsrc-2025Q3-base:1.19
	pkgsrc-2025Q2:1.14.0.4
	pkgsrc-2025Q2-base:1.14
	pkgsrc-2025Q1:1.14.0.2
	pkgsrc-2025Q1-base:1.14
	pkgsrc-2024Q4:1.9.0.2
	pkgsrc-2024Q4-base:1.9
	pkgsrc-2024Q3:1.4.0.2
	pkgsrc-2024Q3-base:1.4
	pkgsrc-2024Q2:1.2.0.2
	pkgsrc-2024Q2-base:1.2;
locks; strict;
comment	@# @;


1.25
date	2026.01.13.16.54.16;	author schmonz;	state Exp;
branches;
next	1.24;
commitid	OqjxP3q4HdqgLfqG;

1.24
date	2025.11.08.22.55.52;	author schmonz;	state Exp;
branches;
next	1.23;
commitid	mEyvYVvo5lUQSNhG;

1.23
date	2025.10.09.15.04.54;	author schmonz;	state Exp;
branches;
next	1.22;
commitid	f6Myo6rCuNT3fUdG;

1.22
date	2025.10.04.19.42.34;	author schmonz;	state Exp;
branches;
next	1.21;
commitid	ao1mfd4rSryhWhdG;

1.21
date	2025.10.02.20.14.33;	author schmonz;	state Exp;
branches;
next	1.20;
commitid	4o0FWhfJbDsfb2dG;

1.20
date	2025.09.26.14.53.39;	author schmonz;	state Exp;
branches;
next	1.19;
commitid	L0VKDG15Wd17BecG;

1.19
date	2025.09.10.18.43.59;	author schmonz;	state Exp;
branches;
next	1.18;
commitid	WVZQKk5OYon1ocaG;

1.18
date	2025.09.10.00.50.55;	author schmonz;	state Exp;
branches;
next	1.17;
commitid	UYbFcftwWysTr6aG;

1.17
date	2025.08.19.01.23.30;	author schmonz;	state Exp;
branches;
next	1.16;
commitid	GM9VhiExf4SUkh7G;

1.16
date	2025.07.27.15.43.13;	author schmonz;	state Exp;
branches;
next	1.15;
commitid	U9LAXUo7NePGPo4G;

1.15
date	2025.07.14.15.46.19;	author schmonz;	state Exp;
branches;
next	1.14;
commitid	zL5D7Pb93fQEgJ2G;

1.14
date	2025.03.12.23.40.22;	author schmonz;	state Exp;
branches;
next	1.13;
commitid	fOZrEubgu0wpSPMF;

1.13
date	2025.02.08.01.29.08;	author schmonz;	state Exp;
branches;
next	1.12;
commitid	LbZQkVTk14quxBIF;

1.12
date	2025.01.22.04.25.22;	author schmonz;	state Exp;
branches;
next	1.11;
commitid	TztrkRB7JEXO3rGF;

1.11
date	2025.01.18.01.25.59;	author schmonz;	state Exp;
branches;
next	1.10;
commitid	6syDoqsiKkifcUFF;

1.10
date	2024.12.31.04.18.29;	author schmonz;	state Exp;
branches;
next	1.9;
commitid	AR1zOZoSUNajJBDF;

1.9
date	2024.11.13.23.43.09;	author schmonz;	state Exp;
branches;
next	1.8;
commitid	pDF5yArEoG2wIxxF;

1.8
date	2024.11.12.00.40.34;	author schmonz;	state Exp;
branches;
next	1.7;
commitid	kuVYQ8v7uDoc6ixF;

1.7
date	2024.11.09.16.53.45;	author schmonz;	state Exp;
branches;
next	1.6;
commitid	ClVCUKxYNHe2AZwF;

1.6
date	2024.10.27.19.47.58;	author schmonz;	state Exp;
branches;
next	1.5;
commitid	wPJkkyxP1nZHXkvF;

1.5
date	2024.10.04.16.10.16;	author schmonz;	state Exp;
branches;
next	1.4;
commitid	5cnKrJNFYhYRumsF;

1.4
date	2024.09.22.18.11.20;	author schmonz;	state Exp;
branches;
next	1.3;
commitid	Sj1Q8xnN9ywjyPqF;

1.3
date	2024.08.19.21.56.25;	author schmonz;	state Exp;
branches;
next	1.2;
commitid	frgrDT5O6QaiTtmF;

1.2
date	2024.06.04.14.46.18;	author schmonz;	state Exp;
branches;
next	1.1;
commitid	bAz0j9vK7dIbXFcF;

1.1
date	2024.05.18.01.46.31;	author schmonz;	state Exp;
branches;
next	;
commitid	n2vYkojfBPRybqaF;


desc
@@


1.25
log
@ruby-jirametrics: update to 2.20.1. Changes:

- Fixed an exception when using cookie based authentication.
@
text
@# $NetBSD: Makefile,v 1.24 2025/11/08 22:55:52 schmonz Exp $

DISTNAME=	jirametrics-2.20.1
CATEGORIES=	devel

MAINTAINER=	schmonz@@NetBSD.org
HOMEPAGE=	https://jirametrics.org/
COMMENT=	Export Jira data and generate reports
LICENSE=	apache-2.0

DEPENDS+=	${RUBY_PKGPREFIX}-random-word>=2.1.1:../../textproc/ruby-random-word
DEPENDS+=	${RUBY_PKGPREFIX}-require_all>=3.0.0:../../devel/ruby-require_all
DEPENDS+=	${RUBY_PKGPREFIX}-thor>=1.2.2:../../devel/ruby-thor

USE_LANGUAGES=	# none

.include "../../lang/ruby/gem.mk"
.include "../../mk/bsd.pkg.mk"
@


1.24
log
@ruby-jirametrics: update to 2.20. Changes:

- Performance: Put some caching in the calculation logic. On our test
  data here, this cuts the time to export in half. If you want to test
  before and after for yourself, you can disable the caching by putting
  this line in your settings `"cache_cycletime_calculations": false`
- Fixed a bug in rendering of the aging work in progress table that
  could show some items in the wrong position on the chart. Note that
  the age shown in the tooltip was always correct, just not always where
  the dot was drawn.
- Fixed an exception when an incorrectly spelled status is specified in
  `status_category_mappings` and the config is using standard project.
  It should have stopped the export anyway but this exception provided a
  very misleading error message.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.23 2025/10/09 15:04:54 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.20
@


1.23
log
@ruby-jirametrics: update to 2.19. Changes:

- One more change for Jira Data Center (Cloud is unaffected by this
  release), to address the point from 2.18 below. The downloader is
  working for Data Center. Note that the caching issue discussed in 2.17
  is only fixed for Jira Cloud. See the FAQ for an explanation of why
  our support for Data Center is deviating from our support for Cloud.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.22 2025/10/04 19:42:34 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.19
@


1.22
log
@ruby-jirametrics: update to 2.18. Changes:

- Fixed a number of subtle bugs having to do with the new
  changelog logic.
- This release will force a refresh of the local cache and a fresh
  download of everything. For this reason, it's not just considered a
  bug fix release.
- Reverted download logic for Data Center as it appears we broke
  something there but we have no way to test against data center so
  we're pushing this and hoping for feedback from people using it in
  that environment. Note that Cloud is fine and the vast majority of
  people using this tool are on Cloud.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.21 2025/10/02 20:14:33 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.18
@


1.21
log
@ruby-jirametrics: update to 2.17.1. Changes:

- Fixed bug where issues with a LOT of changes in the changelog
  wouldn't download all of those changes and therefore some
  calculations were wrong.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.20 2025/09/26 14:53:39 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.17.1
@


1.20
log
@ruby-jirametrics: update to 2.17. Changes:

- We cache issues locally to improve download performance. There were
  two problems with our caching logic that have now been fixed. The
  first is that if an issue is deleted in Jira (not closed but actually
  deleted), then it remained in our cache and could show in the reports
  as an incorrectly aging item. The second is that over time, the cache
  continued to grow, taking up space on your local machine that it
  didn't need.
    - The first time you run a download with this version, there will be
      a one-time correction where issues that fell into this situation
      are deleted, and you may notice fewer data points in the charts.
    - Additionally, we no longer do fully incremental downloads, so
      the time it takes to do a download may be longer now although it
      should still be faster than it was before we implemented the
      incremental feature. This is the trade-off for cache
      invalidation accuracy.
- Fixed exception when the configuration file can't be found.
- Daily View: Now display the year in history timestamps. This can be
  important when an issue has been active for over a year. Yes, that
  happens more often than you might believe.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.19 2025/09/10 18:43:59 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.17
@


1.19
log
@ruby-jirametrics: update to 2.16. Changes:

- v2.15 introduced a bug that caused the tool to immediately crash on
  loading, for some machines. That’s fixed.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.18 2025/09/10 00:50:55 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.16
@


1.18
log
@ruby-jirametrics: update to 2.15. Changes:

- All reports are now foldable. You can collapse or expand as needed.
- Standardized how folding is done across the report, which means things
  will look a little different in places, but will generally be more
  consistent.
- Fixed exception in `jirametrics info` when a comment contains ADF,
  Jiras “rich text” format.
- Better error messages in one case where Jira was returning HTML
  instead of JSON.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.17 2025/08/19 01:23:30 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.15
@


1.17
log
@ruby-jirametrics: update to 2.14. Changes:

- If a file prefix is reused across projects in the same configuration
  then files will get overridden and generally bad things will happen.
  When it happens, it's almost certainly a mistake and probably due to
  too much copy/pasting. We now detect when that's happened and dump
  out an error.
- Fixed bug where an item could sometimes say 'stalled by
  inactivity: days' (note the missing day count), when in fact it
  wasn't stalled at all.
- On the Daily View...
    - Child issues are now collapsible
    - We had previously excluded child issues that are done, but now we
      show them, albeit with less detail.
- Fixed exception when an ADF document is returned with no
  content section.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.16 2025/07/27 15:43:13 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.14
@


1.16
log
@ruby-jirametrics: update to 2.13. Changes:

- When on Jira Cloud (not Data Centre or Server), we now use the v3 API
  to retrieve issue details because the v2 API is being removed. Data
  Centre and Server, on the other hand, only support the v2 API so we
  cannot use the v3 API with them. Until now, all Jira installations
  supported the same API’s and this is no longer true. If you notice
  different behaviour in Cloud then let us know.
- When on Jira Cloud, we now have better support for the rich text
  formatting that is available. Cloud and Data Centre return that rich
  text data in very different formats and we’ve been focused on making
  cloud look good right now.
- When javascript is disabled, most of the charts won’t work and a
  large message will be displayed at the top of the page explaining
  that. Despite being large, several people reported not seeing this
  message and not understanding why the report wasn’t showing anything
  useful. Now that message is even more obnoxious and in your face.
  Javascript needs to be enabled for any of this to work.
- Atlassian has begun rolling out the naming change from `Issue` to
  `Work item` and this has broken some of our parsing logic. If you were
  seeing an error like `Issue(ISSUE_ID) Can't parse link text: This work
  item clones OTHER_ISSUE_ID` then that’s now fixed.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.15 2025/07/14 15:46:19 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.13
@


1.15
log
@ruby-jirametrics: update to 2.12.1. Changes:

- New chart: Daily View that is an optimized view for use during the
  daily standup/sprint/meeting.
- Estimation changes
    - The sprint_burndown and estimate_accuracy_chart both pull the
      estimate from the issue history. In the past we've looked for the
      field "Story Points" which works just fine in an English instance
      of Jira but fails for many (all?) non-English instances.
    - Also changed them to support time based estimates, if the board is
      configured to use them.
- Aging Work Table now shows the issue priority.
- Bug: Fixed exception when downloading for the first time and
  status_category_mappings are already set.
- New criteria that can be used with `start_at` or `stop_at`:
  `first_time_visible_on_board`
- Whenever we display statuses now, we display them in the format
  `"Review":10011` rather than just `Review`. We do this to remove any
  ambiguity around which specific `Review` status we're talking about as
  there may be several.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.14 2025/03/12 23:40:22 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.12.1
@


1.14
log
@ruby-jirametrics: update to 2.11. Changes:

- Aging work in progress chart - improvements
  - We've always shown the 85% point in each column so we can
    immediately see if an item is an outlier. We now show the 50%, 85%,
    98%, and 100% points as well.
  - The CSS variable `--aging-work-in-progress-chart-shading-color` has
    been removed and replaced with four new ones for the percentile
    colours. This will only matter to you if you're customizing the CSS.
  - We no longer show all the columns, only those that are considered
    "in progress", to reduce clutter.
- Aging work table - improvements
  - In addition to the current age, we display how much longer it's
    likely to take to finish this. This is a forecast, based on
    historical data for this board.
  - If an item has a due date then we display that. We also show if
    we're likely to complete by that date.
- If Javascript is disabled in the browser then almost none of the
  charts will be visible and the report will be largely useless. We now
  display a warning the the top of the page if this is the case. This
  has been reported as a frequent problem when reports are stored on
  Sharepoint as it will disable javascript by default and then people
  are left wondering why the report isn't helpful.
- Bug: Fixed obscure exception when one issue had been blocked on
  another issue that isn't currently downloaded AND we were using either
  `currently_in_status` or `currently_in_status_category`.
- Bug: Fixed bug where `info` was only being written to the log and not
  to the console, making it seem if it weren't working at all.
- `info` improvement: Statuses now list the id of the status as well
  as the name.
- Jira will happily let you create two columns on a board with the same
  name. Unfortunately there are no id's with those columns so there is
  now no way to tell them apart. This change will add a numerical
  suffix such as Backlog-2 to duplicate columns so that we're able to
  work with them.

Updating during pkgsrc careful mode as this is a leaf package and
contains bugfixes.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.13 2025/02/08 01:29:08 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.11
@


1.13
log
@ruby-jirametrics: update to 2.10. Changes:

- Cycletime Histogram improvements
    - Added a collection of statistics under the chart. Thanks to
      Fernando Cuenca for the contribution.
    - Added percentile lines on the chart.
- Bug: Fixed exception in rare case when comparing output rows
- Bug: Fixed some timezone logic, for which the unit tests only failed
  when being run somewhere other than the Pacific Timezone.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.12 2025/01/22 04:25:22 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.10
@


1.12
log
@ruby-jirametrics: update to 2.9.1. Changes:

- Fixed an exception when running the tool for the very first time.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.11 2025/01/18 01:25:59 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.9.1
@


1.11
log
@ruby-jirametrics: update to 2.9. Changes:

- Status/category mappings have been an ongoing pain point for a long
  time. When a status gets removed from Jira, all of a sudden the
  reports can't be generated until someone sets up a
  status_category_mapping and it isn't always obvious what the values
  should be. We are now much better at guessing the correct mapping and
  will use that guess where we can. You will see suggestions in the
  output, where we guessed and what values we used.
- Bug: Fixed an exception in the data quality report when a status can't
  be found at all.
- On StatusCollection, there used to be methods todo, in_progress, and
  done that would return the names of statuses that matched those
  categories. Since we now know that names aren't unique, those
  methods have just been removed. They hadn't been documented before
  and were never officially supported so we aren't going through a
  deprecation process.
- Bug: Fixed case where the quality report didn't always correctly warn
  about items that had been moved back to the backlog.
- Whenever a status or status-category is specified, we can do a better
  job of identifying typos.
- The methods first_time_in_status_category, still_in_status_category,
  and currently_in_status_category...
    - ...will now accept names ("Done"), name/ID pairs ("Done:3"), or
      just ID's ("3"). If the name and ID are both specified then we
      will verify that they match and raise an error if they don't.
    - ...will also accept one of the following keys :new,
      :indeterminate, or :done to reflect the three categories. The code
      had previously worked only with names but those names will change
      in non-English installations of Jira so the keys are better.
        - Why is it called "indeterminate"? That's a question for
          Atlassian; we just use the key names that Jira uses
          internally.
- standard_project now uses the keys, which should make things easier
  for non-English instances.
- Added a quality check for the case where an issue is identified
  as being blocked by another issue and yet that other issue is
  already closed. This is clearly a mistake and the quality report
  will now show it.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.10 2024/12/31 04:18:29 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.9
@


1.10
log
@ruby-jirametrics: update to 2.8. Changes:

The main focus of this release is improving the experience with better
error messages, and more helpful suggestions.

- Bug: It wasn't possible to clear the description or title texts on
  individual charts.
- Added first_time_label_added for determining start or end times.
- Moved the generated timestamp of the report to the footer.
- Added the version number of JiraMetrics to the footer so there's
  a record of what version of the tool was used for this
  particular report.
- no_earlier_than previously only worked during the download stage and
  this proved to be confusing as there was no effect when just doing an
  export. It now works at both points and should be clearer as to what
  is actually happening.
- All the methods like first_time_in_status used to return a Time object
  and now return the ChangeItem that happened at that time. Unless
  you're writing your own methods, you likely won't even be aware that
  anything changed here. If you are, then you'll get a warning when
  returning a Time. The reason for this change is to give more context
  that will be useful in future reporting.
- Bug: We've discovered that Jira allows for multiple statuses with the
  same name and when this happens, it broke some of our existing logic.
  Fixes for this case have been added.
  - In standard_project, when specifying status_category_mappings, it's
    now possible to specify the ID at the same time as the name.
    "Review" will continue to specify just the name and "Review:4" will
    specify the name and also an ID of 4.
  - Status ID's are now mandatory and the tool will do it's best to
    guess the correct one, however it won't be able to guess in every
    case and you'll now get a error when it can't.
- Bug: some status category logic was failing in non-English instances
  of Jira because we were relying on category names, rather than keys.
  We think we've caught all the cases of this.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.9 2024/11/13 23:43:09 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.8
@


1.9
log
@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.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.8 2024/11/12 00:40:34 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.7.3
@


1.8
log
@ruby-jirametrics: update to 2.7.2. Changes:

- Fixed a regression that prevented a new full download from working.
  Incremental downloads hadn’t been affected.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.7 2024/11/09 16:53:45 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.7.2
@


1.7
log
@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
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.6 2024/10/27 19:47:58 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.7.1
@


1.6
log
@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.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.5 2024/10/04 16:10:16 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.7
d7 1
a7 1
HOMEPAGE=	https://github.com/mikebowler/jirametrics/
@


1.5
log
@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`.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.4 2024/09/22 18:11:20 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.6
@


1.4
log
@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']`
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.3 2024/08/19 21:56:25 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.5
@


1.3
log
@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.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.2 2024/06/04 14:46:18 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.4
@


1.2
log
@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.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.1 2024/05/18 01:46:31 schmonz Exp $
d3 1
a3 1
DISTNAME=	jirametrics-2.3
@


1.1
log
@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.
@
text
@d1 1
a1 1
# $NetBSD$
d3 1
a3 1
DISTNAME=	jirametrics-2.2.1
@