Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created Status is not working Properly #5146

Open
Bozo0511 opened this issue Apr 23, 2024 · 3 comments
Open

Created Status is not working Properly #5146

Bozo0511 opened this issue Apr 23, 2024 · 3 comments

Comments

@Bozo0511
Copy link
Collaborator

Used Zammad Version

6.3

Environment

  • Installation method: package
  • Operating system (if you're unsure: cat /etc/os-release ): any
  • Database + version: any
  • Elasticsearch version: any
  • Browser + version: any

Actual behaviour

I created 2 Status:

  1. Testme (open status)
  2. Testmenot (closed status)

I set the status "Testme" as default for new ticket creation and follow up.
I deactivated all other status.

Agent: when I create a ticket with an agent I can choose between "open", "testme" and "testmenot" status.
Customer: when I create a ticket as a customer I can choose between "new" and "testmenot" status

Expected behaviour

Since all other status are inactive, I would expect that I can only choose between "testme" and "testmenot" status.

Steps to reproduce the behaviour

  • Create an open status and set it as default for new tickets and follow up.

  • Create an closed status

  • deactivate all other status
    2024-04-23 16_37_12-Zammad Helpdesk - Ticket States – Opera

  • Create ticket as agent:
    2024-04-23 16_39_00-Zammad Helpdesk - Inbound Call – Opera

-Create ticket as Customer:
2024-04-23 16_40_33-Zammad Helpdesk - New Ticket – Opera

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes

@MrGeneration
Copy link
Member

Encountered the same issue when trying these and forgot to create an issue.
In my experience restarting Zammad is required to ensure full and expected functionality. Did you try that?

Setting states to inactive didn't matter btw. At least in my test.

@dominikklein
Copy link
Collaborator

When I remember correctly, minimum one new state needs to be present/active?

@t-shehab
Copy link

@MrGeneration

Yesterday, when @Bozo0511 showed me this issue, I remembered that you resolved this via a restart when you encountered it. But when I tried that yesterday, it remained broken after restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants