Back to bug 33268

Who When What Removed Added
katrin.fischer 2023-03-17 16:34:36 UTC Depends on 14957
katrin.fischer 2023-06-10 19:08:24 UTC CC esther.melander
nick 2023-06-29 16:26:27 UTC CC jonathan.druart+koha, martin.renvoize, nick, tomascohen
michaela.sieber 2023-09-15 14:57:27 UTC See Also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34191
glasklas 2023-11-13 16:01:46 UTC CC glasklas
glasklas 2023-11-14 19:03:42 UTC Status NEW In Discussion
glasklas 2023-11-15 19:02:00 UTC Attachment #158956 Attachment is obsolete 0 1
glasklas 2023-11-16 17:55:31 UTC Status In Discussion Needs Signoff
glasklas 2023-11-16 17:55:55 UTC Assignee koha-bugs glasklas
david 2023-11-21 13:40:58 UTC Status Needs Signoff Signed Off
david 2023-11-21 13:41:01 UTC Attachment #159004 Attachment is obsolete 0 1
david 2023-11-21 13:41:04 UTC Attachment #159058 Attachment is obsolete 0 1
m.de.rooy 2023-11-24 08:03:32 UTC CC m.de.rooy
victor 2023-12-03 15:43:01 UTC CC victor
Status Signed Off Failed QA
tomascohen 2023-12-04 11:35:05 UTC Status Failed QA Signed Off
tomascohen 2023-12-04 11:35:09 UTC Attachment #159161 Attachment is obsolete 0 1
Attachment #159160 Attachment is obsolete 0 1
martin.renvoize 2023-12-19 15:18:35 UTC Attachment #159518 Attachment is obsolete 0 1
martin.renvoize 2023-12-19 15:18:38 UTC Attachment #159519 Attachment is obsolete 0 1
martin.renvoize 2023-12-19 15:19:09 UTC Status Signed Off Passed QA
katrin.fischer 2023-12-28 09:26:13 UTC Keywords release-notes-needed
Status Passed QA Failed QA
r.delahunty 2024-02-28 11:52:15 UTC CC r.delahunty
glasklas 2024-03-05 14:30:13 UTC Status Failed QA Needs Signoff
glasklas 2024-03-05 15:51:39 UTC Attachment #162764 Attachment is obsolete 0 1
glasklas 2024-03-05 15:58:39 UTC Attachment #162766 Attachment is obsolete 0 1
glasklas 2024-03-05 17:19:38 UTC Attachment #162767 Attachment is obsolete 0 1
glasklas 2024-03-05 17:20:38 UTC Attachment #162785 Attachment is obsolete 0 1
victor 2024-03-05 22:33:29 UTC Attachment #160018 Attachment is obsolete 0 1
victor 2024-03-05 22:33:32 UTC Attachment #160017 Attachment is obsolete 0 1
victor 2024-03-05 22:33:35 UTC Attachment #162786 Attachment is obsolete 0 1
victor 2024-03-05 23:33:51 UTC Attachment #162796 Attachment is obsolete 0 1
victor 2024-03-05 23:33:55 UTC Attachment #162797 Attachment is obsolete 0 1
victor 2024-03-05 23:33:58 UTC Attachment #162798 Attachment is obsolete 0 1
victor 2024-03-05 23:34:01 UTC Attachment #162799 Attachment is obsolete 0 1
victor 2024-03-05 23:34:02 UTC Comment 40 Tag obsolete
victor 2024-03-05 23:34:04 UTC Comment 41 Tag obsolete
victor 2024-03-05 23:34:05 UTC Comment 42 Tag obsolete
victor 2024-03-05 23:34:06 UTC Attachment #162800 Attachment is obsolete 0 1
victor 2024-03-05 23:34:07 UTC Comment 43 Tag obsolete
victor 2024-03-05 23:34:08 UTC Comment 44 Tag obsolete
victor 2024-03-05 23:52:36 UTC Status Needs Signoff Failed QA
glasklas 2024-03-06 16:21:10 UTC Status Failed QA Needs Signoff
victor 2024-03-08 04:04:13 UTC Attachment #162801 Attachment is obsolete 0 1
victor 2024-03-08 04:04:50 UTC Attachment #162802 Attachment is obsolete 0 1
victor 2024-03-08 04:05:29 UTC Attachment #162803 Attachment is obsolete 0 1
victor 2024-03-08 04:06:08 UTC Attachment #162804 Attachment is obsolete 0 1
victor 2024-03-08 04:06:44 UTC Attachment #162805 Attachment is obsolete 0 1
victor 2024-03-08 05:06:32 UTC Status Needs Signoff Signed Off
glasklas 2024-03-11 17:11:36 UTC Text to go in the release notes , if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden
Severity major enhancement
Text to go in the release notes This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source"

- If no matching rule is found
Patch complexity --- Medium patch
Text to go in the release notes , a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context.
Change sponsored? --- Sponsored
Text to go in the release notes , the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value)
glasklas 2024-03-11 17:21:11 UTC Text to go in the release notes , the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value), if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source"

- If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context.
, the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value), if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source"

- If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context.

For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior
glasklas 2024-03-11 17:23:44 UTC Text to go in the release notes , regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context.

For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value), if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source"

- If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary
, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context module.

For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value), if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source".

- If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary
mnero 2024-03-12 16:21:48 UTC CC mnero
victor 2024-03-12 21:14:51 UTC Text to go in the release notes , if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source".

- If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context module.

For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value)
glasklas 2024-04-02 09:49:09 UTC Text to go in the release notes , regardless of if any of the rules with that filter value matched or not. With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context module. For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows: - A matching rule is looked for based on context (module and filter value), if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, "Patron category" and "Source". - If no matching rule is found, a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules. In summary
victor 2024-04-03 04:55:49 UTC Text to go in the release notes , a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules. In summary, regardless of if any of the rules with that filter value matched or not. With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context module. For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows: - A matching rule is looked for based on context (module and filter value), if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated. Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, "Patron category" and "Source". - If no matching rule is found , a wildcard tag rule for that filter value can be defined which will have higher precedence and override all the filter wildcard rules.

In summary, regardless of if any of the rules with that filter value matched or not.

With this change we fallback to the wildcard filter rules even though rules with a matching filter value do exists, we fallback to the wildcard filter rules of the current context module.

For Koha installations where marc overlay rules is in use a database migration will run that creates new rules if necessary to preserve the current behavior, the rules will applied as follows:

- A matching rule is looked for based on context (module and filter value), if no rule for that filter value matches. This resolves the issue of having to repeat the same default rules for each filter value rule set. If for some filter value the wildcard filter rules should be overridden, so no user action needs to be taken in order to correct for this change. This enhancement changes how marc overlay rules are evaluated.

Before the change rules with filter set to '*' (wildcard) where only applied when no other rules had been defined for a specific filter value, if multiple contexts matches rules for the module with highest priority are used. The module priority is (from highest to lowest) "User name", "Patron category" and "Source".

- If no matching rule is found
katrin.fischer 2024-05-02 16:58:30 UTC Severity enhancement normal
katrin.fischer 2024-05-09 07:12:38 UTC Keywords RM_priority
nick 2024-05-10 13:47:46 UTC Status Signed Off Failed QA
bibliothek 2024-11-20 11:53:26 UTC CC bibliothek
lisette 2024-11-21 15:32:55 UTC CC lisette
Keywords release-notes-needed
bibliothek 2024-12-18 18:30:17 UTC Attachment #162936 Attachment is obsolete 0 1
bibliothek 2024-12-18 18:30:21 UTC Attachment #162937 Attachment is obsolete 0 1
bibliothek 2024-12-18 18:30:24 UTC Attachment #162938 Attachment is obsolete 0 1
bibliothek 2024-12-18 18:30:28 UTC Attachment #162939 Attachment is obsolete 0 1
bibliothek 2024-12-18 18:30:31 UTC Attachment #162940 Attachment is obsolete 0 1
bibliothek 2024-12-19 07:41:47 UTC Status Failed QA Needs Signoff
victor 2024-12-25 23:25:25 UTC Attachment #175659 Attachment is obsolete 0 1
victor 2024-12-25 23:25:28 UTC Attachment #175660 Attachment is obsolete 0 1
victor 2024-12-25 23:25:32 UTC Attachment #175661 Attachment is obsolete 0 1
victor 2024-12-25 23:25:35 UTC Attachment #175662 Attachment is obsolete 0 1
victor 2024-12-25 23:25:39 UTC Attachment #175663 Attachment is obsolete 0 1
victor 2024-12-25 23:36:23 UTC Status Needs Signoff Signed Off
dcook 2024-12-26 22:26:25 UTC CC dcook
martin.renvoize 2025-01-07 15:59:33 UTC QA Contact testopia martin.renvoize
martin.renvoize 2025-01-07 16:10:50 UTC Attachment #175939 Attachment is obsolete 0 1
martin.renvoize 2025-01-07 16:10:54 UTC Attachment #175940 Attachment is obsolete 0 1
martin.renvoize 2025-01-07 16:10:57 UTC Attachment #175941 Attachment is obsolete 0 1
martin.renvoize 2025-01-07 16:11:01 UTC Attachment #175942 Attachment is obsolete 0 1
martin.renvoize 2025-01-07 16:11:04 UTC Attachment #175943 Attachment is obsolete 0 1
martin.renvoize 2025-01-07 16:11:51 UTC Status Signed Off Passed QA
katrin.fischer 2025-01-10 17:00:28 UTC Status Passed QA Pushed to main
Version(s) released in 25.05.00
paul.derscheid 2025-04-17 12:45:19 UTC Status Pushed to main Pushed to stable
Version(s) released in 25.05.00 25.05.00,24.11.04
lucas 2025-06-02 21:32:44 UTC CC lucas
Keywords RM_priority

Back to bug 33268