Fixes #1215 - Add configuration of AI summary generation via condition

Author: ralf401

ai/summary.rst

@@ -26,12 +26,22 @@ Configure what the summary should include. After activating the feature,
 choose to activate **Open Questions**, **Upcoming Events** and
 **Customer Sentiment**, depending on your use case.
 
+Summary Selector
+----------------
+
+Use :doc:`object conditions </misc/object-conditions/basics>` to define
+precisely which tickets should be considered for the AI summary
+generation. This allows you to specify conditions based on ticket attributes
+such as group, state, priority or custom attributes. The summary generation is
+only available for tickets matching the configured conditions. For other
+tickets, the summary sidebar tab isn't available.
+
 Summary Generation
 ------------------
 
-In general, the ticket summary is only triggered if the ticket got updated since
-the last summary generation. You can choose the timing of the generation or hide
-the sidebar tab at all via the dropdown:
+In general, the ticket summary is only triggered if the ticket matches the
+configured condition and has been updated since the last summary generation.
+You can choose the timing of the generation via the dropdown:
 
 On ticket detail opening
    The summary is generated when an agent opens the ticket. This can be more
@@ -43,8 +53,7 @@ On ticket summary sidebar activation
    viewed. However, it can happen that an agent has to wait for the summary
    to be generated, depending on the ticket size and the resources.
 
-Hide ticket summary sidebar
-   This hides the summary sidebar tab at all. This option can be useful if
-   you want to enable the summary for specific groups only. Check the
+.. note::
+   You can also configure the summary generation on a group level. Check the
    :doc:`group settings </manage/groups/settings>` section about where to
    configure the summary for each group individually.

images/ai/summary-settings.png

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad Admin Documentation pre-release\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-06-29 08:20+0200\n"
+"POT-Creation-Date: 2026-06-29 15:10+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -528,36 +528,40 @@ msgid "Configure what the summary should include. After activating the feature,
 msgstr ""
 
 #: ../ai/summary.rst:30
-#: ../manage/groups/settings.rst:99
-msgid "Summary Generation"
+msgid "Summary Selector"
 msgstr ""
 
 #: ../ai/summary.rst:32
-msgid "In general, the ticket summary is only triggered if the ticket got updated since the last summary generation. You can choose the timing of the generation or hide the sidebar tab at all via the dropdown:"
+msgid "Use :doc:`object conditions </misc/object-conditions/basics>` to define precisely which tickets should be considered for the AI summary generation. This allows you to specify conditions based on ticket attributes such as group, state, priority or custom attributes. The summary generation is only available for tickets matching the configured conditions. For other tickets, the summary sidebar tab isn't available."
+msgstr ""
+
+#: ../ai/summary.rst:40
+#: ../manage/groups/settings.rst:106
+msgid "Summary Generation"
 msgstr ""
 
-#: ../ai/summary.rst:39
+#: ../ai/summary.rst:42
+msgid "In general, the ticket summary is only triggered if the ticket matches the configured condition and has been updated since the last summary generation. You can choose the timing of the generation via the dropdown:"
+msgstr ""
+
+#: ../ai/summary.rst:49
 msgid "On ticket detail opening"
 msgstr ""
 
-#: ../ai/summary.rst:37
+#: ../ai/summary.rst:47
 msgid "The summary is generated when an agent opens the ticket. This can be more comfortable for agents as the summary is already present or at least triggered when the agent wants to read it."
 msgstr ""
 
-#: ../ai/summary.rst:44
+#: ../ai/summary.rst:54
 msgid "On ticket summary sidebar activation"
 msgstr ""
 
-#: ../ai/summary.rst:42
+#: ../ai/summary.rst:52
 msgid "This option can save computing resources if the AI summary is not always viewed. However, it can happen that an agent has to wait for the summary to be generated, depending on the ticket size and the resources."
 msgstr ""
 
-#: ../ai/summary.rst:49
-msgid "Hide ticket summary sidebar"
-msgstr ""
-
-#: ../ai/summary.rst:47
-msgid "This hides the summary sidebar tab at all. This option can be useful if you want to enable the summary for specific groups only. Check the :doc:`group settings </manage/groups/settings>` section about where to configure the summary for each group individually."
+#: ../ai/summary.rst:57
+msgid "You can also configure the summary generation on a group level. Check the :doc:`group settings </manage/groups/settings>` section about where to configure the summary for each group individually."
 msgstr ""
 
 #: ../ai/writing-assistant.rst:2
@@ -750,7 +754,7 @@ msgstr ""
 #: ../channels/email/filters.rst:96
 #: ../channels/email/accounts/secondary-addresses.rst:46
 #: ../channels/email/filters.rst:96
-#: ../manage/groups/settings.rst:103
+#: ../manage/groups/settings.rst:110
 #: ../manage/macros.rst:65
 #: ../manage/organizations/index.rst:120
 #: ../manage/roles/index.rst:89
@@ -788,7 +792,7 @@ msgstr ""
 #: ../channels/email/filters.rst:100
 #: ../channels/email/filters.rst:100
 #: ../channels/email/filters.rst:100
-#: ../manage/groups/settings.rst:124
+#: ../manage/groups/settings.rst:131
 #: ../manage/macros.rst:71
 #: ../manage/organizations/index.rst:135
 #: ../manage/overviews.rst:0
@@ -7214,23 +7218,27 @@ msgstr ""
 msgid "Allows you to override the :doc:`AI ticket summary </ai/summary>` configuration. Choose when the summary should get generated or hide the ticket summary sidebar tab at all for this group."
 msgstr ""
 
-#: ../manage/groups/settings.rst:102
+#: ../manage/groups/settings.rst:103
+msgid "In addition to this group-level setting, you can also use :doc:`object conditions </misc/object-conditions/basics>` in the :doc:`AI ticket summary configuration </ai/summary>` to define more precisely which tickets should have the summary generated."
+msgstr ""
+
+#: ../manage/groups/settings.rst:109
 msgid "An internal note about the group that is only visible to people who can access the group management area."
 msgstr ""
 
-#: ../manage/groups/settings.rst:106
+#: ../manage/groups/settings.rst:113
 msgid "Don't need the group anymore or want to restrict the selection of this group? If you can't or don't want to recycle (rename) the group, you can also set it to inactive. Agents will no longer be able to see or edit tickets in this group. However, customers can still interact with their existing tickets in an inactive group."
 msgstr ""
 
-#: ../manage/groups/settings.rst:114
+#: ../manage/groups/settings.rst:121
 msgid "Want to handle tickets from an inactive group, which are updated by customers?"
 msgstr ""
 
-#: ../manage/groups/settings.rst:117
+#: ../manage/groups/settings.rst:124
 msgid "You could e.g. create a trigger which moves them to another group when they got updated. Create this trigger before deactivating the group so it is selectable in the trigger configuration."
 msgstr ""
 
-#: ../manage/groups/settings.rst:123
+#: ../manage/groups/settings.rst:130
 msgid "Please keep in mind that you still can route tickets into these groups. This is potentially dangerous, make sure the group is no longer part of email filters or a destination group."
 msgstr ""
 

locale/admin-docs.pot

@@ -95,9 +95,16 @@ Shared Drafts
 
 Summary Generation
    Allows you to override the :doc:`AI ticket summary </ai/summary>`
-   configuration. Choose when the summary should get generated or hide the 
+   configuration. Choose when the summary should get generated or hide the
    ticket summary sidebar tab at all for this group.
 
+   .. hint::
+
+      In addition to this group-level setting, you can also use
+      :doc:`object conditions </misc/object-conditions/basics>` in the
+      :doc:`AI ticket summary configuration </ai/summary>` to define more
+      precisely which tickets should have the summary generated.
+
 Note
    An internal note about the group that is only visible to people who can
    access the group management area.