https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.auld@openfifth.co.uk | |, clemens.tubach@kit.edu, | |michaela.sieber@kit.edu --- Comment #1 from Michaela Sieber <michaela.sieber@kit.edu> --- Hm yes, that's why we only do monthly harvesting. It could be an option to force the monthly harvesting in the background and start separate background-jobs per month, even if users enter a period with several months -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Comma delimited| |Karlsruhe Institute of list of Sponsors| |Technology (KIT) Priority|P5 - low |P2 Blocks| |43904 Status|NEW |ASSIGNED Summary|Data not available for |Allow monthly harvesting |certain months should not |only so Data not available |result in a complete |for certain months do not |failure of the harvest |result in a complete | |failure of the harvest Target Milestone|--- |26.11 Assignee|koha-bugs@lists.koha-commun |matt.blenkinsop@openfifth.c |ity.org |o.uk Sponsorship status|--- |Sponsored --- Comment #2 from Michaela Sieber <michaela.sieber@kit.edu> --- Link to Omnibus Bug to track all ERM Usage Improvements Switch to monthly harvesting, so that the COUNTER log can distinguish which months had no usage. This means the user can still select a date range in the interface, but in the background this range is split into individual background jobs per month, similar to how this is already done for the report types. A migration script must be provided to retroactively bring existing entries into the new structure. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43904 [Bug 43904] [OMNIBUS] ERM Usage Improvements -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |41307 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307 [Bug 41307] Improve erm_counter_logs and automatically indicate when a harvest job is completed (successfully or with an error) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Christian Nelson <christian.nelson@uwasa.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.nelson@uwasa.fi -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johanna.miettunen@haaga-hel | |ia.fi, | |jvinke@austinseminary.edu, | |nick@bywatersolutions.com, | |veli-matti.hakkinen@jyu.fi Text to go in the| |COUNTER usage harvesting release notes| |has been improved to | |process each month | |separately. This prevents | |missing or | |not-yet-available usage | |data for one month from | |causing the entire | |harvesting process to fail. | |Available data for other | |months can now be harvested | |successfully. This change | |is a prerequisite for the | |improvements introduced in | |Bug 38822. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #209217|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #209219|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #11 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 210197 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210197&action=edit Bug 41294: Split harvest period into monthly jobs A harvest over several months ran as one background job and one SUSHI request. Providers serve usage per month, a failure in one month lost the whole range, and the counter log held one row for the range so a month could not be retried on its own. Koha::ERM::EUsage::UsageDataProvider->harvest_periods splits a date range into one period per calendar month: the first period starts on the begin date, the last ends on the end date, equal dates give one period. The dates are calendar days in the floating time zone, so the split does not depend on the server time zone or on daylight saving. An end date after today is reduced to today; a begin date after today throws BadParameter. enqueue_sushi_harvest_jobs enqueues one job per report type and month and returns the jobs with their report type and period. The process_SUSHI_response API returns that list, accepts equal dates, and answers 400 with the message of a BadParameter exception. Test plan: 1. On the data providers list, click "Run now" for a provider and ask for a period of three months. The message lists, per report type, "3 jobs queued for report type TR_J1" with one link per month 2. Click a month link: the background job page shows the report type and the harvest period of that month only, with one month of data 3. Go to E-resource management > Home: the "Latest SUSHI Counter jobs" widget shows the three jobs with a "Report type" and a "Period" column 4. Let one month fail (for example disable the network during the harvest): the failed job page names the report type and the period, and the other months still finish 5. Run the cronjob: misc/cronjobs/erm_run_harvester.pl --begin-date 2024-01-01 \ --end-date 2024-03-31 --dry-run It lists, per provider and report type, the three monthly periods that would be enqueued and enqueues nothing 6. Run it without --dry-run: it reports the jobs it enqueued per report type with their month range and job ids, and the jobs appear in the widget 7. Run it with --begin-date set to a date after today: the script stops with an error message and enqueues nothing 8. Run it with --end-date in the future: the end date is reduced to today and no error is reported 9. prove -l t/db_dependent/Koha/ERM/EUsage/UsageDataProvider.t \ t/db_dependent/api/v1/erm_usage_data_providers.t \ t/db_dependent/Koha/BackgroundJobs/ErmSushiHarvester.t 10. yarn cypress run --spec t/cypress/integration/ERM/DataProviders_spec.ts yarn cypress run --spec t/cypress/integration/ERM/ModuleDashboard_spec.ts Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #13 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 210199 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210199&action=edit Bug 41294: Update the job report for the background job and cronjob The background job page shows the report type and the harvest period of each monthly job, and names the period in the failure message; both strings are translatable. The cronjob reports the jobs it enqueued per report type, in the order of the provider's report types, with the month range and the job ids. --dry-run now lists the report types and the monthly periods that would be enqueued for each provider instead of printing nothing. A bad date range stops the script with the message of the exception. Assisted-by: Sonnet 5 (Anthropic) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Clemens Tubach <clemens.tubach@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #15 from Clemens Tubach <clemens.tubach@kit.edu> --- Created attachment 210237 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210237&action=edit Bug 41294: Split harvest period into monthly jobs A harvest over several months ran as one background job and one SUSHI request. Providers serve usage per month, a failure in one month lost the whole range, and the counter log held one row for the range so a month could not be retried on its own. Koha::ERM::EUsage::UsageDataProvider->harvest_periods splits a date range into one period per calendar month: the first period starts on the begin date, the last ends on the end date, equal dates give one period. The dates are calendar days in the floating time zone, so the split does not depend on the server time zone or on daylight saving. An end date after today is reduced to today; a begin date after today throws BadParameter. enqueue_sushi_harvest_jobs enqueues one job per report type and month and returns the jobs with their report type and period. The process_SUSHI_response API returns that list, accepts equal dates, and answers 400 with the message of a BadParameter exception. Test plan: 1. On the data providers list, click "Run now" for a provider and ask for a period of three months. The message lists, per report type, "3 jobs queued for report type TR_J1" with one link per month 2. Click a month link: the background job page shows the report type and the harvest period of that month only, with one month of data 3. Go to E-resource management > Home: the "Latest SUSHI Counter jobs" widget shows the three jobs with a "Report type" and a "Period" column 4. Let one month fail (for example disable the network during the harvest): the failed job page names the report type and the period, and the other months still finish 5. Run the cronjob: misc/cronjobs/erm_run_harvester.pl --begin-date 2024-01-01 \ --end-date 2024-03-31 --dry-run It lists, per provider and report type, the three monthly periods that would be enqueued and enqueues nothing 6. Run it without --dry-run: it reports the jobs it enqueued per report type with their month range and job ids, and the jobs appear in the widget 7. Run it with --begin-date set to a date after today: the script stops with an error message and enqueues nothing 8. Run it with --end-date in the future: the end date is reduced to today and no error is reported 9. prove -l t/db_dependent/Koha/ERM/EUsage/UsageDataProvider.t \ t/db_dependent/api/v1/erm_usage_data_providers.t \ t/db_dependent/Koha/BackgroundJobs/ErmSushiHarvester.t 10. yarn cypress run --spec t/cypress/integration/ERM/DataProviders_spec.ts yarn cypress run --spec t/cypress/integration/ERM/ModuleDashboard_spec.ts Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Clemens Tubach <clemens.tubach@kit.edu> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #17 from Clemens Tubach <clemens.tubach@kit.edu> --- Created attachment 210239 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210239&action=edit Bug 41294: Update the job report for the background job and cronjob The background job page shows the report type and the harvest period of each monthly job, and names the period in the failure message; both strings are translatable. The cronjob reports the jobs it enqueued per report type, in the order of the provider's report types, with the month range and the job ids. --dry-run now lists the report types and the monthly periods that would be enqueued for each provider instead of printing nothing. A bad date range stops the script with the message of the exception. Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Clemens Tubach <clemens.tubach@kit.edu> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #210237|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #210240|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Lisa G <lgonzalez@palni.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lgonzalez@palni.edu -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #21 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 210902 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210902&action=edit Bug 41294: Split harvest period into monthly jobs A harvest over several months ran as one background job and one SUSHI request. Providers serve usage per month, a failure in one month lost the whole range, and the counter log held one row for the range so a month could not be retried on its own. Koha::ERM::EUsage::UsageDataProvider->harvest_periods splits a date range into one period per calendar month: the first period starts on the begin date, the last ends on the end date, equal dates give one period. The dates are calendar days in the floating time zone, so the split does not depend on the server time zone or on daylight saving. An end date after today is reduced to today; a begin date after today throws BadParameter. enqueue_sushi_harvest_jobs enqueues one job per report type and month and returns the jobs with their report type and period. The process_SUSHI_response API returns that list, accepts equal dates, and answers 400 with the message of a BadParameter exception. Test plan: 1. On the data providers list, click "Run now" for a provider and ask for a period of three months. The message lists, per report type, "3 jobs queued for report type TR_J1" with one link per month 2. Click a month link: the background job page shows the report type and the harvest period of that month only, with one month of data 3. Go to E-resource management > Home: the "Latest SUSHI Counter jobs" widget shows the three jobs with a "Report type" and a "Period" column 4. Let one month fail (for example disable the network during the harvest): the failed job page names the report type and the period, and the other months still finish 5. Run the cronjob: misc/cronjobs/erm_run_harvester.pl --begin-date 2024-01-01 \ --end-date 2024-03-31 --dry-run It lists, per provider and report type, the three monthly periods that would be enqueued and enqueues nothing 6. Run it without --dry-run: it reports the jobs it enqueued per report type with their month range and job ids, and the jobs appear in the widget 7. Run it with --begin-date set to a date after today: the script stops with an error message and enqueues nothing 8. Run it with --end-date in the future: the end date is reduced to today and no error is reported 9. prove -l t/db_dependent/Koha/ERM/EUsage/UsageDataProvider.t \ t/db_dependent/api/v1/erm_usage_data_providers.t \ t/db_dependent/Koha/BackgroundJobs/ErmSushiHarvester.t 10. yarn cypress run --spec t/cypress/integration/ERM/DataProviders_spec.ts yarn cypress run --spec t/cypress/integration/ERM/ModuleDashboard_spec.ts Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #23 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 210904 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210904&action=edit Bug 41294: Update the job report for the background job and cronjob The background job page shows the report type and the harvest period of each monthly job, and names the period in the failure message; both strings are translatable. The cronjob reports the jobs it enqueued per report type, in the order of the provider's report types, with the month range and the job ids. --dry-run now lists the report types and the monthly periods that would be enqueued for each provider instead of printing nothing. A bad date range stops the script with the message of the exception. Assisted-by: Sonnet 5 (Anthropic) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|42217 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42217 [Bug 42217] ERM Usage – Harvesting Twice Does Not Overwrite Data -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #25 from Michaela Sieber <michaela.sieber@kit.edu> --- Created attachment 210941 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210941&action=edit Bug 41294: Split harvest period into monthly jobs A harvest over several months ran as one background job and one SUSHI request. Providers serve usage per month, a failure in one month lost the whole range, and the counter log held one row for the range so a month could not be retried on its own. Koha::ERM::EUsage::UsageDataProvider->harvest_periods splits a date range into one period per calendar month: the first period starts on the begin date, the last ends on the end date, equal dates give one period. The dates are calendar days in the floating time zone, so the split does not depend on the server time zone or on daylight saving. An end date after today is reduced to today; a begin date after today throws BadParameter. enqueue_sushi_harvest_jobs enqueues one job per report type and month and returns the jobs with their report type and period. The process_SUSHI_response API returns that list, accepts equal dates, and answers 400 with the message of a BadParameter exception. Test plan: 1. On the data providers list, click "Run now" for a provider and ask for a period of three months. The message lists, per report type, "3 jobs queued for report type TR_J1" with one link per month 2. Click a month link: the background job page shows the report type and the harvest period of that month only, with one month of data 3. Go to E-resource management > Home: the "Latest SUSHI Counter jobs" widget shows the three jobs with a "Report type" and a "Period" column 4. Let one month fail (for example disable the network during the harvest): the failed job page names the report type and the period, and the other months still finish 5. Run the cronjob: misc/cronjobs/erm_run_harvester.pl --begin-date 2024-01-01 \ --end-date 2024-03-31 --dry-run It lists, per provider and report type, the three monthly periods that would be enqueued and enqueues nothing 6. Run it without --dry-run: it reports the jobs it enqueued per report type with their month range and job ids, and the jobs appear in the widget 7. Run it with --begin-date set to a date after today: the script stops with an error message and enqueues nothing 8. Run it with --end-date in the future: the end date is reduced to today and no error is reported 9. prove -l t/db_dependent/Koha/ERM/EUsage/UsageDataProvider.t \ t/db_dependent/api/v1/erm_usage_data_providers.t \ t/db_dependent/Koha/BackgroundJobs/ErmSushiHarvester.t 10. yarn cypress run --spec t/cypress/integration/ERM/DataProviders_spec.ts yarn cypress run --spec t/cypress/integration/ERM/ModuleDashboard_spec.ts Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #27 from Michaela Sieber <michaela.sieber@kit.edu> --- Created attachment 210943 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210943&action=edit Bug 41294: Update the job report for the background job and cronjob The background job page shows the report type and the harvest period of each monthly job, and names the period in the failure message; both strings are translatable. The cronjob reports the jobs it enqueued per report type, in the order of the provider's report types, with the month range and the job ids. --dry-run now lists the report types and the monthly periods that would be enqueued for each provider instead of printing nothing. A bad date range stops the script with the message of the exception. Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #29 from Michaela Sieber <michaela.sieber@kit.edu> --- Signed off using a sandbox -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA --- Comment #30 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- I made a minor rebase here on top of 42218 and will add that as a dependency - without that bug the monthly and yearly totals can get out of alignment as a month with matching data can skip a yearly usage -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #31 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 211132 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=211132&action=edit Bug 41294: Split harvest period into monthly jobs A harvest over several months ran as one background job and one SUSHI request. Providers serve usage per month, a failure in one month lost the whole range, and the counter log held one row for the range so a month could not be retried on its own. Koha::ERM::EUsage::UsageDataProvider->harvest_periods splits a date range into one period per calendar month: the first period starts on the begin date, the last ends on the end date, equal dates give one period. The dates are calendar days in the floating time zone, so the split does not depend on the server time zone or on daylight saving. An end date after today is reduced to today; a begin date after today throws BadParameter. enqueue_sushi_harvest_jobs enqueues one job per report type and month and returns the jobs with their report type and period. The process_SUSHI_response API returns that list, accepts equal dates, and answers 400 with the message of a BadParameter exception. Test plan: 1. On the data providers list, click "Run now" for a provider and ask for a period of three months. The message lists, per report type, "3 jobs queued for report type TR_J1" with one link per month 2. Click a month link: the background job page shows the report type and the harvest period of that month only, with one month of data 3. Go to E-resource management > Home: the "Latest SUSHI Counter jobs" widget shows the three jobs with a "Report type" and a "Period" column 4. Let one month fail (for example disable the network during the harvest): the failed job page names the report type and the period, and the other months still finish 5. Run the cronjob: misc/cronjobs/erm_run_harvester.pl --begin-date 2024-01-01 \ --end-date 2024-03-31 --dry-run It lists, per provider and report type, the three monthly periods that would be enqueued and enqueues nothing 6. Run it without --dry-run: it reports the jobs it enqueued per report type with their month range and job ids, and the jobs appear in the widget 7. Run it with --begin-date set to a date after today: the script stops with an error message and enqueues nothing 8. Run it with --end-date in the future: the end date is reduced to today and no error is reported 9. prove -l t/db_dependent/Koha/ERM/EUsage/UsageDataProvider.t \ t/db_dependent/api/v1/erm_usage_data_providers.t \ t/db_dependent/Koha/BackgroundJobs/ErmSushiHarvester.t 10. yarn cypress run --spec t/cypress/integration/ERM/DataProviders_spec.ts yarn cypress run --spec t/cypress/integration/ERM/ModuleDashboard_spec.ts Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu> Signed-off-by: Nick Clemens <nick@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 --- Comment #33 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 211134 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=211134&action=edit Bug 41294: Update the job report for the background job and cronjob The background job page shows the report type and the harvest period of each monthly job, and names the period in the failure message; both strings are translatable. The cronjob reports the jobs it enqueued per report type, in the order of the provider's report types, with the month range and the job ids. --dry-run now lists the report types and the monthly periods that would be enqueued for each provider instead of printing nothing. A bad date range stops the script with the message of the exception. Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu> Signed-off-by: Nick Clemens <nick@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |42218 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42218 [Bug 42218] ERM Usage – Database Table erm_usage_yus -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41294 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |26.11.00 released in| | Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.