Title: let customer change organization of a ticket
- What is your original issue/pain point you want to solve?
- usually, tickets need to be private, but sometimes it makes sense to work together with colleagues.
- usually, users send a mail to the ticket system to create a new issue. they rarely use the web interface or even know at first that the need to share their ticket
- users have a primary organization (private) and one or more secondary organization like their department or project group, which are sharing organizations
- Which are one or two concrete situations where this problem hurts the most?
- a secretary sends the message while colleague a needs the help, colleague b has to provide information and all want to be informed about the resolving of the issue
- person a wants something, the agent needs more information that person b can provide
- Why is it not solvable with the Zammad standard?
- there are no options to do that, and the zammad system prevents it toe and claw
- What is your expectation/what do you want to achieve?
- there should be an option for the client to change the organization of his ticket to one of his own primary or secondary organizations
If there is any more useful information, feel free to share it all (e.g.: mockup screenshots, if something is UI related, or the API URL/documentation URL for a service you need a connection to).
Your Zammad environment:
- Average concurrent agent count: 5
- Average tickets a day: 10
- What roles/people are involved: standard office persons, non-technical staff
Anything else which you think is useful to understand your use case:
sure, an agent could change that for the client. but why not let the client do this?
Thank you and have fun.