head 1.11; access; symbols pkgsrc-2026Q1:1.11.0.4 pkgsrc-2026Q1-base:1.11 pkgsrc-2025Q4:1.11.0.2 pkgsrc-2025Q4-base:1.11 pkgsrc-2025Q3:1.10.0.2 pkgsrc-2025Q3-base:1.10 pkgsrc-2025Q2:1.7.0.4 pkgsrc-2025Q2-base:1.7 pkgsrc-2025Q1:1.7.0.2 pkgsrc-2025Q1-base:1.7 pkgsrc-2024Q4:1.5.0.2 pkgsrc-2024Q4-base:1.5 pkgsrc-2024Q3:1.3.0.4 pkgsrc-2024Q3-base:1.3 pkgsrc-2024Q2:1.3.0.2 pkgsrc-2024Q2-base:1.3; locks; strict; comment @# @; 1.11 date 2025.09.26.14.53.39; author schmonz; state Exp; branches; next 1.10; commitid L0VKDG15Wd17BecG; 1.10 date 2025.09.10.00.50.55; author schmonz; state Exp; branches; next 1.9; commitid UYbFcftwWysTr6aG; 1.9 date 2025.07.27.15.43.13; author schmonz; state Exp; branches; next 1.8; commitid U9LAXUo7NePGPo4G; 1.8 date 2025.07.14.15.46.19; author schmonz; state Exp; branches; next 1.7; commitid zL5D7Pb93fQEgJ2G; 1.7 date 2025.03.12.23.40.22; author schmonz; state Exp; branches; next 1.6; commitid fOZrEubgu0wpSPMF; 1.6 date 2025.01.18.01.25.59; author schmonz; state Exp; branches; next 1.5; commitid 6syDoqsiKkifcUFF; 1.5 date 2024.11.09.16.53.45; author schmonz; state Exp; branches; next 1.4; commitid ClVCUKxYNHe2AZwF; 1.4 date 2024.10.27.19.47.58; author schmonz; state Exp; branches; next 1.3; commitid wPJkkyxP1nZHXkvF; 1.3 date 2024.06.04.14.46.18; author schmonz; state Exp; branches; next 1.2; commitid bAz0j9vK7dIbXFcF; 1.2 date 2024.06.02.15.36.58; author taca; state Exp; branches; next 1.1; commitid lc1mPDJOV3ybiqcF; 1.1 date 2024.05.18.01.46.32; author schmonz; state Exp; branches; next ; commitid n2vYkojfBPRybqaF; desc @@ 1.11 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 @@@comment $NetBSD$ bin/jirametrics ${GEM_HOME}/cache/${GEM_NAME}.gem ${GEM_LIBDIR}/bin/jirametrics ${GEM_LIBDIR}/lib/jirametrics.rb ${GEM_LIBDIR}/lib/jirametrics/aggregate_config.rb ${GEM_LIBDIR}/lib/jirametrics/aging_work_bar_chart.rb ${GEM_LIBDIR}/lib/jirametrics/aging_work_in_progress_chart.rb ${GEM_LIBDIR}/lib/jirametrics/aging_work_table.rb ${GEM_LIBDIR}/lib/jirametrics/anonymizer.rb ${GEM_LIBDIR}/lib/jirametrics/atlassian_document_format.rb ${GEM_LIBDIR}/lib/jirametrics/blocked_stalled_change.rb ${GEM_LIBDIR}/lib/jirametrics/board.rb ${GEM_LIBDIR}/lib/jirametrics/board_column.rb ${GEM_LIBDIR}/lib/jirametrics/board_config.rb ${GEM_LIBDIR}/lib/jirametrics/board_movement_calculator.rb ${GEM_LIBDIR}/lib/jirametrics/change_item.rb ${GEM_LIBDIR}/lib/jirametrics/chart_base.rb ${GEM_LIBDIR}/lib/jirametrics/columns_config.rb ${GEM_LIBDIR}/lib/jirametrics/css_variable.rb ${GEM_LIBDIR}/lib/jirametrics/cycletime_config.rb ${GEM_LIBDIR}/lib/jirametrics/cycletime_histogram.rb ${GEM_LIBDIR}/lib/jirametrics/cycletime_scatterplot.rb ${GEM_LIBDIR}/lib/jirametrics/daily_view.rb ${GEM_LIBDIR}/lib/jirametrics/daily_wip_by_age_chart.rb ${GEM_LIBDIR}/lib/jirametrics/daily_wip_by_blocked_stalled_chart.rb ${GEM_LIBDIR}/lib/jirametrics/daily_wip_by_parent_chart.rb ${GEM_LIBDIR}/lib/jirametrics/daily_wip_chart.rb ${GEM_LIBDIR}/lib/jirametrics/data_quality_report.rb ${GEM_LIBDIR}/lib/jirametrics/dependency_chart.rb ${GEM_LIBDIR}/lib/jirametrics/download_config.rb ${GEM_LIBDIR}/lib/jirametrics/downloader.rb ${GEM_LIBDIR}/lib/jirametrics/downloader_for_cloud.rb ${GEM_LIBDIR}/lib/jirametrics/downloader_for_data_center.rb ${GEM_LIBDIR}/lib/jirametrics/estimate_accuracy_chart.rb ${GEM_LIBDIR}/lib/jirametrics/estimation_configuration.rb ${GEM_LIBDIR}/lib/jirametrics/examples/aggregated_project.rb ${GEM_LIBDIR}/lib/jirametrics/examples/standard_project.rb ${GEM_LIBDIR}/lib/jirametrics/expedited_chart.rb ${GEM_LIBDIR}/lib/jirametrics/exporter.rb ${GEM_LIBDIR}/lib/jirametrics/file_config.rb ${GEM_LIBDIR}/lib/jirametrics/file_system.rb ${GEM_LIBDIR}/lib/jirametrics/fix_version.rb ${GEM_LIBDIR}/lib/jirametrics/flow_efficiency_scatterplot.rb ${GEM_LIBDIR}/lib/jirametrics/groupable_issue_chart.rb ${GEM_LIBDIR}/lib/jirametrics/grouping_rules.rb ${GEM_LIBDIR}/lib/jirametrics/hierarchy_table.rb ${GEM_LIBDIR}/lib/jirametrics/html/aging_work_bar_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html/aging_work_in_progress_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html/aging_work_table.erb ${GEM_LIBDIR}/lib/jirametrics/html/collapsible_issues_panel.erb ${GEM_LIBDIR}/lib/jirametrics/html/cycletime_histogram.erb ${GEM_LIBDIR}/lib/jirametrics/html/cycletime_scatterplot.erb ${GEM_LIBDIR}/lib/jirametrics/html/daily_wip_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html/estimate_accuracy_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html/expedited_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html/flow_efficiency_scatterplot.erb ${GEM_LIBDIR}/lib/jirametrics/html/hierarchy_table.erb ${GEM_LIBDIR}/lib/jirametrics/html/index.css ${GEM_LIBDIR}/lib/jirametrics/html/index.erb ${GEM_LIBDIR}/lib/jirametrics/html/index.js ${GEM_LIBDIR}/lib/jirametrics/html/sprint_burndown.erb ${GEM_LIBDIR}/lib/jirametrics/html/throughput_chart.erb ${GEM_LIBDIR}/lib/jirametrics/html_report_config.rb ${GEM_LIBDIR}/lib/jirametrics/issue.rb ${GEM_LIBDIR}/lib/jirametrics/issue_collection.rb ${GEM_LIBDIR}/lib/jirametrics/issue_link.rb ${GEM_LIBDIR}/lib/jirametrics/jira_gateway.rb ${GEM_LIBDIR}/lib/jirametrics/project_config.rb ${GEM_LIBDIR}/lib/jirametrics/rules.rb ${GEM_LIBDIR}/lib/jirametrics/self_or_issue_dispatcher.rb ${GEM_LIBDIR}/lib/jirametrics/settings.json ${GEM_LIBDIR}/lib/jirametrics/sprint.rb ${GEM_LIBDIR}/lib/jirametrics/sprint_burndown.rb ${GEM_LIBDIR}/lib/jirametrics/sprint_issue_change_data.rb ${GEM_LIBDIR}/lib/jirametrics/status.rb ${GEM_LIBDIR}/lib/jirametrics/status_collection.rb ${GEM_LIBDIR}/lib/jirametrics/throughput_chart.rb ${GEM_LIBDIR}/lib/jirametrics/tree_organizer.rb ${GEM_LIBDIR}/lib/jirametrics/trend_line_calculator.rb ${GEM_LIBDIR}/lib/jirametrics/user.rb ${GEM_LIBDIR}/lib/jirametrics/value_equality.rb ${GEM_HOME}/specifications/${GEM_NAME}.gemspec @ 1.10 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 @d33 2 @ 1.9 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 @d59 1 @ 1.8 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 @d11 1 @ 1.7 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 @d23 1 d33 1 d62 1 d77 1 @ 1.6 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 @@comment $NetBSD: PLIST,v 1.5 2024/11/09 16:53:45 schmonz Exp $ d15 1 @ 1.5 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 @@comment $NetBSD: PLIST,v 1.4 2024/10/27 19:47:58 schmonz Exp $ a27 1 ${GEM_LIBDIR}/lib/jirametrics/discard_changes_before.rb @ 1.4 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 @@comment $NetBSD$ a49 1 ${GEM_LIBDIR}/lib/jirametrics/html/data_quality_report.erb @ 1.3 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 @@comment $NetBSD: PLIST,v 1.2 2024/06/02 15:36:58 taca Exp $ d39 1 d53 1 @ 1.2 log @Remove extra @@pkgdir from PLIST This problem is fixed by revision 1.54 of lang/ruby/gem.mk. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1 2024/05/18 01:46:32 schmonz Exp $ d31 1 a34 2 ${GEM_LIBDIR}/lib/jirametrics/experimental/generator.rb ${GEM_LIBDIR}/lib/jirametrics/experimental/info.rb d50 1 a55 1 ${GEM_LIBDIR}/lib/jirametrics/html/story_point_accuracy_chart.erb a69 1 ${GEM_LIBDIR}/lib/jirametrics/story_point_accuracy_chart.rb @ 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 @@comment $NetBSD$ a76 2 @@pkgdir lib/ruby/gems/3.2.0/plugins @@pkgdir lib/ruby/gems/3.2.0/extensions @