Hello Zammad Team,
We need to be able to add multiple values to an overview conditions attribute or to be able to add additional conditions for that attribute.
For instance, for version 2.6.x, I can add a condition with the following:
Customer | is not | specific user | ‘User A’
I need the functionality to add an additional user to the user field OR to add an additional condition to exclude another user. Example:
Customer | is not | specific user | ‘User A’
AND
Customer | is not | specific user | ‘User A’
OR
Customer | is not | specific user | ‘User A; User B’
As it currently stands, I can only add one condition for each attribute and can only add one value in the field.
There is already a Feature Request on github.
opened 03:19PM - 13 Aug 18 UTC
closed 02:55PM - 02 Dec 22 UTC
enhancement
trigger
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.6.x
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: any
* Ticket-ID: #1031039, #1060690, #1067221, #1072409, #1079103, #1079241, #1079346, #1079468, #1082065, #1080184, #1083072, #1083556, #1083611, #1084691, #1087205, #1090351, #1099619
### Expected behavior:
* When ever using conditions (e.g. for Overviews or Triggers) it should be possible to use OR condition (e.g. using the same type of statement more than once )
### Actual behavior:
* Zammad only allows AND-Conditions
* It's not possible to use a Statement type more than once per query
This applies at least to the following Zammad-Sections and should be done at all possible places, because the user would not expect the dialoges to be inconsistend:
- Overviews
- Trigger
- Scheduler
- SLAs
- Time Accounting
### Steps to reproduce the behavior:
The following applies to any Zammad-Section mentioned above, I'll use overviews as example
* Create a new overview, giving it a meaningfull name
* As condition, choose "OWNER is specific user AGENT A"
* press + for a new condition part
* try to choose owner, to make the condition match to AGENT B, too
=> won't work - this should be possible.
This Issue is to cover all request too 100%, thus the other issues will be closed and linked below:
#885
#1004
### Tasks
- [x] https://github.com/zammad/coordination-sprint-tasks/issues/10
- [x] https://github.com/zammad/coordination-sprint-tasks/issues/6
Mirtaaa
September 11, 2023, 8:31am
4
Hello Tyler,
we are currently cleaning up our community and found your request.
As this is an old request, this is possible by now with our AND/OR conditions. If you turn on the expert mode you will be able to set up exactly your use case:
Best
Mirta