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

Misleading 'Escalation' ticket attribute name in SLAs, Scheduler and Trigger should be named 'Escalation_at' #2615

Closed
MrGeneration opened this issue Jun 21, 2019 · 1 comment
Assignees
Milestone

Comments

@MrGeneration
Copy link
Member

Infos:

  • Used Zammad version: 3.0
  • Installation method (source, package, ..): any
  • Operating system: any
  • Database + version: any
  • Elasticsearch version: any
  • Browser + version: any

Desiredbehavior:

We should rename the condition "escalation" to "escalation at".
The current naming is miss leading, as it suggest that this will check if a ticket has escalated.

Infact, this triggers on every moment, when your "escalation_at" field changes.
The function itself works as designed.

This came up on: https://community.zammad.org/t/trigger-on-escalate-does-not-work-properlly/2637/5

@gfriloux
Copy link

gfriloux commented Jun 21, 2019

I indeed spent some hours trying to understand the "escalation" trigger, and this request for renaming is probably a very nice idea.

While this could seem abvious for a zammad dev, some users (like me) just get lost.

(i also spent time looking at API, so i know the escalation_at variable)

@thorsteneckel thorsteneckel changed the title Rename "Escalation" in "Escalation at" for conditions (SLA context) Misleading 'Escalation' ticket attribute name in SLAs, Scheduler and Trigger should be named 'Escalation_at' Jun 24, 2019
@thorsteneckel thorsteneckel added this to the 3.1.0 milestone Jun 24, 2019
zammad-sync pushed a commit that referenced this issue Jun 24, 2019
…SLAs, Scheduler and Trigger should be named 'Escalation_at'.
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

4 participants